Closed Bug 485800 Opened 15 years ago Closed 15 years ago

RFC2047 encoded From: yields garbled To: and attribution in reply - original message in .eml file

Categories

(MailNews Core :: Composition, defect)

x86
Windows XP
defect
Not set
minor

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 314351

People

(Reporter: mark, Unassigned)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.8) Gecko/2009032609 Firefox/3.0.8 (.NET CLR 3.5.30729)
Build Identifier: version 2.0.0.21 (20090302)

When opening a message from a file as opposed to a mailbox, and that message contains an RFC 2047 encoded From: header and the body of that message is charset=utf-8, a reply to that message gets a garbled To: and attribution.

Here's an example message
-----------------------------------------------------
From: Stefan =?utf-8?Q?F=C3=B6rster?= <xxx@example.com>
To: zzz@invalid
Date: Fri, 12 Oct 2007 07:39:05 +0200
Subject: A subject
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit

Now is the time to have a party
-----------------------------------------------------

If that message is in a file and opened in Tbird and replied to, the To: in the composition window is

Stefan F������������������������

and the attribution is

Stefan F������������������������ wrote:

If the Content-Type is changed to

Content-Type: text/plain; charset="iso-8859-1"

The To: and attribution in the reply are correct.

This does not occur with messages in mailboxes.

Reproducible: Always

Steps to Reproduce:
1.Open a .eml file containing a message with an RFC2047 encoded From: and a utf-8 body.
2.Reply to the message

Actual Results:  
To: Stefan F������������������������
...
Stefan F������������������������ wrote:

Expected Results:  
To: Stefan Förster <xxx@example.com>
...
Stefan Förster wrote:

It is apparently only the charset of the body that affects this. Of the following 4 messages, the first two give the garbled result and the second two do not.
--------------------------------------------------
From: Stefan =?iso-8859-1?Q?F=F6rster?= <xxx@example.com>
To: zzz@invalid
Date: Fri, 12 Oct 2007 07:39:05 +0200
Subject: A subject
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit

Now is the time to have a party
----------------------------------------------------
From: Stefan =?utf-8?Q?F=C3=B6rster?= <xxx@example.com>
To: zzz@invalid
Date: Fri, 12 Oct 2007 07:39:05 +0200
Subject: A subject
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit

Now is the time to have a party
----------------------------------------------------------
From: Stefan =?iso-8859-1?Q?F=F6rster?= <xxx@example.com>
To: zzz@invalid
Date: Fri, 12 Oct 2007 07:39:05 +0200
Subject: A subject
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit

Now is the time to have a party
-----------------------------------------------------
From: Stefan =?utf-8?Q?F=C3=B6rster?= <xxx@example.com>
To: zzz@invalid
Date: Fri, 12 Oct 2007 07:39:05 +0200
Subject: A subject
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit

Now is the time to have a party
Component: Message Compose Window → Composition
Product: Thunderbird → MailNews Core
QA Contact: message-compose → composition
CONFIRMED with Tb 2.0.0.21 on MS Win-XP. eml file only problem. If View/Character Encoding is changed to iso-8859-1 before reply, problem doesn't occur. No problem if saved in mail folder file. 

WORKSFORME with Tb Trunk 2009/5/27 build.
> Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1pre) Gecko/20090527 Shredder/3.0b3pre

Seems already fixed problem.
Can you find similar bug in Dependency Tree for meta Bug 269826?
Blocks: 269826
Status: UNCONFIRMED → NEW
Ever confirmed: true
Summary: RFC2047 encoded From: yields garbled To: and attribution in reply - original message in file → RFC2047 encoded From: yields garbled To: and attribution in reply - original message in .eml file
Probably DUP of Bug 314351 to which you already posted comments last year.
(In reply to comment #2)
> Probably DUP of Bug 314351 to which you already posted comments last year.

Sorry about that. Clearly I forgot my comments to Bug 314351 :(
Closing as DUP of Bug 314351.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → DUPLICATE
No longer blocks: 269826
No longer depends on: 314351
You need to log in before you can comment on or make changes to this bug.