305377 - Inline Forwarding some e-mails with base64 body will display wrong content

Status: RESOLVED DUPLICATE of bug 173012

(Thunderbird :: Message Compose Window, defect)

Description

[Ger Teunis]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20050820 Firefox/1.6a1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20050820 Firefox/1.6a1

I can't inline forward some emails I have received.
The email text content itself is base64-ed
When forwarding that message the forwarded content is crippled to some
unreadable characters. OE and Outlook both forward the message OK.awrof t'nac I 

Reproducible: Always

Steps to Reproduce:
1. Open the attached email in TB
2. Forward the message inline (Message -> forward as -> inline)
3.

Actual Results:  
The original content is unreadable, some weird characters are displayed

Expected Results:  
The original content should still be readable.

Comment 1

[Ger Teunis]

Attachment: Example email

Comment 2

[Ger Teunis]

I wasn't able to forward / Reply / Edit opened emails from .eml files.
I've filed Bug 305378 for that.
You will have to import the attached message somehow before you are able to test
the forward.

Comment 3

[Joe Sabash [:JoeS1]]

Forwarding is not the only function that is affected. If a message is copied to
another folder, or saved as unsent the image source links are lost, and the
following tag is inserted: <img moz-do-not-send="true" the rest of the source is
left in the escaped condition.
It doesn't matter if the image is a jpeg, gif or whatever format.
Images inserted as a background image are not affected.

Comment 4

[Joe Sabash [:JoeS1]]

This is with version 1.0+ (20050820), and I believe the same condition exists on
the trunk.

Comment 5

[Mike Cowperthwaite]

(In reply to comment #2)
> I wasn't able to forward / Reply / Edit opened emails from .eml files.
> I've filed Bug 305378 for that.

Also a duplicate, as you've already been notified.  Please make an effort to 
search for bugs before reporting them.

(In reply to comment #3)
> Forwarding is not the only function that is affected. If a message is copied
> to another folder, or saved as unsent the image source links are lost, and the
> following tag is inserted: <img moz-do-not-send="true" the rest of the source
> is left in the escaped condition.

I really don't see how you can consider this to be the same bug.  I'm not sure I 
understand the problem completely -- could this be bug 224733?  If not, please 
open a new, complete bug (with sample data and Steps To Reproduce).

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

Comment 6

[Ger Teunis]

(In reply to comment #5)
> Also a duplicate, as you've already been notified.  Please make an effort to 
> search for bugs before reporting them.

I did, as I always do. But unfortunately I checked for the keyword "forward".
That bug seems to be using "fwd" in the description.
I'll search more thourough next time.

Comment 7

[Joe Sabash [:JoeS1]]

> (In reply to comment #3)
> > Forwarding is not the only function that is affected. If a message is copied
> > to another folder, or saved as unsent the image source links are lost, and the
> > following tag is inserted: <img moz-do-not-send="true" the rest of the source
> > is left in the escaped condition.
> 
> I really don't see how you can consider this to be the same bug.  I'm not sure I 
> understand the problem completely -- could this be bug 224733?  If not, please 
> open a new, complete bug (with sample data and Steps To Reproduce).
> 
> *** This bug has been marked as a duplicate of 173012 ***

Not bug 224733 but has the same result on the image source tag due to
<img moz-do-not-send="true"  being inserted.

Submitted bug #305557