298288 - Forwarding attachments changes filenames to (null).eml

Status: RESOLVED DUPLICATE of bug 188108

(Thunderbird :: Message Compose Window, defect)

Description

[Roland Neilands]

User-Agent:       Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1)
Build Identifier: version 1.0.2 (20050317)

Forwarding an email with multiple attached emails changes all the attachment 
names to "(null).eml", instead of the original filenames, which were displayed 
correctly in the preview & message windows.
XML attachments are lost completely.

Reproducible: Always

Steps to Reproduce:
1. Receive an email with multiple email attachments
2. Click on Forward 


Actual Results:  
All .eml filenames are changed to (null).eml
No .xml attachments are included at all.

Expected Results:  
Kept original filenames.
Attached XML files

Default theme

Comment 1

[Roland Neilands]

Attachment: Example screenshot

Comment 2

[Adam Guthrie]

Are you using any extensions? This works for me on the latest trunk. I e-mailed
a message with three files attached -- foobar.xml, foo.xml, and foo.txt. I
recieved that message just fine. Then I forwarded it. It sent the original
message (testcase) and all the attachments with the proper extensions just fine. 

Try this with a new profile and no extensions?

Comment 3

[Roland Neilands]

Attachment: original email screenshot (before forwarding)

No extensions either.
Single xml file attachments forward OK. .eml files are forwarded from Outlook.

Comment 4

[Mike Cowperthwaite]

(In reply to comment #0)
> Forwarding an email with multiple attached emails changes all the attachment 
> names to "(null).eml", instead of the original filenames, which were displayed 
> correctly in the preview & message windows.

This sounds like a dupe of bug 188108, except for that last part -- the case 
where I have been able to reproduce this has no filename associated with the 
original attachment.  See bug 277913 comment 0 for an example of original and 
morphed headers that exhibit this bug.

If you have a sample message with an XML attachment that goes missing, please 
save it as a .EML file and attach it to this bug; I can't reproduce that part of 
the symptom.

Comment 5

[Roland Neilands]

Attachment: Original .eml. Forward this to reproduce bug

Comment 6

[Mike Cowperthwaite]

OK, this is a dupe.  The XML attachments in the original message are not 
actually attached *to* that original message; rather, each XML file is attached 
to one of those message/rfc822 attachments.  Mozilla (& TB) have known problems 
in this area: nested attachments (and attachments of a parent message) are 
displayed in the message window as if they belonged to the message being viewed 
-- bug 35587 and bug 203570.

However, when you forward the message, the compose window only shows the actual 
message/rfc822 attachments (now renamed); the XML sub-attachments are still in 
place, just not displayed in the compose window.  You can check this easily by 
sending the forwarded message, then viewing the result in the Sent folder.

And the (null) renaming you're seeing is the same as the dupe -- the 
message/rfc822 attachments were not provided with filenames, so the message 
subject is used instead; and Moz/TB is unnecessarily providing the bogus 
filename when forwarding.

*** This bug has been marked as a duplicate of 188108 ***

Comment 7

[Roland Neilands]

OK thanks for the response. I would say displaying nested attachments is a 
feature then & would prefer them marked as such rather than not shown.
The forwarding problem is more serious as the files can't be distinguished and 
will continue to frustrate. Why can't the original subject be used? Is there 
some workaround? (none mentioned in bug 188108) There are numerous other minor 
forwarding bugs, but this is the most annoying.

PS Why can't TB open the .eml files in the compose screen, but it can in the 
inbox/sent items? Tries to use Outlook Express, which is installed but has 
never been used.

Comment 8

[Mike Cowperthwaite]

(In reply to comment #7)
> Why can't the original subject be used? 

This is the wrong solution.  The fix is to not try to supply a filename at all.

> Is there some workaround? 

None that I'm aware of.


> PS Why can't TB open the .eml files in the compose screen, but it can in the 
> inbox/sent items? Tries to use Outlook Express, which is installed but has 
> never been used.

This is a separate issue.  You can look at   Tools | Options | Attachments 
(if you're using a trunk build, go one step further to View & Edit Actions) and 
see if there is an entry for the EML extension; if there is, delete it.  There 
are definitely some problems in this area, even for MIME types or extensions 
that shouldn't be handled automatically; your query has only just caused me to 
look at the .EML case, and there is something wrong there, as well.  I'll 
investigate further, and you let know if I open a bug about the problem.