672571 - Feed messages garbled when being forwarded

Status: RESOLVED DUPLICATE of bug 611666

(SeaMonkey :: MailNews: Composition, defect)

Description

[Igor Velkov]

I't impossible to forward (possible only non-ascii?) a message from feed folder of a "blogs&feeds" account of a mailnews.

Reproduce:
1. have a feed and at least 1 message in "blogs&feeds" subtree
2. read feed message, press "forward" button
new mail window appears, you see a .eml file attached in attachment box
3. save in drafts, or just send message to yourself
4. see letter with attachement like

CjxodG1sPg0KICA8aGVhZD4NCiAgICA8dGl0bGU+Q2xvdWRGUzwvdGl0bGU+DQogICAgPGJh c2UgaHJlZj0iaHR0cDovL2ZlZWRzLmZlZWRidXJuZXIuY29tL3ZtNHJ1Ij4NCiAgPC9oZWFk Pg0KICA8Ym9keSBpZD0ibXNnRmVlZFN1bW1hcnlCb2R5IiBzZWxlY3RlZD0iZmFsc2UiPg0K 

instead of message body in attachement (outer letter shows ok)

If feed messages looks like normal messages - they should allow usage as normal letters.
It some dee is not allowed - it should be clearly showed.

Comment 1

[Stanimir Stamenkov]

Attachment: Sample

The same happens using Thunderbird.

There's something weird with the attached message:

--------------060708050507050202070808
Content-Type: message/rfc822;
 name="Formula One Fantasy - Mercedes' Michael Schumacher.eml"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
 filename="Formula One Fantasy - Mercedes' Michael Schumacher.eml"

X-Mozilla-Keys:
Date: Tue, 19 Jul 2011 08:39:00 GMT
Message-Id: <http://www.formula1.com/news/interviews/2011/7/[e-mail]>
From: <Formula1.com - Latest News>
MIME-Version: 1.0
Subject: Formula One Fantasy - Mercedes' Michael Schumacher
Content-Transfer-Encoding: 8bit
Content-Base: http://www.formula1.com/news/interviews/2011/7/12316.html
Content-Type: text/html; charset=UTF-8

CjxodG1sPg0KICA8aGVhZD4NCiAgICA8dGl0bGU+Rm9ybXVsYSBPbmUgRmFudGFzeSAtIE1l
cmNlZGVzJyBNaWNoYWVsIFNjaHVtYWNoZXI8L3RpdGxlPg0KICAgIDxiYXNlIGhyZWY9Imh0
dHA6Ly93d3cuZm9ybXVsYTEuY29tL25ld3MvaW50ZXJ2aWV3cy8yMDExLzcvMTIzMTYuaHRt
bCI+DQogIDwvaGVhZD4NCiAgPGJvZHkgaWQ9Im1zZ0ZlZWRTdW1tYXJ5Qm9keSIgc2VsZWN0
ZWQ9ImZhbHNlIj4NCiAgICBXaXRoIHNldmVuIHdvcmxkIHRpdGxlcywgOTEgd2lucyBhbmQg
NjggcG9sZSBwb3NpdGlvbnMgZnJvbSBhIEZvcm11bGEgT25lIGNhcmVlciBzcGFubmluZyB0
aHJlZSBkZWNhZGVzLCB3aGVuIGl0IGNvbWVzIHRvIE1pY2hhZWwgU2NodW1hY2hlciB0aGUg
bGluZSBiZXR3ZWVuIGZhbnRhc3kgYW5kIHJlYWxpdHkgYmVjb21lcyB2ZXJ5IGJsdXJyZWQg
aW5kZWVkLg0KCkJ1dCB3aGlsZSBtYXRjaGluZyBoaXMgc3RhdHMgbWF5IGJlIHRoZSBzdHVm
ZiBvZiBmYW50YXN5IGZvciBoaXMgcml2YWxzLCB0aGUgR2VybWFuIGxlZ2VuZCBzdGlsbCBo
YXMgZHJlYW1zIG9mIGhpcyBvd246IE5vcmJlcnQgSGF1ZyBhcyBoaXMgdGVhbSBtYXRlOyBh
IGNpcmN1aXQgaW4gdGhlIEJpZyBBcHBsZSBjb21iaW5pbmcgdGhlIGJlc3QgcGFydHMgb2Yg
U3BhIGFuZCBTdXp1a2E7IGFuZCBoaXMgdmVyeSBvd24gbW90b3Job21lIGJlZC4gU3dlZXQg
ZHJlYW1zIFNjaHVtYWNoZXLChQ0KICA8L2JvZHk+DQo8L2h0bWw+DQoK
--------------060708050507050202070808--

It first says:

Content-Transfer-Encoding: base64

but then raw message headers appear which additionally state:

Content-Transfer-Encoding: 8bit

Comment 2

[Jens Hatlak (:InvisibleSmiley)]

If this also happens with TB, this should be moved to MailNews Core.

Dupe of bug 611666?

Comment 3

[Stanimir Stamenkov]

> Dupe of bug 611666?

Yes, the sample attached there appears to have the same problem (In reply to comment #1):

> Created attachment 546900 [details]
> 
> It first says:
> 
> Content-Transfer-Encoding: base64
> 
> but then raw message headers appear

To clarify, "raw", i.e. clear text appears in the content of the attachment which is supposed to be all BASE64 encoded.