Reply or forward of long message clears message body

RESOLVED EXPIRED

Status

MailNews Core
Backend
--
critical
RESOLVED EXPIRED
15 years ago
10 years ago

People

(Reporter: Sean Aitken, Assigned: (not reading, please use seth@sspitzer.org instead))

Tracking

({dataloss})

Trunk
x86
Windows 2000
dataloss

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Reporter)

Description

15 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5) Gecko/20030925
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5) Gecko/20030925

After receiving a message that is part of several replies, the sent message,
with new body added shows sent successful.  The recipient complains of "no
message".  Checking in the sent items, the message does in fact contain NO body.

Reproducible: Always

Steps to Reproduce:
1. Using the attached sample message, attempt to forward, or reply to.
2. View the sent message source in Mozilla and on the recipient end.
3. Notice the body does not exist!

Actual Results:  
Blank message sent to recipient, all typed content lost and isn't even in the
"sent" message found in the sent folder.

Expected Results:  
Send the message with the added body content, including the original message thread.
(Reporter)

Comment 1

15 years ago
Created attachment 132363 [details]
Sample message

This file is a sample message that I can consistently reproduce the bug that
will blank the entire body of the message when a forward or reply with original
message is performed.
(Reporter)

Comment 2

15 years ago
I filed this as "critical" because all of the typed content added to an email
displaying this bug is lost.  I personally spent 20 minutes typing a reply to
this message only to find it lost forever after I discovered this problem.

Updated

15 years ago
Keywords: dataloss
Product: MailNews → Core
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/
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.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.