559532 - When one attached email (.eml) is opened, all attachments from original email are listed

Status: RESOLVED DUPLICATE of bug 736798

(MailNews Core :: Attachments, defect)

Description

[Ludovic Hirlimann [:Usul]]

To reproduce:
1) Select a message, forward as attachment
2 [details] [review]) in the compose window, attach some file from disk, or another message
3) Send to yourself
4) On receipt, select the message, double-click on the forwarded message.

Actual results:
Message window shows the attached file in its attachment bucket

Expected results:
No attachments shown

This is the obverse of bug 35587, but I don't think David's argument against
fixing that bug applies to this bug; there is no convenience offered in showing
the parent's attachments.

Attachment test case is at https://bugzilla.mozilla.or/attachment.cgi?id=201307 ,File name of file attachment is "attachment.pdf" but is not a real pdf
file(HTML file). This is done to force Base64 attachment. Please don't open it
with Adobe Reader, please.

Comment 2

[WADA:World Anti-bad-Duping Agency]

This bug is spinn-off of bug 203570 comment #36. So changing bug summary to Bug 549903' one which is easier to understand problem, for ease of search and tracking.

Comment 3

[Mark Purcell]

I recently sent some .eml files as attachments in an email. Those attached .eml files were themselves emails with attachments. When I double clicked on one of those .eml attachments in the first email I sent, I get *all* the attachments of that parent email, as well as those attachments of the one I had double clicked.

In my opinion double clicking a .eml file should open another window with just that email and its own attachments only.

Also the .eml attachments don't have any meaninful description in the attachment list, they just show as 'Attached Message'. The subject line might be useful here as that description, or at least a method of distinguishing them.

Comment 4

[Jim Porter (:squib)]

This should be fixed by the patch in bug 736798. I'm going to mark this as a dupe, since I've verified that the testcase fails without the patch and passes with it. If it turns out that this is wrong for whatever reason, feel free to undupe.

As an aside: I think this was fixed for a while and then regressed from bug 674473...