And the thing is, while I think the ISP delaying schools email for 120
seconds to try and get an ident connection on 113 is nuts, I was too
embarrassed to mention that I was timing out after only 30 seconds - so
I merely said that I had increased the timeout to nearly 5 minutes.
30 seconds is a fine time to *want* to wait; but a measure of
sufficiency is it being long enough to be able to confidently blame the
other party - and it failed on that score.
If I said "but you shouldn't wait 120 seconds for ident which can't be
trusted anyway" the would say "and you should wait longer than 30 seconds".
And the thing is although I would be right, so would they.
Sam
On 29/06/11 07:41, samjam wrote:
My children's school's SMTP server waits 120 seconds before responding
with a "250 Recipient OK" during SMTP.
The server is reports itself as "Mirapoint Messaging Server MOS
4.2.2-FCS Queuing"
Funnily if the connection is aborted after 60 seconds, the "250"
response comes back immediately.
Talks with the techie suggest they are waiting for a response from my
ident server; however although I don't run an ident service the port
is not firewalled so they should get a connection refused pretty
quickly. I'm wondering if their firewall blocks their own ident
connection.
I mention this because:
commit 45ba51763ead4a25ad46fb8b2c82d398fdbb051a
Author: Wilfried Goesgens <dotheb...@citadel.org>
Date: Sun Nov 21 16:34:16 2010 +0100
Relax SMTP Client timeout settings as discussed.
- default is 30 seconds
- Server greeting 90 seconds (DNS lookups for RBLs might be slow
And this is a real-world case where perhaps we need to be more
forgiving than 30 seconds because of someone elses badly configured
mail server.
I increased the timeout from 30 seconds to 230 seconds and - to my
relief, mail started to be delivered.
I think this timeout should be configurable
Sam
