Closed
Bug 310592
Opened 19 years ago
Closed 19 years ago
Wrong file name when attaching file located in directory containing a # symbol
Categories
(Thunderbird :: Message Compose Window, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 243504
People
(Reporter: bpierre, Assigned: mscott)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.12) Gecko/20050915 Firefox/1.0.7 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.12) Gecko/20050915 Firefox/1.0.7 If I attach a file that is located in a directory or sub directory of a directory with a # symbol in its name, then the attached file is sent out as the first part of the directory name before the # symbol. Example, if I attach file c:\drawings\lot #9\asimpledrawing.dwg The filename sent to the recipients will be "lot". The mimetype is set properly and the data within the file is correct. But since most mail clients use extension to decide what program opens it, or they save the file then open it, it causes the recipients to not be able to open the file. Reproducible: Always Steps to Reproduce: 1.Attach file located within a directory with a # symbol in its name 2.Send file 3.Wait for the person who recieved the e-mail to complain. :) Actual Results: Attached file had the filename of the first part of the directory before the # Expected Results: It should've named the file to the same name as I had attached.
Comment 1•19 years ago
|
||
Reporter, which version are you using ? It's supposed to be fixed in Thunderbird 1.5 beta 1, see bug 243504.
| Reporter | ||
Comment 2•19 years ago
|
||
(In reply to comment #1) > Reporter, which version are you using ? It's supposed to be fixed in Thunderbird > 1.5 beta 1, see bug 243504. I'm using the most recent binary available from the website, 1.0.7 (20050923)
Comment 3•19 years ago
|
||
*** This bug has been marked as a duplicate of 243504 ***
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.
Description
•