After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 459041 - Evolution does not update read flags on IMAP server while running
Evolution does not update read flags on IMAP server while running
Status: RESOLVED DUPLICATE of bug 317755
Product: evolution
Classification: Applications
Component: Mailer
2.10.x (obsolete)
Other Linux
: Normal normal
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-07-21 17:47 UTC by Tessa Lau
Modified: 2009-02-04 19:31 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description Tessa Lau 2007-07-21 17:47:22 UTC 
+++ This bug was initially created as a clone of Bug #321168 +++

I use multiple mail clients to access the same IMAP service.  Suppose I have two Evolution clients running on two different machines, accessing the same INBOX.

* start up client A on one machine
* start up client B on another machine
* in client A, refile a message to a folder and mark another as read
* in client B, notice that both messages are still marked unread in the INBOX
* pressing Send/Receive on client B does not change anything
* press Send/Receive on client A and notice that client B *still* has those two messages marked unread
* quit client A
* client B still does not pick up the changes
* quit/restart client B, and *finally* the changes are propagated to client B

This bug means that I end up dealing with the same mail twice, because even though I've refiled it using evolution on my home computer, when I get to work, the message is still in my inbox.  Evolution ought to synchronize changes periodically with the IMAP server so that other clients accessing the same server pick up changes made by the Evolution client.
Comment 1 Jean-François Fortin Tam 2008-05-01 19:32:58 UTC 
isn't this bug #317755 ?
Comment 2 Tessa Lau 2008-05-01 20:12:00 UTC 
Yes, it looks like a dup.  They don't talk about refiling being one of the actions that isn't synchronized but the general gist of the bug is the same.
Comment 3 Martin Ejdestig 2009-02-04 19:31:56 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


*** This bug has been marked as a duplicate of 317755 ***