Bug 236741

Summary: Broken From because of incorrect RFC 2047 encoding and decoding
Product: [Fedora] Fedora Reporter: Peter Bieringer <pb>
Component: thunderbirdAssignee: Gecko Maintainer <gecko-bugs-nobody>
Status: CLOSED UPSTREAM QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 6CC: mcepl
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2007-05-22 13:53:01 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Peter Bieringer 2007-04-17 14:06:07 UTC
Description of problem:
Displaying of "From" address is broken, if encoded because of use of Umlauts and
a commata is in use.

Version-Release number of selected component (if applicable):
thunderbird-1.5.0.10-1.fc6
(same on 2.0b2, different but still/more broken on 2.0.0.0rc1)

How reproducible:
always

Steps to Reproduce/ Actual results / Expected results:

1. Create test mail:

$ cat tmp/mail-umlaut.txt
From: =?iso-8859-1?Q?Sure=F6name=2C_Forename__Dr=2E?= <pb>
To: "Peter Bieringer" <pb>
Subject: Umlauttest

Testmail containing Umlaut and commata in From:
<<END

2. Send mail
$ cat tmp/mail-umlaut.txt | /usr/sbin/sendmail pb

Results:
a) Main mail panel / sender column:
Is:     Sureöname
Should: Sureöname, Forename Dr.

b) Mail window / From:
Is:     Forename Dr. <pb>
Should: Sureöname, Forename Dr. <pb>

c) after hitting the reply button / recipients:
Is:     To: Sureöname
        To: Forename Dr. <pb>
(2 entries!!!!)

Should: To: Sureöname, Forename Dr. <pb>

  

Additional info:

Seen on mails sent by Outlook.

Long known upstream bug: https://bugzilla.mozilla.org/show_bug.cgi?id=254519
Unfortunately, not fixed until now.

Comment 1 Matěj Cepl 2007-05-22 13:31:27 UTC
Yup, can confirm that the message is broken in Thunderbird, while mutt displays
it just fine, thank you.

Comment 2 Matěj Cepl 2007-05-22 13:53:01 UTC
We found that this bug has been already registered in the upstream database
(https://bugzilla.mozilla.org/show_bug.cgi?id=254519) and believe that it is
more approriate to let it be resolved upstream.

Red Hat will continue to track the issue in the centralized upstream bug
tracker, and will review any bug fixes that become available for consideration
in future updates.

Thank you for the bug report.


Comment 3 Peter Bieringer 2007-05-22 13:58:30 UTC
BTW: makes it sense to close bugs with "CLOSED UPSTREAM" while it's known that
the bug isn't fixed in upstream yet? Probably a better status would be "WAITFOR
UPSTREAM".

Comment 4 Matěj Cepl 2007-05-22 23:11:34 UTC
It is not "CLOSED UPSTREAM", but CLOSED (reason being UPSTREAM), take a look at
the definition https://bugzilla.redhat.com/bugzilla/page.cgi?id=fields.html#upstream

And concerning WAITFOR UPSTREAM -- well, we are not that anxious, when it will
be fixed upstream, it will come to us automagically, so for us working on this
bug is basically finished.