Closed
Bug 326265
Opened 18 years ago
Closed 18 years ago
Attachments sent with long file names not accessible in Outlook 2003
Categories
(Thunderbird :: General, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 309566
People
(Reporter: john.hann, Assigned: mscott)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.1) Gecko/20060111 Firefox/1.5.0.1 Build Identifier: version 1.5 (20051201) Attachments sent with long file names are not accessble to users using Outlook 2003. Filename corrupted??? Example message source for problem file attachment: ------------------------------------------------------------ Content-Type: multipart/mixed; boundary="------------060206040902020505060304" This is a multi-part message in MIME format. --------------060206040902020505060304 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit <snip> text message snipped</snip> --------------060206040902020505060304 Content-Type: application/pdf; name*0="e-numera - ClickRSVP Status Report 2005-12 to 2006-01.pdf" Content-Transfer-Encoding: base64 Content-Disposition: inline; filename*0="e-numera - ClickRSVP Status Report 2005-12 to 2006-01.pdf" <snip> base64 encoded file snipped</snip> ------------------------------------------------------------ Note the *0 after the name and filename parameters in the Content-Type and Content-Disposition headers. Is this correct? The same file attachment sent with a small file name works: ------------------------------------------------------------ Content-Type: multipart/mixed; boundary="------------080802080901070408090605" This is a multi-part message in MIME format. --------------080802080901070408090605 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit <snip> text message snipped</snip> --------------080802080901070408090605 Content-Type: application/pdf; name="e-numera - ClickRSVP Status Report.pdf" Content-Transfer-Encoding: base64 Content-Disposition: inline; filename="e-numera - ClickRSVP Status Report.pdf" <snip> base64 encoded file snipped</snip> ------------------------------------------------------------ In Outlook 2003, the attachment shows as ATT03189.dat and, of course, does not open using the associated program (Acrobat Reader). (In TB, the attachment does open because of the MIME type.) Reproducible: Always Steps to Reproduce: 1. Create a file with the same name as the example. 2. Send to a user of Outlook 2003. 3. Ask said user to open message and/or attachment. Actual Results: Attachment is generically named, lost its file extension, and cannot be opened by a non-sophisticated user. Expected Results: Preserved teh file name and extension.
*** This bug has been marked as a duplicate of 309566 ***
Status: UNCONFIRMED → RESOLVED
Closed: 18 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•