This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author izomiac
Recipients barry, izomiac, pepoluan, r.david.murray
Date 2021-01-05.19:01:17
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1609873277.67.0.530531961814.issue42498@roundup.psfhosted.org>
In-reply-to
Content
I agree, it's my suspicion that the server's error message and python's outbound command are sent so close to each other that buffering ensures they disagree about the exact sequence of commands/responses.

As for my server, it was HAProxy doing the injection and I rewrote the server to both ignore PROXY commands and to listen on multiple ports so a proxy is not necessary. 

So this issue no longer exists for me, but I know that I'm not the only one who uses HAProxy to forward SMTP requests (residential ISPs block port 25), and Python was relatively unique in its intolerance of this behavior.  (Python uses lower case commands, which are easy to recognize on server logs to determine which clients are using it.)  It's certainly not a critical issue affecting thousands, but in my experience glitchy behavior is a good indicator that the code is buggy in general.  Plus, buffering errors scare me because there are so many potential security exploits associated with them (on top of being a pain to debug.)  But, yeah, this is more of a courtesy bug to let you know about a tricky glitch I encountered.
History
Date User Action Args
2021-01-05 19:01:17izomiacsetrecipients: + izomiac, barry, r.david.murray, pepoluan
2021-01-05 19:01:17izomiacsetmessageid: <1609873277.67.0.530531961814.issue42498@roundup.psfhosted.org>
2021-01-05 19:01:17izomiaclinkissue42498 messages
2021-01-05 19:01:17izomiaccreate