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 r.david.murray
Date 2010-12-12.18:01:47
SpamBayes Score 3.3303465e-08
Marked as misclassified No
Message-id <>
This is a followon to Issue 4661.  The fix for that issue introduced a way to parse messages containing 8bit bytes.  When Generator is called on a model containing 8 bit bytes, it converts it to 7bit clean.  There is, however, a bug in this conversion process: currently when encountering 8bit bytes in headers, it simply replaces then with ?.  According to the RFCs[*], what it should do instead is to replace them with encoded words using the 'charset' "unknown-8bit".

[*] I'm specifically referring to RFC is effectively acting as a translating gateway when requested to do the 8bit to 7bit conversion.  Although that RFC does not explicitly say that the unknown-8bit charset should be used in encoded words, it does imply it strongly in its section 3 prescription.
Date User Action Args
2010-12-12 18:01:49r.david.murraysetrecipients: + r.david.murray
2010-12-12 18:01:49r.david.murraysetmessageid: <>
2010-12-12 18:01:47r.david.murraylinkissue10686 messages
2010-12-12 18:01:47r.david.murraycreate