Closed
Bug 291502
Opened 20 years ago
Closed 20 years ago
Attachment File name or path truncated if thier is a # sign.
Categories
(Thunderbird :: Message Compose Window, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 239192
People
(Reporter: daniel, Assigned: mscott)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.5) Gecko/20041107 Harrison Conference Center at Glen Cove/1.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.5) Gecko/20041107 Harrison Conference Center at Glen Cove/1.0
When using the command line to send an email with attachment, Thunderbird cuts
off everything after the "#" sign.
The file is succesfully attached with no errors poping up. When sending email
it complains that it can not find the file.
Reproducible: Always
Steps to Reproduce:
Create a command like the one below:
"C:\Program Files\Mozilla Thunderbird\thunderbird.exe" -compose
"to='knXXXb-anXXXew@XXXX.com',subject=test,attachment='file:///C:\Documents and
Settings\danny\Local Settings\Temp\ADI Upload PC#123123123
(10-30-2003)-10506.xls',body=See attached File."
Actual Results:
Thunderbird attaches the file specified in the atachment path, but the filename
is truncated at the # sign.
When you try to preview the attachment, nothing happens (double click or open)
When you send the messege an error appears stating that it can not find the
file. The path in error message is to the truncated file.
Expected Results:
The # sign is part of the file name and the file atachment path should not be
cut off at it.
I was creating a VB Macro in Excel 2000 to have a workbook mailed as an
attachment in Thunderbird becuase the built in function (Send Workbook as
attachment) is not functional with Thunderbird.
Comment 1•20 years ago
|
||
Problem has already been fixed, will be part of Thunderbird 1.1. Current
nightly builds include the fix now.
*** This bug has been marked as a duplicate of 239192 ***
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•