➜

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 Lukasa, r.david.murray
Date 2016-08-09.13:35:11
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1470749712.0.0.972675648207.issue27716@psf.upfronthosting.co.za>
In-reply-to
Content 
utf-8 headers are contrary to the http spec, aren't they?  Or has that changed?  (It's been a long time since I've looked at any http RFCs.)

This could be fixed by using SMTPUTF8 mode when parsing the headers, which in theory ought to be backward compatible.  We could make SMTPUTF8 the default for email.policy.http, if this is correct per the RFCs.
History
Date User Action Args
2016-08-09 13:35:12r.david.murraysetrecipients: + r.david.murray, Lukasa
2016-08-09 13:35:12r.david.murraysetmessageid: <1470749712.0.0.972675648207.issue27716@psf.upfronthosting.co.za>
2016-08-09 13:35:11r.david.murraylinkissue27716 messages
2016-08-09 13:35:11r.david.murraycreate