[ python-Bugs-1025395 ] email.Utils.parseaddr fails to parse valid addresses

[SourceForge.net]

Bugs item #1025395, was opened at 2004-09-09 16:43
Message generated for change (Settings changed) made by akuchling
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1025395&group_id=5470

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Python Library
Group: Python 2.3
Status: Open
Resolution: None
Priority: 5
Submitted By: Charles (melicertes)
>Assigned to: Barry A. Warsaw (bwarsaw)
Summary: email.Utils.parseaddr fails to parse valid addresses

Initial Comment:
email.Utils.parseaddr() does not successfully parse a
field value into a (comment, address) pair if the
address contains a source route with more than one hop.

i.e., it is successfully parses this:

  "God" <@hop1.org:jeff at spec.org>

to get the address <jeff at spec.org>, but it fails to do
the same if supplied with a 2-hop source route:

  "God" <@hop1.org, at hop2.net:jeff at spec.org>

In this case, it gets the comment ("God") right, but
fails to extract the address.

Multi-hop source routes, while deprecated, are still
valid in rfc2822.



----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1025395&group_id=5470