Summary: whenever it turns out that IMAP STATUS reports something inconsistent with the local DB state, it would be nice if Mozilla knew to re-request all headers and resync the local DB with the server status of the messages. It seems that it is possible for the "unread" flags on messages to get unsynchronized between the local .msf db and the IMAP server. Whenever this happens, the "mail.imap.use_status_for_biff" mechanism will permanently keep marking the folder as having new messages: - Every time biff fires, the folder gets marked as having new messages and x unread messages. - When the folder is selected, the "new messages" mark disappears (there are indeed no new messages) and the number of unread messages is updated to y (with y < x). - The above repeats indefinitely (with x and y being constant until something indeed changes). I have no idea what causes the DB to become unsynchronized, but I know it is indeed unsynchronized - if I quit Mozilla, deleted the .msf and restart, then the unread counts become the same, with both being equal to the "x" count above. Would it be a good idea for Mozilla to be capable of detecting this condition and synchronizing the local status with the remote one? P.S. Not sure whether it matters, but all forlders in question are marked for offline. P.P.S. I see this on both 1.6 and a few days old trunk build.
sorry for the spam. making bugzilla reflect reality as I'm not working on these bugs. filter on FOOBARCHEESE to remove these in bulk.
Assignee: sspitzer → nobody
More like a bug for me, seen it too on TB3a1. There easy steps to reproduce it. Make changes on your IMAP folder like change count of unread. Go to another computer with same account start TB see unread count doesn't updated. This is especially true for folders other than INBOX.
OS: Linux → All
Hardware: PC → All
Product: Core → MailNews Core
Nikolay, still see this with trunk?
Not anymore Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1b5pre) Gecko/20090506 Shredder/3.0b3pre
Status: NEW → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.