PowerMTA Support Forum
General Category => General Discussion => Topic started by: CaLViN on January 16, 2013, 06:59:18 AM
-
Hello dears,
Are you having errors on Italian domains like alice.it libero.it tin.it virgilio.it ?
It seems like they are throttling us with below errors :
SMTP service unavailable: "421 Exceeded allowable connection time, disconnecting." received from liberomx2.libero.it
SMTP service unavailable: "421 #4.4.5 Too many connections from your host."
SMTP service unavailable: "421 <marino.luigi.s@alice.it> Service not available - too busy" received from smtp.aliceposta.it
Could you please share your current experience ?
8)
-
Yes, saw quite a bit of it yesterday, but today seems much better, in fact all of the .it domains had the same issue, don't know if it is related to something else.
-
May I ask what sort of configurations people have found to work for sending to these domains? Recently, a very large percentage of all the domains in backoff mode for us right now are Italian domains (*.it). We've done a lot of tweaking but haven't quite found the right formula. Also, any insight as to why this is an issue all of a sudden, or mentions from anyone else that has had the problem would be cool. Thank you.
-
We don't have much volume to these domains, but I also saw this recently so set smtp-out to 2 and it has been working fine since.
-
Is there a particular SMTP error response or two being returned across these domains? If so, what specifically are they sending back?
-
I only saw "...too many connections from..."
-
Still seeing "too many connections" error.
-
Are the errors given back to connections that are made above some unpublished simultaneous connection limit (with active connections still delivering), or are they given back to all connections made after hitting some total connection limit within a time period (say after 100 total connections made to them within an hour)?
-
Wanted to check in and see if anyone had any success finding a limit that these Italian domains like. And to respond to the last question (apologies for just responding now), it does seem that the errors are given back to connections that are made above some unpublished concurrent connection limit. We still deliver through active connections even as we get these errors.
I've tried lowering max-smtp-out to 1 to no avail. I've done a lot of tweaking, lowering and raising max-msg-rate, max-msg-per-connection, max-rcpt-per-message, and max-connect-rate. But, it's all trial and error, and so it's sort of like navigating in the dark. It's good to know others are seeing the same "too many connections" error. Hopefully, together, we can find something that works.