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� (415) 946-3056� http://www.osafoundation.org
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 knows
| 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 but
|>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. Using
|>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.
|>
|>Wichert.
Stuart,
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 rfc822.
Let's gather some thoughts here and if there's enough interest, I'll sign up for a sprint at Pycon2005.
-Barry
_______________________________________________
Email-SIG mailing list
[email protected]
Your options: http://mail.python.org/mailman/options/email-sig/ bkirsch%40osafoundation.org
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (GNU/Linux)
iQCVAwUAQelDOXEjvBPtnXfVAQJ6iAP/cq2AGbgF6iKAK4k69RqnsCurxl7Hv4XG qzw8pmYYYgIU9HNrZghu5kYEbhWYlmP8WlvRJ3vZAYbCEGJ/Anw2xB0jYSEC+wP3 4z0CWoWz7RiTAmyPdNcjRWe6+6w4nMZvoDSsCAb5Gg/1e4eZ56TqJt30264XntB6 /kKorI2CiOg= =/ah1 -----END PGP SIGNATURE-----
_______________________________________________ Email-SIG mailing list [email protected] Your options: http://mail.python.org/mailman/options/email-sig/archive%40mail-archive.com
