Closed
Bug 195464
Opened 21 years ago
Closed 21 years ago
Attachment won't open for message in IMAP mailbox if attachment filename contains #
Categories
(MailNews Core :: Attachments, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: fischer-michael, Assigned: mscott)
Details
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3b) Gecko/20030210 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3b) Gecko/20030210 I have a message in an IMAP mailbox with an attachment of type application/msword named "Reading_List_Unit_#3.doc". When I try to open it, either by double-clicking on its name in the "Attachments:" box or by right-clicking and selecting "Open", nothing happens. However, "Save As" works normally, giving a file selector box with the proper name filled in. This same attachment opens fine under Mozilla 1.3a. This same attachment opens fine if the email message is copied to a mailbox in Local Folders. This same attachment opens fine from the IMAP mailbox if I first go into the mailbox with a text editor and remove the # from the file name, both in the Content-Type and Content-Disposition lines. Reproducible: Always Steps to Reproduce: 1.Read IMAP mail message with attachment containing "#" in file name. Name of attachment shows in Attachments box. 2.Double-click on name, or right-click and select open. 3. Actual Results: Nothing happens. Expected Results: Should have opened a dialog box asking what to do with this file. Here is the Mime header to the attachment in question: Content-Id: <p05111a02ba84c0b2c4c9@[130.132.57.54].0.0> Content-Type: application/msword; name="Reading_List_Unit_#3.doc" ; x-mac-type="5738424E" ; x-mac-creator="4D535744" Content-Disposition: attachment; filename="Reading_List_Unit_#3.doc" Content-Transfer-Encoding: base64
Comment 1•21 years ago
|
||
I think this was fixed a while ago - could you try a more recent build?
Reporter | ||
Comment 2•21 years ago
|
||
I tried it in Mozilla 1.6. It works fine now.
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → FIXED
Comment 3•21 years ago
|
||
Bug/patch that fix this unidentified. ->WORKSFORME
Status: RESOLVED → UNCONFIRMED
Resolution: FIXED → ---
Updated•21 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago → 21 years ago
Resolution: --- → WORKSFORME
Updated•20 years ago
|
Product: MailNews → Core
Updated•16 years ago
|
Product: Core → MailNews Core
You need to log in
before you can comment on or make changes to this bug.
Description
•