On Fri, 28 Oct 2016 11:23:49 +0200, Benoit Panizzon said: > Nice, so Yahoo's mailservers are broken?
It's 2016. The mere fact it's sending HELO rather than EHLO is a pretty good indication that it is either so decrepit or so deficient that it can safely be called broken. The fact it doesn't even do RFC821 correctly (apparently choking on a perfectly valid multi-line response) is further evidence that it's plagued by less than stellar code quality. (Note that your spamtrap gets a few demerits for sending a 200 rather than 250 response, but if you change that to a single-line 200 response and it starts working, that's even more evidence that the far end is incredibly confused....) I'm trying to be gracious and not use the phrase "steaming pile of dingo's kidneys". :) (For the RFC lawyers out there - although RFC2821 section 3.2 specifically says "Servers MUST NOT return the extended EHLO-style response to a HELO command.", that is essentially a no-harm/no-foul case, because an RFC821 client must still be able to deal with a multi-line 250 reply - specifically by ignoring all the text after the 250.)
pgpoBk3bcjSKa.pgp
Description: PGP signature
_______________________________________________ mailop mailing list [email protected] https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
