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 airween, r.david.murray
Date 2015-11-26.17:05:12
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1448557513.09.0.324836132777.issue25736@psf.upfronthosting.co.za>
In-reply-to
Content
Although that will work for text-only messages if you know what RFC format looks like, you really don't want to do that in the general case, since you can't express messages that have binary non-text content using unicode.  What you want to do is prepare your message in correct RFC form, which is what the email library is for.  With the new API (provisional now, but any changes will be minor when it becomes final in 3.6), this is even easy (see the 'contentmanager' docs).  Then you call smtplib.send_message, and the encoding to RFC format is taken care of for you.  In 3.5 it even supports SMTPUTF8, if you know any servers that do :)
History
Date User Action Args
2015-11-26 17:05:13r.david.murraysetrecipients: + r.david.murray, airween
2015-11-26 17:05:13r.david.murraysetmessageid: <1448557513.09.0.324836132777.issue25736@psf.upfronthosting.co.za>
2015-11-26 17:05:13r.david.murraylinkissue25736 messages
2015-11-26 17:05:12r.david.murraycreate