Open
Bug 720342
Opened 12 years ago
Updated 2 years ago
None-ASCII "From:" character leads to corruption of the displayed sender
Categories
(Thunderbird :: Folder and Message Lists, defect)
Tracking
(Not tracked)
UNCONFIRMED
People
(Reporter: sophie, Unassigned)
Details
Attachments
(1 file)
33.44 KB,
image/png
|
Details |
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:9.0.1) Gecko/20100101 Firefox/9.0.1 Build ID: 20111220165912 Steps to reproduce: Received a (spam) mail where the "From:" field contained the 'í' character. Actual results: Instead of the "From:" content the name of a adressbook entry is displayed in the message list while the sender in the message tab is displayed correctly. I can reproduce this bug with own mails using a sender adress that cotains this character. Disabling the feature of replacing senders with a adressbook entry let the bug disapear. Deleting the adressbook entry displayed (for all mails the same one) leads to another entry beeing displayed.
Comment 1•12 years ago
|
||
(In reply to quabla from comment #0) Actually, the problem is not only with non-ascii entries, it is with ascii entries as well. In my inbox, I can choose to display the name or e-mail address of some senders. But I cannot do that to another group of senders. It seems that deleting their addressbook entries and creating them again solves the issue, because maybe there are duplicate entries and Thunderbird refers to another copy than the one I change. User Agent: Mozilla/5.0 (X11; Linux i686; rv:9.0) Gecko/20111222 Thunderbird/9.0.1 Application Build ID: 20111222141531
Reporter | ||
Comment 2•12 years ago
|
||
(In reply to Hashem Masoud from comment #1) > In my inbox, I can choose to display the name or e-mail address of some > senders. But I cannot do that to another group of senders. I'm not sure if this is coercible related to the bug that I repoted as a _random_ adressbook entry is displayed instead of the unknown sender.
Updated•12 years ago
|
OS: Mac OS X → All
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•