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 433816 - imap doesn't sync the read flag
imap doesn't sync the read flag
Status: RESOLVED DUPLICATE of bug 317755
Product: evolution
Classification: Applications
Component: Mailer
2.6.x (obsolete)
Other All
: Normal normal
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks: 233428 434571
 
 
Reported: 2007-04-27 08:41 UTC by Wilfried Goesgens
Modified: 2008-10-22 19:19 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Wilfried Goesgens 2007-04-27 08:41:07 UTC
Please describe the problem:
I'm using Evolution with the citadel.org groupware server, and i'm connecting via imap. The issue i'm having is that evolution won't resync the read flags in both directions. 

Steps to reproduce:
So, when i read a mail in the webinterface, and the server marks it as  read, evolution will continue showing it as unread. If i read a mail in evolution, it won't mark it as read on the imap server.

Actual results:
connect evolution to an account you can create via 
https://uncensored.citadel.org
Connect evolution with the account you've created via imap.
Send you a mail in. 
Try reading the mail with evolution or the webmail interface.

Expected results:
evolution should resync the states.

Does this happen every time?
yes

Other information:
If you need more information about citadels imap server join #citadel in freenode, or post a message to the citadel support room.
Comment 1 Jean-François Fortin Tam 2008-05-01 19:26:47 UTC
isn't this bug #317755 ?
Comment 2 Akhil Laddha 2008-06-16 06:22:48 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 ***