GNOME Bugzilla – Bug 571684
Evolution not updating IMAP mailbox
Last modified: 2009-05-26 11:54:10 UTC
Please describe the problem: I use Evolution (on Ubuntu 8.10) on both my home and office computers, and configured identically. The only account I have is my AOL email, accessed by IMAP. Changes I make to the Inbox are not reflected in the source, my online AOL webmail (hence not at the other machine either). Steps to reproduce: 1. access my AOL Inbox through Evolution 2. read and/or delete any message 3. login to http://mail.aol.com 4. the change will not be reflected online Actual results: Expected results: Does this happen every time? This happens very frequently; I can't say if it's 100% consistent, though. Other information:
did you close evolution before accessing your account via webmail?
Yes, I closed Evolution. And this is not an isolated incident, it's been clear for a long time that my two copies of Evolution were not reflecting the changes made from the other copy, i.e., I'd check my email at home (read, delete, etc), then close down, go to work, check my email again and all the changes I'd just made would be gone. Rather than report that 2 copies of Evolution don't 'sync', however, I think it's better to focus on the immediate test showing that the source (AOL's webmail) doesn't show any changes either.
I'm having this same problem with evolution 2.24.4 on Arch Linux. Moving 20 read messages to a folder may mark all of them new, or any number of the recently moved messages new. It's also possible that it works fine and none are marked new (happens mostly when moving single or small groups). Sometimes it also happens when I close evolution at work with everything read. Open evolution on a different computer at home and that computer now sees unread messages that I read from the work computer. The home computer was off and not accessing the inbox at the same time. This happens using both Dovecot and Exchange's IMAP server and only started happening noticably for me with the upgrade to 2.24.4.
see bug 507575 also
I thought about bug #545103, as it sounds very similar, but it doesn't seem to be a case here, as it's in sources for quite a long time. The other I can think of is 2009-02-19 Sankar P ** Fix for bug bnc #477535 * camel/camel-folder-summary.c: Randomly mail status changes were not getting stored in server. Fixed the issue by unsetting correct flags. I believe it's the reason. Thus closing as fixed. (In reply to comment #3) > I'm having this same problem with evolution 2.24.4 on Arch Linux. Moving 20 > read messages to a folder may mark all of them new, or any number of the > recently moved messages new. It's also possible that it works fine and none > are marked new (happens mostly when moving single or small groups). The above should be addressed within bug #534938, copied/moved messages are not treated as new after the patch there.