Closed Bug 519699 Opened 16 years ago Closed 6 years ago

Wrong 'From' character encoding in some messages in message list

Categories

(Thunderbird :: Folder and Message Lists, defect)

x86
Windows 7
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: vkondakoff, Unassigned)

References

Details

(Keywords: testcase)

Attachments

(2 files)

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.3) Gecko/20090824 Firefox/3.5.3 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.4pre) Gecko/20090930 Shredder/3.0pre Several messages displayed in message list pane has wrong 'From' character encoding. The same field is displayed in correct encoding in message header pane and in thread summary pane. Here are screenshots: http://www.rugby-forum.ru/temp/enc.jpg http://www.rugby-forum.ru/temp/enc1.jpg And here is a screenshot of the sources of the message in question: http://www.rugby-forum.ru/temp/enc2.jpg Reproducible: Always
Whiteboard: dupeme
Related to bug #508745: probably we can merge this error in only one. I cannot find any similar bug already open.
Would be nice to have a testcase showing this behavior can the reporters save one of the emails showing this in .eml format and attach it to this bug ?
Неrе it is (attached)
Confirmed here on Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.5pre) Gecko/20091019 Lightning/1.0pre Shredder/3.0pre ID:20091019031614
Keywords: testcase
ps: importing the mail testcase in my Inbox local folders with ImportExportTools (Mboximport enhanced) 2.3.0.2
Status: UNCONFIRMED → NEW
Ever confirmed: true
And can we get a screenshot too ?
Whiteboard: dupeme
Attached image screenshot
I see in mail source that there is: Received: from unknown (HELO mx1.valuehost.ru) this sound me familiar (as a know issue, but I'm not sure)
As far as I understand, this bug is related to MSF files. After changing the encoding through preferences, most probably the MSF files are not updated regularly. So, the from field is fetched with wrong encoding from the MSF files where the message itself is read with the correct encoding from the source. Two different occurences I've been faced before, are solved by removing the MSF files to force file recreation.
Reference: Two cases I've been encountered before are the ones listed in Bug 656564.
Additional info: Temporary solution: 1. Set message display default character encoding to ISO-8859-1 2. Shutdown Seamonkey 3. Delete the msf file 4. Start Seamonkey
Valery, okohurgo, do you still see this problem?
Flags: needinfo?(vkondakoff)
Flags: needinfo?(siradanuyelik)
Status: NEW → RESOLVED
Closed: 6 years ago
Component: General → Folder and Message Lists
Flags: needinfo?(vkondakoff)
Flags: needinfo?(siradanuyelik)
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: