Closed Bug 363673 Opened 18 years ago Closed 18 years ago

Wrong display of Recipient in message list

Categories

(Thunderbird :: General, defect)

x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 273884

People

(Reporter: thbley, Assigned: mscott)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1) Gecko/20061010 Firefox/2.0 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1) Gecko/20061010 Firefox/2.0 When I have a Recipient that contains quotes, e.g. To: "Paul Ling" <drpaulling@msn.com> it gets displayed as "Paul Ling" in the message list and Paul Ling <drpaulling@msn.com> in the message view. The recipient should be displayed as Paul Ling in the message list. Stripping the quotes should be done after decoding the mime string, e.g. mail source To: =?iso-8859-1?Q?=22Rog=E9rio_A._Gon=E7alves=22?= <rag@db1.com.br> gets displayed as ""Rogério A. Gonçalves"" in the message list. These problems stay when I forward a message, e.g. I get: To: "Rogério A. Gonçalves" <rag@db1.com.br> in the text of the forwarded message. When a sender name contains quotes, they are stripped correctly, e.g. mail source From: "GMail" <luigia.fassina@gmail.com> is displayed as GMail in the message list and the message view. Version is Thunderbird 2.0 beta 1 (20061211). Reproducible: Always Steps to Reproduce: 1. Mail source: To: "Paul Ling" <drpaulling@msn.com> 2. Mail source: To: =?iso-8859-1?Q?=22Rog=E9rio_A._Gon=E7alves=22?= <rag@db1.com.br> 3. Watch the message list, click forward on the message
Version: unspecified → 2.0
Failing to strip the quotes in the Recipient column is bug 273884. In the case of the MIME-encoded header, we're not supposed to strip the quotes that are part of the MIME-encoding. We're also not supposed to *add* the quotes within the MIME-encoding, which problem is mentioned in bug 254519, altho that bug is far more focused on the problems with *decoding* such headers.
Status: UNCONFIRMED → RESOLVED
Closed: 18 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.