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 eric.araujo
Recipients eric.araujo, r.david.murray
Date 2010-07-17.14:35:57
SpamBayes Score 0.0010309018
Marked as misclassified No
Message-id <>
This behavior does not seem right to me:

parsing 'merwok'
 expected ('merwok', '')
 got      ('', 'merwok')

parsing 'merwok wok@rusty'
 expected ('', 'wok@rusty')
 got      ('', 'merwokwok@rusty')

(Generated with a small script just doing a loop and prints, not attached because boring.)

Are my expectations wrong? I don’t know if a string like “merwok” in my first example is a legal address in the relevant RFCs; Mark Sapiro replied in msg110556 that it could be consistent with most MUAs/MTAs.

I don’t know either if the folding done in the second example is okay; I’d like an exception here, or if parseaddr is designed to never fail, empty strings to indicate failure. I’m also okay with “garbage in, garbage out” as answer.
Date User Action Args
2010-07-17 14:36:00eric.araujosetrecipients: + eric.araujo, r.david.murray
2010-07-17 14:35:59eric.araujosetmessageid: <>
2010-07-17 14:35:57eric.araujolinkissue9286 messages
2010-07-17 14:35:57eric.araujocreate