Message 220754 - Python tracker

➜

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	zvyn
Recipients	barry, jesstess, pitrou, r.david.murray, zvyn
Date	2014-06-16.20:27:56
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1402950477.07.0.805297062536.issue21783@psf.upfronthosting.co.za>
In-reply-to

Content
Sending HELO or EHLO more then once causes smtpd.SMTPChannel to respond with b'503 Duplicate HELO/EHLO\r\n' (see Lib/test/test_smtpd.py:124 for an example). My interpretation of RFC 821, section 4.1.1.5 is that multiple HELO commands are fine outside a mail transaction and a second HELO is eauivalent to a RSET during a mail transaction (undoing any changes made by previous greetings). I would propose to reject greetings during mail transactiond (thats what RSET is for) and else accept them. The question is how we should handle backwards compatibility here. I am willing to work on this right after #21725.

Sending HELO or EHLO more then once causes smtpd.SMTPChannel to respond with b'503 Duplicate HELO/EHLO\r\n' (see Lib/test/test_smtpd.py:124 for an example).

My interpretation of RFC 821, section 4.1.1.5 is that multiple HELO commands are fine outside a mail transaction and a second HELO is eauivalent to a RSET during a mail transaction (undoing any changes made by previous greetings).

I would propose to reject greetings during mail transactiond (thats what RSET is for) and else accept them. The question is how we should handle backwards compatibility here.

I am willing to work on this right after #21725.

History
Date	User	Action	Args
2014-06-16 20:27:57	zvyn	set	recipients: + zvyn, barry, pitrou, r.david.murray, jesstess
2014-06-16 20:27:57	zvyn	set	messageid: <1402950477.07.0.805297062536.issue21783@psf.upfronthosting.co.za>
2014-06-16 20:27:57	zvyn	link	issue21783 messages
2014-06-16 20:27:56	zvyn	create