Author r.david.murray
Recipients barry, jfinkels, r.david.murray, sdossey
Date 2010-10-02.04:06:33
SpamBayes Score 5.20774e-09
Marked as misclassified No
Message-id <1285992395.58.0.607747098769.issue1050268@psf.upfronthosting.co.za>
In-reply-to
Content
After working my way through the code I no longer think that parseaddr is working as designed.  I think that this is a bug, and that there is a missing call to quote in getaddrspec.  Attached is a revised set of unit tests and a fix.  The full python test suite passes with this fix in place, but note that initially I made a mistake in the patch and running test_email passed...that is, before the attached tests there were no tests of parseaddr in the email test suite.

I don't know if this patch is safe for backport, but I'm inclined that way.  It is hard to see how 3rd party code could be compensating for this bug, since it looses quoting information that doesn't appear to be algorithmically recoverable.
History
Date User Action Args
2010-10-02 04:06:35r.david.murraysetrecipients: + r.david.murray, barry, sdossey, jfinkels
2010-10-02 04:06:35r.david.murraysetmessageid: <1285992395.58.0.607747098769.issue1050268@psf.upfronthosting.co.za>
2010-10-02 04:06:34r.david.murraylinkissue1050268 messages
2010-10-02 04:06:33r.david.murraycreate