User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.8.1.15) Gecko/20080623 Firefox/2.0.0.15 Build Identifier: version 3.0a2pre (2008071103) RFC 2047 6.2. states: "Decoding and display of encoded-words occurs *after* a structured field body is parsed into tokens." but is is done *before* resulting in a problem displaying or replying to emails containing an encoded "From:" header field being decoded as containing an unquoted "," thus being interpreted as a mailbox seperator as in RFC 2822 3.4. This results in a misinterpretation of a legally address in display and reply. The latter generates two or more separate addresses where the leading ones are wrong. Reproducible: Always Steps to Reproduce: 1. compose an email with sender having a display name containing a "," and an umlaut, e.g. common name-format family-name first "Golinski, Björn" <test@example.com> 2. Because of the umlaut RFC 2822 conversion should be applied. This should include the ",", since the conversion can not occur in quoted string ("=?iso-8859-1?Q?Golinski=2C_Bj=F6rn?=" is illegal), resulting in From: =?iso-8859-1?Q?Golinski=2C_Bj=F6rn?= <test@example.com>. Beacuse the "," in encoded there is no need for quotes. 3. displaying this email in TB results in display of two seperate addresses delimited by the "," because the decoding is done first reveiling the unquoted "," and then tokenizing is done. Actual Results: Golinski Björn <test@example.com> Expected Results: Golinski, Björn <test@example.com> or "Golinski, Björn <test@example.com>" depending wether or not quoted should be inserted in this situation. TB also encodes quotes as a safe way, but "Microsoft Exchange V6.5" does not but is still RFC compliant.

This bugs makes it impossible to correctly reply e-mails coming from many correct mail user agents. Another example: From: =?iso-8859-1?Q?Kr=FCger=2C_Matthias?= <nobody@uni-muenster.de> Pressing on Reply, tries to reply to 1st "Krüger" and 2nd "Matthias <nobody@uni-muenster.de>"

> From: =?iso-8859-1?Q?Kr=FCger=2C_Matthias?= <nobody@uni-muenster.de> 2C(",") in encoded-word(atom) case... It's DUP of bug 254519 which is already fixed. > Bug 254519 Incorrect RFC 2047 encoding and decoding: encoded-words not treated as atoms within headers Can you reproduce problem with latest-trunk? > http://ftp.mozilla.org/pub/mozilla.org/thunderbird/nightly/latest-trunk/ > If MS Win user, download win32.zip build. You can test by UNZIP only. > Test with new profile, to avoid corruption of your daily use profile. > Don't forget to set "Leave Messages on Server", if you test POP3. By the way, bug summary of bug 254519 is absolutely correct technically, but how we user can reach bug 254519 when we meet problem you met? :-)

Jano, Rainer ?

As of line 2 of comment 2, all is said and done.

bug 254519 which this is a dup of is fixed.