[Email-SIG] encoding To headers
bkirsch at osafoundation.org
Tue Jan 18 20:08:39 CET 2005
Count me in!
A robust email address parser and improved header support sound like
worth while causes to me.
Brian Kirsch - Email Framework Engineer
Open Source Applications Foundation
543 Howard St. 5th Floor
San Francisco, CA 94105
On Jan 15, 2005, at 8:22 AM, Barry Warsaw wrote:
> On Wed, 2005-01-05 at 05:55, Stuart Bishop wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>> Wichert Akkerman wrote:
>> | It's been a month since I posted this; can I safely assume nobody
>> | the answer or is it just not possible?
>> I never saw your original message sorry.
>> There is code that will correctly encode and decode email addresses at
>> http://stuartbishop.net/Software/EmailAddress. It handles the case you
>> mention, as well as handling Unicode domain names if you should ever
>> actually see one.
>> |>I am trying to figure out how to use an 'internationaled' To-header
>> |>not succeeding so far. The basic documented approach does not work:
>> |>>>>mail["From"]=email.Header.Header(, "utf-8")
>> |>>>>print mail.as_string()
>> |>From: =?utf-8?b?dMODwrhzdGk=?=
>> |>this is not allowed by the RFCs: the address must not be encoded.
>> |>quoted-printable would fix this but I can not find any documentation
>> |>as to how to do that.
>> |>All current documentation mentions that specifying encoders is
>> |>deprecated, but without setting them the email module seems to
>> insist on
>> |>using base64 encoding.
> I wonder if it makes sense to try to fold this into the email package?
> On a related note, Pycon2005 is coming up soon and I will be attending.
> There are four days of sprints preceding the conference and last year,
> Anthony, Thomas and I sprinted on the new feed parser. While we didn't
> finish that work during the sprint, I think that session was more
> successful than my following Mailman3 sprint. The fruits of the email
> sprint are evident in the new FeedParser that's part of email 3.0.
> Does anybody want to sprint on the email package again this year? Some
> things we could work on include:
> - An RFC compliant email address parser
> - Adding better header support
> - Adding a persistency and/or external storage API, or developing a
> relational model for storing email messages.
> - Another round of API fixes, and/or sprinting on bugs.
> - Switching the Python stdlib away from deprecated modules such as
> Let's gather some thoughts here and if there's enough interest, I'll
> sign up for a sprint at Pycon2005.
> Email-SIG mailing list
> Email-SIG at python.org
> Your options:
-------------- next part --------------
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)
-----END PGP SIGNATURE-----
More information about the Email-SIG