Closed
Bug 716220
Opened 13 years ago
Closed 13 years ago
Thunderbird makes bad guess if “from:” header is not correct.
Categories
(Thunderbird :: Folder and Message Lists, defect)
Thunderbird
Folder and Message Lists
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 669925
People
(Reporter: FeuerFliege, Unassigned)
Details
Attachments
(1 file)
690 bytes,
application/octet-stream
|
Details |
User Agent: Mozilla/5.0 (Windows NT 5.1) AppleWebKit/535.2 (KHTML, like Gecko) Chrome/15.0.872.0 Safari/535.2
Build ID: 20120106042007
Steps to reproduce:
Make sure that the option “Show only display name for people in my address book” is enabled (Options → Advanced → Reading & Display).
Have an email where the “from:” header contains no email address (usually spam mail) AND a non-ASCII character is present (I’ll attach a file with »From: Big Bäd Spammer«).
View the mail in the thread pane.
Actual results:
Thunderbird showed the name of a contact from the dress book instead the right one. This increases the risk to trust and open the mail, but mostly it is annoying.
The contact shown has at least one email address field in the address book empty. My guess is, that TB stumbles upon the non-ASCII character and searches the address book for a contact with "" as an email address.
Expected results:
Thunderbird should not make such bad guesses.
Reporter | ||
Updated•13 years ago
|
OS: Windows XP → All
Hardware: x86 → All
Version: 9 → Trunk
Reporter | ||
Comment 1•13 years ago
|
||
I’ve just tested some From headers:
»From: Big Bad Spammer« → TB shows “Big Bad Spammer”
»From: Big Bäd Spammer« → TB shows a contact form the address book
»From: Big Bäd Spammer a@b.invalid« → TB shows contact from the address book
»From: Big Bäd Spammer <a@b.invalid>« → TB shows “Big B�d Spammer”
»From: « → Thunderbird shows nothing at all.
Comment 2•13 years ago
|
||
Dupe of bug 669925, probably.
Reporter | ||
Comment 3•13 years ago
|
||
Yes, it seems to be a dupe, thx.
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•