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 Malcolm.Box
Recipients Malcolm.Box, barry, manlioperillo, r.david.murray, t-v
Date 2010-06-22.13:29:10
SpamBayes Score 0.00033996016
Marked as misclassified No
Message-id <>
Echoing the comment of Thomas Viehmann, the current behaviour makes it impossible to use this library to generate a correct multipart/mixed message with 7_or_8_bit encoding on Unix.

The MIME standard specifies that headers are to be CRLF terminated - this is independent of any lower-level transport encoding.  

Binary bodies are simply octet sequences - so may contain \n or \r characters.

The correct MIME encoding would have the headers terminated with CRLF, and the bodies as raw byte sequences.  However on Unix, since the headers are generated with \n not CRLF, you can't even post-process this (e.g. message.as_string().replace('\n', '\r\n') as that will screw up the binary body data.

The current behaviour is basically wrong and should be fixed.
Date User Action Args
2010-06-22 13:29:13Malcolm.Boxsetrecipients: + Malcolm.Box, barry, t-v, manlioperillo, r.david.murray
2010-06-22 13:29:12Malcolm.Boxsetmessageid: <>
2010-06-22 13:29:10Malcolm.Boxlinkissue1349106 messages
2010-06-22 13:29:10Malcolm.Boxcreate