➜

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 r.david.murray
Recipients Eric Lafontaine, barry, bpoaugust, r.david.murray
Date 2016-12-20.16:32:57
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1482251577.42.0.868155127935.issue28945@psf.upfronthosting.co.za>
In-reply-to
Content 
The RFC compliance battle in email was lost long ago.  We have to do our best to process what we get, and to produce only RFC correct output (unless retransmitting without change).  That is Postel's law, and you can't successfully process Internet email without following the first part.

I haven't looked at the proposed solution yet.  Not sure when I'll get time, since I should try to think and research the questions (why was it done the way it is currently done?), which will take quite a bit of time.
History
Date User Action Args
2016-12-20 16:32:57r.david.murraysetrecipients: + r.david.murray, barry, bpoaugust, Eric Lafontaine
2016-12-20 16:32:57r.david.murraysetmessageid: <1482251577.42.0.868155127935.issue28945@psf.upfronthosting.co.za>
2016-12-20 16:32:57r.david.murraylinkissue28945 messages
2016-12-20 16:32:57r.david.murraycreate