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 barry, macfreek, r.david.murray
Date 2013-12-29.02:06:54
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1388282814.72.0.904000235284.issue20084@psf.upfronthosting.co.za>
In-reply-to
Content
There is another possible approach, but I haven't decided yet whether or not I like it.  The email package string parser could (and may for other reasons) become smart enough to convert unicode into the charset declared in the MIME part when it is parsing the string version of a message.  In that case, smtplib could use the string parser to parse the DATA payload, and if it parses successfully it can then use the same code path as I'm proposing for send_message to generate the right output depending on whether or not the smtputf8 capability is present.  That would place a new constraint on what was acceptable as a DATA payload, though, so I'm not at all sure it is a good idea.
History
Date User Action Args
2013-12-29 02:06:54r.david.murraysetrecipients: + r.david.murray, barry, macfreek
2013-12-29 02:06:54r.david.murraysetmessageid: <1388282814.72.0.904000235284.issue20084@psf.upfronthosting.co.za>
2013-12-29 02:06:54r.david.murraylinkissue20084 messages
2013-12-29 02:06:54r.david.murraycreate