Is anybody having problems listening to yahoo/egroup servers, particularly
those in 64.211.240/24, 208.50.144/24, and 208.50.144/24?  Since about Thu
Nov 16 07:00 GMT, I've had a lot of unsuccessful SMTP transactions.  It
goes something like this: egroup server makes a connection, qmail-smtpd
sends "354 go ahaed", server usually (but not always) sends a packet with
a single line, the "X-eGroups-Return: " header, and then about 9m20s later
an RST.

Note it's not a particular server that's doing this - for example, one
server (hp.egroups.com) made a connection at 23:40:00 and sent the RST at
23:49:26, and made another connection at 23:41:28 which successfully
completed at 23:41:42.

The last time I had a problem with symptoms like this, there was a piece
of network hardware in the route that had a smaller MTU but somebody was
filtering all ICMP traffic, so PMTU discovery wasn't working.  I don't
know if this is a similar situation; one would expect gblx to know what
they're doing.

The end result is a lot of idle SMTP connections, resulting in mail
being routed to the secondary, which is similarly affected.

I'm about screw down the limit on the allowed connections from those
subnets, but I'd like to know if anybpody else is experiencing the
problem before I try talking to yahoo/gblx - I couldn't find anything
in Deja or nanog.

Thanks,
Rick.

Reply via email to