296282 - Certain MIME message body unreadable with Forward Inline

Status: RESOLVED DUPLICATE of bug 307023

(MailNews Core :: Composition, defect)

Description

[Tobias B. Besemer [:BesTo] (QA)]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; de-DE; rv:1.7.8) Gecko/20050511 Firefox/1.0.4
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; de-DE; rv:1.7.8) Gecko/20050511 Firefox/1.0.4

Hey!

Plz have a look on this email I get.
The eml-files include the mail I get.
RE does work with it, but ffw brings garbage (see the html-file I send in).

Reproducible: Always

Steps to Reproduce:

Comment 1

[Tobias B. Besemer [:BesTo] (QA)]

Attachment: the orginal-e-mail saved

Comment 2

[Tobias B. Besemer [:BesTo] (QA)]

Attachment: the garbage

Comment 3

[Tobias B. Besemer [:BesTo] (QA)]

... my prefs are: include msg

Comment 4

[Matthias Versen [:Matti]]

>RE does work with it, but ffw brings garbage
RE ? ffw ?

Comment 5

[Tobias B. Besemer [:BesTo] (QA)]

Sorry, I use the german Version ...
RE means "returns mail".
fw means "forward mail".

Comment 6

[Tobias B. Besemer [:BesTo] (QA)]

Prob still remains in Thunderbird 1.1a1.

Comment 7

[Mike Cowperthwaite]

This is not a general problem of being unable to forward mail; it's specific to 
the message in attachment 185069 [details].  Reproduced with TB 1.0+0603, Win2K; also 
Moz 1.8b2-0516.  

The actual garbage string is different in both cases, and each is different from 
the text shown in the attachment 185070 [details].  Since the string is different, I 
suspect there is an issue with the "forwarded message body" being taken from 
some uninitialized buffer.

The message has this MIME structure:
  top: multipart/alternative; boundary=X
    --X
    text/plain
    --X
    multipart/related; boundary=Y
      --Y
      text/html; C-T-E: base64
      --Y--
    --X--

Note that the problem occurs whether the forwarding is in HTML or plain text 
compose, and whether the message itself is Viewed As Plain or As HTML.

This may be a duplicate of similar bug elsewhere.

Comment 8

[Mike Cowperthwaite]

(In reply to comment #7)
> This may be a duplicate of similar bug elsewhere.

Bug 173012, I think.

Comment 9

[Nikolay Shopik]

Still there with version 3.0a2pre (2008053003), WindowsXP

Comment 10

[rsx11m]

I've also seen this with Linux and SeaMonkey 1.1.9 release, adjusting flags.
A possible variant in bug 430697 produces an entirely empty message body.

Comment 11

[Mike Cowperthwaite]

I believe this bug has been fixed, probably by the patch to bug 307023.

Comment 12

[David :Bienvenu]

thx, Mike, yeah there would be several dupes, I'm sure.