224579 - malformed no-sender or Korean mail hangs filter on WinME

Status: RESOLVED EXPIRED

(MailNews Core :: Filters, defect)

Description

[Pete]

User-Agent:       Mozilla/5.0 (Windows; U; Win 9x 4.90; en-US; rv:1.5) Gecko/20030925
Build Identifier: Mozilla/5.0 (Windows; U; Win 9x 4.90; en-US; rv:1.5) Gecko/20030925

I think malformed email may hang the email filter. OS is WinME.
The behaviour I saw was the 6 or 8 of about 20 emails were downloaded from the
POP server, the last several were not. After a while I clicked on 'get messages'
again and got a message about the mail still being processed. So I closed the
mail window and went to look at the mail in a web window from the server. What
I see there is one email/spam with upper-ascii (Korean) characters in the
Subject line and several emails with no address for a sender. Deleting these on
the server side makes everything on the mail client side work normally again. If
I didn't delete these or similar  bad email then download/reading email would
seem not to work forever. I'm fairly sure I saw this on 1.4 and 1.5b too. I'm
fairly sure that Netscape 7 or 7.1 didn't do this.

Reproducible: Always

Steps to Reproduce:
1. wait for bogus email without a sender
2. I get this about twice monthly, not sure yet how to save the bad mail.
3.

Actual Results:  
A really malformed email message will hang filters and so stop
all future email reading until the bad mail is deleted.

Expected Results:  
Complain about the bad mail(s), leave it on the server, read the rest.

No themes or default theme.
WinME, plenty of memory and not maxed out. cable modem.
All the up to date MS updates applied, Norton internet
security running.

Comment 1

[Christian Eyrich]

Why are you so sure about that filters are the problem? Filters do their work
after downloading a message, not while it's being downloaded.

Unfortunately you deleted the bogus mails and don't have the problem right now,
yes? But if you have this problem the next time, it would be great if you could
create a communications log and attach it to this bug. Instructions how to
create the log can be found here:
http://www.mozilla.org/quality/mailnews/mail-troubleshoot.html#pop

Comment 2

[Gervase Markham [:gerv]]

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/

Comment 3

[Gervase Markham [:gerv]]

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.