GNOME Bugzilla – Bug 321608
Evolution does not update read status on IMAP mail when read from another location
Last modified: 2008-10-22 19:19:59 UTC
Version details: evolution-2.2.3-2.fc4 Distribution/Version: Fedora Core 4 The IMAP protocol can (apparently) indicate which emails have been read on a server. I tend to read my email from several locations (home, work, etc.). If I leave evolution running at one of these locations (say, work) while reading my email from another location (say, home), the process at work does not update to reflect the most recent read status of the emails. 1. Open evolution and have it use an IMAP account as a source. 2. On another machine, run a separate evolution process and have it use the same source. 3. When new mail comes in, read it on one machine (or mark it read). 4. Force Evolution to update the server status by typing Cntl-E. Actual Results: The process on the other machine still shows the mail as new and unread. Expected Results: The process on the other machine updates the read status of the mail to be 'read' the next time it syncs with the IMAP server.
Hmm... i remember this is a bug which has been filed already. Not sure of the bug number though. Several things: * Ctrl-E - just does an expunge, and does *not* do anything else (like syncing up flags) * have you tried changing folders or hiting the send/receive button cos thats when Evolution syncs up with the server.
(question to myself:) doesn't gicmo work on sth to fix this issue? hmm...
Prothonotor: This bug is not reproducible in stable release evolution 2.6.2. Upgrade to latest version and update if this bug is still reproducible.
poornima: sorry? of course this is more than reproducible. i get that every two weeks on IRC. reopening.
Partha is right. Expunge is not a general purpose "force sync", though it probably should just do that, too. Also, I too believe I have read about that before in bugzilla. Anything along the lines of "syncing periodically" would fix this. The syncing part on one end. There still is the server involved... Comment 3 is just useless and utterly wrong. Additional steps to reproduce this "does not sync issue": * read mail, previous unread * wait for hours... * kill Evo Result on next startup: Unread mails again. Same for flags. (Yes, this is a side issue of the infamous "crashes on closing" family of bugs.) Also, switching folders back and forth indeed does work as has been mentioned, since it forces a sync on leaving the folder. For both cases, running idle (oriniginal report) or killing/crashing Evo. Confirming.
I am experiencing this bug in Evolution 2.6.3. andre and guenther helped me on IRC by suggesting I switch to another IMAP folder and back. I tried this and it does push changed "read" flags to my IMAP server, thanks! Now messages read in Evolution also appear as "read" in mutt and SquirrelMail. I am still having trouble, however, pulling changed "read" flags from my IMAP server to another instance of Evolution. I tried switching to another IMAP folder and back. I also tried the "Send / Receive" button, but "read" flags still do not match flags on my IMAP server. Only after quiting and restaring Evolution did the "read" flags match flags on my IMAP server. Thanks, Jack
(refering to comment #2) <gicmo> fejj always told me that is a feature <novice> download mails from pop3 and filter them to an mbox-account <andre-afk> gicmo: well, i think i remember that you once told that you're working on this issue, also for the scalix connector <gicmo> yes .. but I couldnt come up with a good solution since this is again a camel design issue <gicmo> like everything is done asych in camel BUT flag changes because flag changes will only be synched back to the server at the exit <gicmo> normally it only stores the flags locally to the summary <gicmo> btw, this also is the reason evolution often seems to hang if you close it (because its acutally synching flags)
I'd like to clarify that I wrote this one up specifically for Evolution not re-reading the 'read' status when it changes on the server. I'm using Evo 2.8.1.1 (from FC6) now, and still see this problem. BTW, I still have to manually expunge to get evo to update the flags on the server, but that's a separate issue AFAIC.
hm, isn't this the same as bug #317755 ?
It certainly seems so. Resolving as a dup. *** This bug has been marked as a duplicate of 317755 ***