Closed Bug 94604 Opened 24 years ago Closed 24 years ago

Messages are incorrectly marked as read instead of new

Categories

(MailNews Core :: Database, defect)

x86
Linux
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 85588

People

(Reporter: dledford, Assigned: Bienvenu)

Details

My mail setup checks my imap server for new messages once every 2 minutes. If there is more than 1 message for a given folder in that 2 minute interval, then only one of the messages will get marked as new, subsequent messages get marked as read even though I have not seen them. This makes the count of new messages wrong on my system.
what build id are you running? My guess is that this was fixed a couple days ago.
Build ID: 2001080814
Additional note. I've been able to isolate the problem down to the following: If there are multiple emails going into the same folder on a single check of my imap mail server, then the last of those emails will be marked read while all the others will be marked as new. So, if it checked 10 times and had 2 emails to download into a folder each time, then 10 of those would be new and 10 would be already read. OTOH, if it checked once and found 81 emails to download, then 80 would be marked as new and 1 as read. My email setup is with a remote IMAP mail server and a set of filter rules that always download all messages into local folders (I have a "catch-all" rule so that any messages that don't get sorted into a specific folder then get sent to the Inbox on my local mail) and the program automatically checks for new messages once every 2 minutes.
There's already a bug about filtering imap messages to local folders marking the messages read. Is it fair to say this a dup of that?
Status: UNCONFIRMED → NEW
Ever confirmed: true
I would say so.
dup *** This bug has been marked as a duplicate of 85588 ***
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → DUPLICATE
Looks like a DUP to me, also. Verified.
Status: RESOLVED → VERIFIED
Product: MailNews → Core
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.