➜

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 exarkun
Recipients exarkun, iElectric
Date 2010-04-21.19:24:18
SpamBayes Score 0.0003939272
Marked as misclassified No
Message-id <1271877860.23.0.943541494799.issue8489@psf.upfronthosting.co.za>
In-reply-to
Content 
SMTP (RFC 2821) doesn't support non-ASCII envelope addresses.  A better behavior here would be for connection.login to raise a ValueError or a TypeError whenever a non-str is passed in.

RFC 5336, though, adds the UTF8SMTP extension, which adds support for UTF-8 encoded unicode mailboxes.  If the server advertises the UTF8SMTP capability, then smtplib could encode unicode using UTF-8 and pass it on.

This is really a feature request (RFC 5336 support), not a bug.
History
Date User Action Args
2010-04-21 19:24:20exarkunsetrecipients: + exarkun, iElectric
2010-04-21 19:24:20exarkunsetmessageid: <1271877860.23.0.943541494799.issue8489@psf.upfronthosting.co.za>
2010-04-21 19:24:19exarkunlinkissue8489 messages
2010-04-21 19:24:18exarkuncreate