264019 - email address mangled if it contains local characters (From:)

Status: RESOLVED DUPLICATE of bug 147346

(Thunderbird :: General, defect)

Description

[Simon Bock]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5) Gecko/20031007 MultiZilla/1.6.4.0b
Build Identifier: Mozilla Thundrbird version 0.7.2 (20040707) - BTW why doesn't this report a real ID line ?

Some eMail I get cannot be replied to directly because the From: address is
mangled, despite legal formatting, displayed & handled correctly in all other
mailers I tried.
An example From: address containing localized characters as

From: [e-mail] (Test B=?ISO-8859-1?B?9mhtKQ==?=)

is displayed as
Test Böhm <""\"\"test\"\"@netscape.net )>
which is mangled up to unusability. This mangling is not only true for
displaying, but also for reply and add to address book.

Probably this is not only limited to From: addresses, but triggers a bug in the
whole Thunderbird address handling (maybe wanting to do to much for the user ?),
since it seems related to bug # 235070.


Reproducible: Always
Steps to Reproduce:
Display eMail with From: address
From: [e-mail] (Test B=?ISO-8859-1?B?9mhtKQ==?=)
e.g. exchange the From: line of a locally stored email to the line indicated above.

Actual Results:  
When opened, the mangled address will be visible. The name "Test Böhm" will be
correct, but the address unsuitable / corrupt.


Expected Results:  
Correct usable email address for reply or address book.
It does not harm if the displayed name might be corrupted - but to corrupt the
address is bad.

Comment 1

[OstGote!]

Related to Bug 254519?

Comment 2

[Mike Cowperthwaite]

Maybe.  The parentheses are "legal" in the sense of defining a comment in the 
string.  (Mozilla does not handle these completely correctly: bug 147346.)
However, the RFC-2047 quoted portion *also* contains a parenthesis -- bad 
formatting; when decoded, it appears as:
  [e-mail] (Test Böhm))
                            ~~~~     <- these four characters are encoded

As with bug 254519, the fact that the encoded characters are not treated as an 
atom is an issue -- if that were done correctly, the extra parenthesis would not 
be a problem.
The fact that the resulting address is therefore mangled with escaped quotes is 
more like bug 193791 and bug 208018.

Comment 3

[Joshua Cranmer [:jcranmer]]

per comment 2 and my own testing, the issue here is that meeting )) causes the parser to confuse itself. Duplicate of bug 147346, as it's the comment problem that's stinging the issue.