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 ajaksu2, ccgus, loewis, r.david.murray
Date 2010-11-05.09:12:19
SpamBayes Score 5.04953e-06
Marked as misclassified No
Message-id <>
I'm closing this issue as invalid, since as Martin pointed out you can't send unicode over the wire.

However, see issue 10321 where I've attached a patch that adds support for sending binary data as a by-product of adding support for Message objects.

From Martin's msg76301 I gather he initially expected sendmail to take only binary data, which would it seems to me probably be the better API.  However at this point we are stuck with supporting ASCII-only strings in the API as well.

As a further note, however, the original example in this issue would have produced a non-RFC-conformant message when used in python 2.x.  You can't just send 8bit data willy-nilly, there are rules that should be followed.  Which is why the issue 10321 patch adds support for using Message objects, since the email package knows what those rules are...
Date User Action Args
2010-11-05 09:12:20r.david.murraysetrecipients: + r.david.murray, loewis, ajaksu2, ccgus
2010-11-05 09:12:20r.david.murraysetmessageid: <>
2010-11-05 09:12:19r.david.murraylinkissue4403 messages
2010-11-05 09:12:19r.david.murraycreate