Closed Bug 137022 Opened 22 years ago Closed 19 years ago

"Forward Inline" contains only headers, and no text/content/body, of forwarded message

Categories

(MailNews Core :: Composition, defect)

x86
Windows 98
defect
Not set
major

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: youying, Assigned: bugzilla)

Details

(Keywords: dataloss)

Attachments

(6 files)

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:0.9.9+) Gecko/20020411
BuildID:    2002041103

I found if I would like to forward (as inline) some HTML format message, 
the composing window contains no text/content.

Reproducible: Always
Steps to Reproduce:
1. Setup forward way as "forward as inline"
2. Forward HTML message


Actual Results:  It(Composing windows) should contain text/content.

I'm not sure which kind of HTML format could be reproduced, I attach the messge
source 
that got this issue.
Reporter, to see the Problem more clearly:
- You open a message with inlined html with "reply"
  => message is opened in a new composer window

expected result:
you find all html (which means, a opage like this) in the composer window, also
as you saw that when you had opened the received mail in your inbox.

actual result:
you find something like following quote:
> 
> -------- Original Message --------
> Subject: Bug 137022 - "Forward Inline" contains no text/content
> Date: Fri, 12 Apr 2002 08:15:45 +0200
> From: Bielefeld__Buss_oHG@t-online.de (Rainer Bielefeld)
> Reply-To: Bielefeld__Buss_oHG@t-online.de
> To: Bielefeld__Buss_oHG@t-online.de
> 
> 
> <http://bugzilla.mozilla.org/show_bug.cgi?id=137022>
> 
and the header of the page in the attatchment-window of the composer-window.

I can confirm that it is a little unexpected that i cannot see the inlined
html-page. But sending the mail seems to be without problem, the recipient will
get the html 



added myself to cc








The problem still exists in Mozilla 1.0 RC1.  :-(
The problem still exists in Mozilla 1.0 RC1.  :-(
[Mozilla/5.0 (Windows; U; Win95; en-US; rv:1.3a) Gecko/20021212]

I ran into a case which starts like bug 168386 story,
but it is actually more like bug 137022 comment 2 behaviour.

I can read, reply to, forward as attachement without problem,
but forward inline gets the headers only and not the body.

I will attach a mail file which contents the original message, and the forwarded
inline one.

Steps to reproduce:
1. Put the file in your mail directory.
2. (Mozilla/Messenger restart may be needed !)
3. Use Messenger to work with this new folder.

NB: Could the problem be related to the email having only 1 "multipart" and/or
its body being "base64" encoded !?

PS: If you agree that it is the same bug: 1) I confirm it, on Win95, 2) Summary
should be updated to be clearer about headers/body behaviour.
Looks good.

Still, please test against a modern build of mozilla./
Re comment 11:

What looks good ? What do you call "modern build" ?

Tested with comment 10 case:


[Mozilla/5.0 (Windows; U; Win95; en-US; rv:1.4) Gecko/20030529]

Bug still there (v1.4rc1).

Adding: (K) 'dataloss'.
Changing: (S) 'Unconfirmed' -> 'New'.


[Netscape® Communicator 4.8 : en-20020722]

Same bug ! [not '4xp' and most probably not 'regression' :-<]
Status: UNCONFIRMED → NEW
Ever confirmed: true
Keywords: dataloss
Summary: "Forward Inline" contains no text/content → "Forward Inline" contains only headers, and no text/content/body, of forwarded message
I have this occur with many spams.  The spammer sends a message that is purely
HTML, is in quoted-printable format, or some other MIME-encoded type message,
and when I set it to "View Headers: All" and try to do an inline forward (many
abuse admins won't accept attachments), I get either the SMTP headers only or
nothing.

It would also be nice to be able to run scripts on junk mail, such that you can
forward the entire message with full headers to an abuse administrator at the
click of a button. :)

This is occurring on the linux build, too.  I'm currently running 1.4 under RH9.
Product: MailNews → Core
Attachment #110665 - Attachment mime type: application/octet-stream → application/zip
I am unable to reproduce the original problem reported.  After integrating 
attachment 78820 [details] into my mail, I can forward-inline the message as HTML or as 
plain and get a correct message body displayed.

Moz 1.7.7, TB 1.0+0506, Win2K.

Serge Gautherie's attachment 110665 [details] does still cause a problem.  The message 
body in that message is base64-encoded (altho it's plain text); also, the 
message is not quite legal -- there is no closing MIME boundary for the "first 
part" of the message.  See bug 173012 for another example of inline-forward 
problems with a Base-64 encoded message, and also the second problem reported at 
bug 196180.
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → WORKSFORME
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: