Open
Bug 779087
Opened 13 years ago
Updated 3 years ago
The sourcecode view is broken when opening mail written in UTF-16 (If mail of charset=UTF-16, View/Message Source shows entire message source data as UTF-16)
Categories
(Thunderbird :: Message Reader UI, defect)
Tracking
(Not tracked)
NEW
People
(Reporter: christof.spies, Unassigned)
Details
Attachments
(1 file)
|
1.58 KB,
application/octet-stream
|
Details |
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20100101 Firefox/14.0.1
Build ID: 20120713134347
Steps to reproduce:
I openend the message with Strg+U to see the sourcecode of the file.
Actual results:
I got only strange characters like this:
剥瑵牮ⵐ慴栺‼獫牡獮祡湳歩祀楣敦潭㸍敬楶敲敤ⵔ漺獰楥獀楣敦潭ഊ剥捥楶敤㨠晲潭潣慬桯獴
汯捡汨潳琠嬱㈷⸰⸰⸱崩ഊॢ礠獡杮楸捥昮捯洠⡐潳瑦楸⤠睩瑨⁅卍呐搠〲㐲䔱㠳㤴〰㌻ഊ॔略Ⱐ㌱⁊畬′〱㈠〸㨵㘺㐴〲〰
䍅協⤍ⵖ楲畳ⵓ捡湮敤㨠䑥扩慮浡癩獤敷琠獡杮楸捥昮捯洍散敩癥携牯洠獡杮楸捥昮捯洠⡛ㄲ㜮〮〮ㅝ⤍ਉ批潣慬桯獴
獡杮楸捥昮捯洠嬱㈷⸰⸰⸱崩
慭慶楳搭湥眬⁰潲琠〲㐩ഊॷ楴栠䱍呐搠祉效灊湙做潑㬠呵攬″ㄠ䩵氠㈰ㄲ‰㠺㔶㨴㌠⬰㈰〠⡃䕓吩ഊ剥捥楶敤㨠晲潭⁛ㄹ㈮ㄶ㠮〮ㄱ㉝
畮歮潷渠嬳㜮㜷⸱㌰⸳㑝⤍ਉ⡁畴桥湴楣慴敤敮摥爺歲慳湹慮獫楹䁩捥昮捯洩ഊॢ礠獡杮楸捥昮捯洠⡐潳瑦楸⤠睩瑨⁅卍呐十搠㈵㉆㜱㠳㤴〰㈻ഊ॔略Ⱐ㌱⁊畬′〱㈠〸㨵㘺㐳〲〰
䍅協⤍੍敳獡来ⵉ䐺‼㔰ㄷ㠱䅁⸳〸〹〷䁩捥昮捯派ഊ䑡瑥㨠呵攬″ㄠ䩵氠㈰ㄲ‱〺㔶㨴㈠⬰㐰」牯洺歲慳湹慮獫楹‼獫牡獮祡湳歩祀楣敦潭㸍獥爭䅧敮琺⁍潺楬污⼵⸰
坩湤潷猠乔‶⸱㬠坏圶㐻瘺ㄴ⸰⤠䝥捫漯㈰ㄲ〷ㄳ⁔桵湤敲扩牤⼱㐮」੍䥍䔭噥牳楯渺‱⸰ഊ呯㨠偡瑲楣欠創晦楮朠㱰牵晦楮杀楣敦潭㸍䌺⁃桲楳瑯映印楥猠㱣獰楥獀楣敦潭㸬ਠ≂敲湤⁓敬扭慮測⁉䍅䘠䝭扈∠㱢獥汢浡湮䁩捥昮捯派ഊ卵扪散琺⁒攺⁁扷敳敮桥楴獮潴楺ഊ剥晥牥湣敳㨠㰵〱ㄳ㘴䈮㠰〰㑀楣敦潭㸠㰵〱ㄳ㝁㘮㌰㥀楣敦潭㸍渭剥灬礭呯㨠㰵〱ㄳ㝁㘮㌰㥀楣敦潭㸍潮瑥湴ⵔ祰攺畬瑩灡牴⽡汴敲湡瑩癥㬍ਠ扯畮摡特㴢ⴭⴭⴭⴭⴭⴭ〴〱〱〸〳〹〶〳〲〶〸〷∍桩猠楳畬瑩⵰慲琠浥獳慧攠楮⁍䥍䔠景牭慴⸍ਭⴭⴭⴭⴭⴭⴭⴰ㐰㠰㌰㤰㘰㌰㈰㘰㠰㜍潮瑥湴ⵔ祰攺⁴數琯灬慩渻桡牳整㵕呆ⴱ㘻潲浡琽晬潷敤ഊ䍯湴敮琭呲慮獦敲ⵅ湣潤楮机‷扩琍ਭⴭⴭⴭⴭⴭⴭⴰ㐰㠰㌰㤰㘰㌰㈰㘰㠰㜍潮瑥湴ⵔ祰攺⁴數琯桴浬㬠捨慲獥琽啔䘭ㄶഊ䍯湴敮琭呲慮獦敲ⵅ湣潤楮机‸扩琍૿︼ഊⴭⴭⴭⴭⴭⴭⴭ〴〱〱〸〳〹〶〳〲〶〸〷ⴭഊ
Expected results:
I'd like to see this:
Return-Path: <skrasnyanskiy@icef.com>
Delivered-To: cspies@icef.com
Received: from localhost (localhost [127.0.0.1])
by sagnix.icef.com (Postfix) with ESMTP id 0242E18394003;
Tue, 31 Jul 2012 08:56:44 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at sagnix.icef.com
Received: from sagnix.icef.com ([127.0.0.1])
by localhost (sagnix.icef.com [127.0.0.1]) (amavisd-new, port 10024)
with LMTP id yIeHpJnYPZoQ; Tue, 31 Jul 2012 08:56:43 +0200 (CEST)
Received: from [192.168.0.112] (unknown [37.77.130.34])
(Authenticated sender: skrasnyanskiy@icef.com)
by sagnix.icef.com (Postfix) with ESMTPSA id 252F718394002;
Tue, 31 Jul 2012 08:56:43 +0200 (CEST)
Message-ID: <501781AA.3080907@icef.com>
Date: Tue, 31 Jul 2012 10:56:42 +0400
From: skrasnyanskiy <skrasnyanskiy@icef.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: Patrick Ruffing <pruffing@icef.com>
CC: Christof Spies <cspies@icef.com>,
"Bernd Selbmann, ICEF GmbH" <bselbmann@icef.com>
Subject: Re: Abwesenheitsnotiz
References: <5011364B.8010004@icef.com> <501137A6.3010109@icef.com>
In-Reply-To: <501137A6.3010109@icef.com>
Content-Type: multipart/alternative;
boundary="------------040101080309060302060807"
This is a multi-part message in MIME format.
--------------040101080309060302060807
Content-Type: text/plain; charset=UTF-16; format=flowed
Content-Transfer-Encoding: 7bit
--------------040101080309060302060807
Content-Type: text/html; charset=UTF-16
Content-Transfer-Encoding: 8bit
ÿþ<
--------------040101080309060302060807--
Updated•13 years ago
|
Group: core-security
Comment 1•13 years ago
|
||
At View/Message Source panel of attached mail in Tb 13.0, if View/Character Encoding is changed to UTF-8, message source is shown as expected, except following text/html part data.
> ��<
Binary of text/html part data in message data stream =
0xFFFE (BOM,little-endian)
+ 0x3C (< in ascii. instead of U+003C in UTF-16)
+ 0x0D0A (CRLF in ascii. instead of U+000D,U+000A in UTF-16)
This corresponds to ÿþ<[CRLF] in data you pasted(0xFFFE of iso-8859-1 = ÿþ).
> http://en.wikipedia.org/wiki/Byte_order_mark#UTF-16
View/Message Source of Tb looks to show UTF-8 data as charset of Content-Type=UTF-16(UTF-16LE in this case).
This bug is also observed with null message body(payload) of text/plain mail or text/html mail.
Data in Tb's local mail folder file.
(a) Other message headers...
Content-Type: text/plain; charset=UTF-16
[CRLF]
[EOF](End of file, no data after Null line as delimiter)
(b) Other message headers...
Content-Type: text/html; charset=UTF-16
[CRLF]
[EOF](End of file, no data after Null line as delimiter)
So, data in text/plain part or text/html part is not relevant to problem.
Confirmig.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Summary: The sourcecode view is brocken when opening this special file → The sourcecode view is brocken when opening mail written in UTF-16
Updated•13 years ago
|
Summary: The sourcecode view is brocken when opening mail written in UTF-16 → The sourcecode view is brocken when opening mail written in UTF-16 (If mail of charset=UTF-16, View/Message source shows "message source data converted to UTF-8" as UTF-16)
Updated•13 years ago
|
Summary: The sourcecode view is brocken when opening mail written in UTF-16 (If mail of charset=UTF-16, View/Message source shows "message source data converted to UTF-8" as UTF-16) → The sourcecode view is brocken when opening mail written in UTF-16 (If mail of charset=UTF-16, View/Message Source shows entire message source data as UTF-16)
Updated•13 years ago
|
Summary: The sourcecode view is brocken when opening mail written in UTF-16 (If mail of charset=UTF-16, View/Message Source shows entire message source data as UTF-16) → The sourcecode view is broken when opening mail written in UTF-16 (If mail of charset=UTF-16, View/Message Source shows entire message source data as UTF-16)
Comment 2•13 years ago
|
||
Windows 2003 Server with TB 16.0.2: I can confirm this problem. In addition: when manually trying to switch the source code view to UTF-16 encoding, an error message pops up:
[Exception... "Component returned failure code: 0x805e0006 [nsIWebNavigation.reload]" nsresult: "0x805e0006 (<unknown>)" location: "JS frame :: chrome://global/content/bindings/browser.xml :: reloadWithFlags :: line 103" data: no]
The whole email message isn't displayed at all in normal view here, so the source code view is really secondary :) - I have created the UTF-16 Email myself and sent to myself (imap). It appears empty in the sent folder and the received one in the inbox, too.
Comment 3•13 years ago
|
||
Error message in comment 2 is in Bug 814382
Moreover you cannot reply to that kind of email. The recipient will receive an empty message.
To reproduce it's quite simple. You just have to export any key from the windows registry. The reg file generated is in UCS-2 Little Endian (UTF-16). Compose a mail and add this attachment. If the receiver reply, you won't see what he wrote.
Updated•3 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•