mail stalls when downloading a damaged message (ie. "no sender")



15 years ago
11 years ago


(Reporter: luschwa, Assigned: sspitzer)


Windows XP

Firefox Tracking Flags

(Not tracked)




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

When retrieving mail the program sucessfully completes logging into the mail
server, determines how many messages are pending, and begins to download them. 
If it's the first or a subsequent message, when the program encounters an
unexpected condition, it just sits there and does nothing.  Using Eudora (ver.
6.0) to retrieve the same batch of messages it is sucessful; however, it alerts
the user of a "task error".  Looking at that last message, Eudora displays "No
Sender, No Subject".  Mozilla should be tolerant of "buggered up" messages.

Reproducible: Always

Steps to Reproduce:
1.Launch mail handler.
2.Sit back and wait for a bum message.

Actual Results:  
The mail handler stalled when it hit a bad message.

Expected Results:  
As with Eudora, indicate to the user that an error was detected; but then go on
and continue the retrieval.

Comment 1

15 years ago
What server do you use, POP3 or IMAP? Please set the Component according to your
Is the "corruption" of the message really no sender and/or no subject? If you
look at the message source in Eudora you should see what's missing.
Product: MailNews → Core

Comment 2

14 years ago
*** Bug 278354 has been marked as a duplicate of this bug. ***

Comment 3

14 years ago
do you have a virus checker installed? virus checkers can get in the way and
simply stop sending data to the pop3 code when they see a malformed message like
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:
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.
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.