➜

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 bryced
Recipients barry, bryced, r.david.murray
Date 2018-07-30.22:06:56
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1532988416.67.0.56676864532.issue34277@psf.upfronthosting.co.za>
In-reply-to
Content 
Yes, utf8 is set to false. Despite that, the dkim-signature header, which contains no unicode characters, is getting filled with ?utf-8?q? values.

My reading of the documentation of the utf8 flag is that headers should not be encoded like this if its set to False.  Its possible I am misunderstanding.
History
Date User Action Args
2018-07-30 22:06:56brycedsetrecipients: + bryced, barry, r.david.murray
2018-07-30 22:06:56brycedsetmessageid: <1532988416.67.0.56676864532.issue34277@psf.upfronthosting.co.za>
2018-07-30 22:06:56brycedlinkissue34277 messages
2018-07-30 22:06:56brycedcreate