Red Hat Bugzilla – Bug 236741
Broken From because of incorrect RFC 2047 encoding and decoding
Last modified: 2007-11-30 17:12:02 EST
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):
(same on 2.0b2, different but still/more broken on 18.104.22.168rc1)
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?= <email@example.com>
To: "Peter Bieringer" <firstname.lastname@example.org>
Testmail containing Umlaut and commata in From:
2. Send mail
$ cat tmp/mail-umlaut.txt | /usr/sbin/sendmail email@example.com
a) Main mail panel / sender column:
Should: Sureöname, Forename Dr.
b) Mail window / From:
Is: Forename Dr. <firstname.lastname@example.org>
Should: Sureöname, Forename Dr. <email@example.com>
c) after hitting the reply button / recipients:
Is: To: Sureöname
To: Forename Dr. <firstname.lastname@example.org>
Should: To: Sureöname, Forename Dr. <email@example.com>
Seen on mails sent by Outlook.
Long known upstream bug: https://bugzilla.mozilla.org/show_bug.cgi?id=254519
Unfortunately, not fixed until now.
Yup, can confirm that the message is broken in Thunderbird, while mutt displays
it just fine, thank you.
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.
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
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.