Closed Bug 396190 Opened 18 years ago Closed 18 years ago

Forwarding message inline unexpectedly includes its attachment

Categories

(Thunderbird :: Message Compose Window, defect)

x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: jpeek, Unassigned)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.6) Gecko/20070725 Firefox/2.0.0.6 Build Identifier: version 2.0.0.6 (20070728) I received a plain-text MIME message with Content-Type: multipart/mixed. The two parts had Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit and Content-Type: application/ms-tnef; name="winmail.dat" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="winmail.dat" After reading the message, I went to the "Message" menu and chose "Forward As -> Inline". The composition window I got had the inline text from the first part in its body, as I expected. But (as I noticed after I sent it) the message also had the original sender's winmail.dat file (from the second part of the original message) attached to the forwarded message -- as if it were my own winmail.dat. Reproducible: Always Steps to Reproduce: 1.Open the original message to read it 2.Choose Message -> Forward As -> Inline 3.Look in the Aattachments pane fot a winmail.dat attachment Actual Results: The inline message included an attachment Expected Results: No attachment because I asked to forward inline. Or, at least, a dialog box that says "The original winmail.dat attachment is a non-text file. Do you want to attach it to your forwarded message?"
Version: unspecified → 2.0
Forward inline/as attachment only says if you want the text inline in the mail or the original attachment as .eml in the forwarded mail. Both include the original attachment, that's no bug. You course after you hit forward, you can delete the attachment before you forward, but the opposite would be less convenient. ->INVALID
Status: UNCONFIRMED → RESOLVED
Closed: 18 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.