Closed Bug 189015 Opened 22 years ago Closed 21 years ago

New mail not showing in count when filters fail to process

Categories

(SeaMonkey :: MailNews: Message Display, defect)

x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: mozilla, Assigned: sspitzer)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3a) Gecko/20021212
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3a) Gecko/20021212

Links to (but is different from) bug 168648.

When the filters cannot filter mail, they drop it into the mailboxes for the
individual accounts that were the original recipient.   Not a major problem, as
long as I remember to scroll down and look there.

With 1.3a, I've noticed several times that when this happens, the new mail
doesn't appear in the "Message count" in the left hand window inbox - which
remains blank, since I don't leave mail in the inbox.

Clicking on the inbox then brings up the "new mail count", and the items then
appear in the top right hand window.

I've not had this problem in earlier releases (or not noticed it, anyway).

Reproducible: Sometimes

Steps to Reproduce:
1. Leave broadband disconnected for a few hours so that the mailboxes on the
various ISPs fill up a bit.
2. Log on - Mozilla tries to collect mail from all the ISPs, and the filters
can't cope so don't process it all (bug 168648).
3. Mail not processed goes to the "Inbox" of the individual ISP account, rather
than to the folders used by the filter.


Actual Results:  
That mail doesn't appear in the left hand window.   

Expected Results:  
Either:
a)  Filtered the mail (separate bug), or
b)  Show it in the mail count.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Summary: New mail not showing when filters fail to process → New mail not showing in count when filters fail to process
Keith Jillings, is this bug still a problem?  Except for the filtering problem, 
it sounds similar to bug 186573, which started in early 1.3 development and was 
fixed (I think) by 1.4.
It wasn't a very frequent occurrence.   I hadn't noticed it in the past few
weeks, so checked closely over the last two days, and have not seen it again.  
Marking it as "Fixed".

The other problem - 116181 green arrow doesn't go away - is definitely still
there, though.
Status: NEW → RESOLVED
Closed: 21 years ago
Resolution: --- → FIXED
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Reopening to fix resolution.

Keith, in the future, please use "WorksForMe" rather than "Fixed" unless you can 
point to a specific patch checked in to Mozilla that addresses the issue in the 
bug.
Status: REOPENED → RESOLVED
Closed: 21 years ago21 years ago
Resolution: --- → WORKSFORME
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.