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 321168 - Read IMAP messages not marked as unread on logout
Read IMAP messages not marked as unread on logout
Status: RESOLVED DUPLICATE of bug 317755
Product: evolution
Classification: Applications
Component: Mailer
2.6.x (obsolete)
Other Linux
: Normal normal
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2005-11-10 16:12 UTC by Ewan Dunbar
Modified: 2008-11-20 15:49 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14


Description Ewan Dunbar 2005-11-10 16:12:12 UTC 
Description of Problem:

The messages in my IMAP folders that I've marked as read locally do get
marked as unread on the server if I close Evolution manually but not if
I logout with it running.

Steps to reproduce the problem:
1. open imap folder
2. read messages
3. log out, saving status
4. log back in

Actual Results:

the imap folder comes up with the read messages still marked as unread

Expected Results:

they should be marked read
Comment 1 parthasarathi susarla 2005-11-10 16:38:53 UTC 
I tried with courier and cyrus and groupwise IMAP server, and this seems to be
working ok for me.
Comment 2 Ewan Dunbar 2005-11-20 02:58:03 UTC 
also works-for-me most of the time - will investigate
Comment 3 André Klapper 2006-03-24 18:13:43 UTC 
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can still reproduce this and can find out more.
Thanks!
Comment 4 Raphael Slinckx 2006-05-16 13:43:59 UTC 
I have the same problem here, how can i produce more results ?
Comment 5 André Klapper 2007-07-21 18:25:33 UTC 
see bug 459041
Comment 6 Peteris Krisjanis 2008-11-20 11:56:19 UTC 
As far as I know and have experienced by myself, this bug has been fixed since 2.24.x (see bug #317755), so this can be closed as dupe.
Comment 7 Matthew Barnes 2008-11-20 15:49:40 UTC 
Closing as requested.

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