Closed Bug 296560 Opened 20 years ago Closed 19 years ago

Attachments within attachments mangled when saved using save as/all

Categories

(Thunderbird :: Mail Window Front End, defect)

defect
Not set
major

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: jeremyp, Assigned: mscott)

References

Details

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en) AppleWebKit/412 (KHTML, like Gecko) Safari/412
Build Identifier: Thunderbird/1.0.2

Saving attachments from within an email attached to the top-level message does not actually create the 
desired file, but rather it creates a file that only contains the following two lines:

</body>
</html>

If, however, you choose "open" on the attachment, and then you choose "save to disk" from the "open 
with" dialog box, it will save properly. The problem also does not occur if you right-click on the 
attachment from the top-level message and choose save as. However, you can only do that if "Display 
attachments inline" is turned on.


Reproducible: Always

Steps to Reproduce:
1. send yourself an email with an attachment.
2. forward said message _as_an_attachment_ to yourself
3. open the resulting email
4. open the _message_ attachment
5. from the inner message's window, right-click on the attachment and choose "save as..."
6. save it somewhere

Actual Results:  
The resulting file will contain the body and html tags described above.

Expected Results:  
The file should be whatever was in the attached email.

 I have confirmed this with PDF and EPS files, but I'm guessing it happens with other types as well.
I have this on Linux and windows as well with 1.0.6. This is only reproducable
when "Display Attachments Inline" is off.
*** Bug 303064 has been marked as a duplicate of this bug. ***
With 1.0.6 and 1.5.0.2, Win2K, I'm unable to save a PDF file attached to a forwarded message, at all -- I get an error "Please check the name of your attachment".  However, this is working correctly with 2a1 and 3a1 builds -- I think due to the fix at bug 203570, just as bug 206278.  The next release with that fix will be TB 2.0.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.