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 akuchling
Recipients akuchling, barry
Date 2010-05-19.20:59:42
SpamBayes Score 0.00020491416
Marked as misclassified No
Message-id <1274302784.42.0.748156911127.issue8769@psf.upfronthosting.co.za>
In-reply-to
Content
The attached patch is a possible fix; it uses the decode_header() and make_header() functions to figure out the encoding properly; it fixes my example, at least.  But does it increase the odds of crashing on messages with malformed headers?  Should it go into 2.7 given that we're at the RC stage?  What about 2.6?

(BTW, Barry, I noticed this because messages being sent through Mailman were coming out with broken subject lines.  The system generating the messages is slightly weird -- doing the UTF-8 quoting is unnecessary since the subject contains no special characters -- but I think Mailman shouldn't be breaking subject lines.  I haven't verified that this Python fix actually fixes Mailman, but I think this is a Python bug, not a Mailman bug.)
History
Date User Action Args
2010-05-19 20:59:44akuchlingsetrecipients: + akuchling, barry
2010-05-19 20:59:44akuchlingsetmessageid: <1274302784.42.0.748156911127.issue8769@psf.upfronthosting.co.za>
2010-05-19 20:59:43akuchlinglinkissue8769 messages
2010-05-19 20:59:43akuchlingcreate