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 barry, mkaiser, r.david.murray
Date 2019-12-14.15:28:49
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Yes, google should fix their bug.  However, the python email package tries very hard to interpret even RFC-non-compliant emails when there is a way to do so.  As I said, the package already tries to interpret headers such as google is generating, it's just that there is a bug in that interpretation: it is keeping the blank between then encoded words when it should not be.  That bug can be fixed, in get_raw_encoded_word and/or get_parameter, in email._header_value_parser.
Date User Action Args
2019-12-14 15:28:49r.david.murraysetrecipients: + r.david.murray, barry, mkaiser
2019-12-14 15:28:49r.david.murraysetmessageid: <>
2019-12-14 15:28:49r.david.murraylinkissue39040 messages
2019-12-14 15:28:49r.david.murraycreate