Closed Bug 233041 Opened 21 years ago Closed 17 years ago

All filtered msgs marked as read, but unread count in folder column is correct.

Categories

(MailNews Core :: Filters, defect)

Product:
MailNews Core
Component:
Filters
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED INVALID

People

(Reporter: keith.hopkins, Unassigned)

Details

Attachments

(1 file)

Zip file containing an IMAP protocol log (edited for privacy)
36.68 KB, application/octet-stream
Details
User-Agent: Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040113 exact same HW/SW setup as http://bugzilla.mozilla.org/show_bug.cgi?id=233040 RH9: Incoming IMAP server is corp MS-Exchange 5.5 on a 10MB lan. Destination IMAP server is dbmail 1.2.1 (mySQL backend) on my laptop PC. About 20 filters in Moz, and 50 IMAP folders/sub-folders on the destination. Filtering happens when new msgs come into the Inbox of the Exchange server. I only see this one machine, where Moz, dbmail/mysql are all running. It is a PIII/800 w/512M RAM. Memory isn't a problem, but there is usually contention for disk I/O, and sometimes for CPU. I'm filtering (Move) msgs from the Exchange Inbox to subfolders on the local dbmail-imap server. Unread counters on the folder list are maintained correctly, but when you access an individual folder, you see that all messages are marked read, and the folder counter clears. It is easy to sort by date and find the new msgs. Reproducible: Always Steps to Reproduce: 1.need MS-Exchange server 2.slow lan 3.so-so laptop 4.dbmail/mysql 5.Moz 6.lots of subfolder in dbmail 7.filter to sort from the Exchange Inbox to the dbmail folders, various criteria. "To or CC" is good. 8.setup 4-5 IMAP account. only one (Exchange) does filtering to the local dbmail-imap server. 9.set the Exchange Inbox to check for new mail every 1 min. Other Inboxes checked every 3-10 min. 10. wait for lots of mail to be delivered. I usually get about 15 e-mails per 10 min. Actual Results: Every filtered (move) msg from one IMAP server to another IMAP server is marked as read. Expected Results: don't mark the messages as read when inserting into another IMAP server.
This may be the same as bug 179556; Keith Hopkins, if you agree, please mark this bug as a dupe of that one.
(In reply to comment #1) > This may be the same as bug 179556; Keith Hopkins, if you agree, please mark > this bug as a dupe of that one. Not a duplicate. from 179556 "New" counts in folder pane not correct for messages filtered with 'Move' and 'Mark as Read' From my perspective: 1) "New" counts in the folder pane are not the issue, but only a side effect. 2) 'Mark as Read' is NOT selected on the filter 3) Messages are being marked as read
I am seeing this same problem: emails from an IMAP server (GroupWise) filtered to move to folders on the same server (but NOT filtered to be marked as read) are marked as read. Until yesterday, when I upgraded from 1.6 to 1.7, I was not having this problem. This bug may be a duplicate of <a href="http://bugzilla.mozilla.org/show_bug.cgi?id=242136">bug 242136</a>. User Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040616 Until I click on a folder to which new emails have been moved (by a filter), the folder name is bold, and shows the correct unread messages count. But after I select the folder, its name is changed from bold to normal, the unread count disappears (becomes zero), and none of the new, unread messages are shown as unread (titles should be bold, but aren't).
the filtered msgs marked as read in the inbox is the desired behaviour, since we now mark deleted messages as read. But the unread count being wrong is not the desired behaviour.
Assignee: sspitzer → bienvenu
Status: UNCONFIRMED → NEW
Ever confirmed: true
(In reply to comment #4) > the filtered msgs marked as read in the inbox is the desired behaviour, since we > now mark deleted messages as read. But the unread count being wrong is not the > desired behaviour. It CAN'T be the desired behavior for new, never read mail, moved by a filter from the Inbox to another folder, to be marked as read IN THE FOLDER TO WHICH IT'S BEEN MOVED, and that is what is occurring in my setup.
oh, no, sorry, only in the source folder - are all these moves across servers? Can you attach an imap protocol log? thx. http://www.mozilla.org/quality/mailnews/mail-troubleshoot.html#imap
This huge file (~800kb) represents a few minutes of activity, in which one email message received, then moved from the INBOX to 'Folder One' (by a move-only filter). After the message was received, I selected 'Folder One', then the message, which was then displayed in the preview pane. After I selected 'Folder One', its unread count went to zero, and the new message in 'Folder One' was marked as read. Note that the new message never appeared to be marked as unread in 'Folder One'.
(In reply to comment #6) > oh, no, sorry, only in the source folder - are all these moves across servers? No, from the INBOX on the server to 'Folder One' (as it is named in the above-linked zip'd IMAP protocol log) on the same server. > Can you attach an imap protocol log? thx. I had to compress it (zip format), because the upload limit is 300kb, and the uncompressed log is ~800kb. > http://www.mozilla.org/quality/mailnews/mail-troubleshoot.html#imap Very nice instructions--I had no problem, even though I'd never attempted it before.
thx for the log - I don't see the client doing anything wrong. I suspect that the server is getting confused when we copy a message and then immediately mark the same message SEEN in the source folder. I suspect the /SEEN flag is getting carried over to the destination folder, even though we don't set it until after the copy has completed.
I want to emphasize that this problem is new; Mozilla 1.6 does not exhibit this behavior.
yes, the new behaviour is that we do mark messages read when we delete them, *after* copying them to another folder. So yes, we have a new behaviour, but as near as I can tell, this is merely exposing a bug on the server. I could be wrong that this is a bug on the server, but people using other imap servers like UW or Cyrus or have not reported this...
(In reply to comment #11) > ... people using other imap servers like UW or Cyrus or have not > reported this... Although the reporter for bug 242136 doesn't know the identity of their IMAP server, they are having a problem very similar to mine.
Product: MailNews → Core
Even I;m also facing this same problem. Here we are using Novell GroupWise Server. Is there any possible way to stop marking this in source folder, to avoid the problem for ppl like us.
Has this been fixed by the checkin for Bug 275561 ?
jsnod, do you have means to test it this was fixed by Bug 275561? david, can you suggest a disposition for this bug? Rowe writes "problem still exists when connected to GroupWise 6.5 IMAP server from Thunderbird 1.5.0.4, 2.0.0.4, and 2.0.0.6. For each of these versions, I reverted the patch at bug 225021 ... This fixed the problem for me. ... switched to Exchange/Outlook, so I no longer use Thunderbird, and unfortunately I can't help with testing." reporter and RamaSubbu email addresses are dead, so no information will be forthcoming from them.
Assignee: bienvenu → nobody
OS: Linux → All
QA Contact: laurel → filters
Hardware: PC → All
Invalid - it looks like a server issue to me.
=> invalid
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → INVALID
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: