294495 - Decode Embedded Message (message/rfc822) also when it has "Content-Transfer-Encoding: base64"

Status: RESOLVED EXPIRED

(Thunderbird :: General, enhancement)

Description

[L. Willms]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; de-AT; rv:1.7.5) Gecko/20041217
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; de-AT; rv:1.7.5) Gecko/20041217

See bug 293475

An attached message with "Content-Type: message/rfc822" is not shown in
Thunderbird (1.02) when the body part in question is encoded as
"Content-Transfer-Encoding: base64". 

There is at least one email program "out there" which does forward embedded
messages in that way, and all other eMail-client programs which I have been able
to test with do decode such a body part without complaints and without problems:
PMMail, The Bat!, KMail, Outlook, and Outlook Express. 

According to the general rule "be strict on sending, but generous on receiving",
Thunderbird should be able to decode such body part. Processing body parts is a
recursive process anyway. 
 


Reproducible: Always

Steps to Reproduce:
1. Receive a message with an attached message encoded as base64
2. Open that message
3. Click on the icon representing the attachment 

Actual Results:  
an message window is opened, but no header nor content are being shown. 

Expected Results:  
Taht the embedded message is being decoded and shown 

See bug 293475

Comment 1

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 2

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.