Closed Bug 361349 Opened 19 years ago Closed 19 years ago

ver en-US 1.5.0.8 couldn't send attachment file with chinese character correctly

Categories

(Thunderbird :: General, defect)

x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 309566

People

(Reporter: sun, Assigned: mscott)

Details

User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; .NET CLR 1.1.4322) Build Identifier: Thunderbird 1.5.0.8 (Windows/20061025) en-US version 1.5.0.8 (20061025) when I send e-mail with attachment named with chinese characters, I find some mail client (eg. formail, ver<6.0) couldn't display the attachment correctly. I find that "name" line is different between chinese character file name attachment and character ascii file name attachment. with chinese character file name attachment: --------------010703000604070706050000 Content-Type: application/msword; name*=GB2312''%D6%D0%CE%C4%B2%E2%CA%D4%2E%64%6F%63 Content-Transfer-Encoding: base64 Content-Disposition: inline; filename*=GB2312''%D6%D0%CE%C4%B2%E2%CA%D4%2E%64%6F%63 and with ascii character file name attachment: --------------030804000304020903050201 Content-Type: application/pdf; name="817-5504.pdf" Content-Transfer-Encoding: base64 Content-Disposition: inline; filename="817-5504.pdf" and use zh-CN version 1.5.0.8 (20061025), the "name" line is same like ascii character file name attachment : --------------060806000707080102030808 Content-Type: application/msword; name="=?GB2312?B?NjMw19zM5cfQu7u3vbC4LmRvYw==?=" Content-Transfer-Encoding: base64 Content-Disposition: inline; filename="=?GB2312?B?NjMw19zM5cfQu7u3vbC4LmRvYw==?=" Reproducible: Always Steps to Reproduce: 1. use en-US/1.5.0.8/windows XP write an e-mail to myself, with an attachment file named with chinese character. 2. check mail. 3. view message source. 4. find "name*" and "filename*". Actual Results: with foxmail(a e-mail agent), I couldn't find the attachment.
This sounds like a duplicate of bug 309566 (foxmail need to support RFC2231).
Agreed, dupe.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.