GNOME Bugzilla – Bug 507575
When IMAP mails end up marked as "read" upon viewing with a different client, they continue to be marked as unread when viewed with evolution, until I restart evolution
Last modified: 2015-09-17 05:18:38 UTC
Here's the use case: 1. Start evolution and note an unread mail in your IMAP inbox. 2. Log into the same account using squirrelmail and read that mail. 3. Log out of squirrelmail. At this point, the mail continues to be marked unread in evolution, and "Refresh (F5)" does not result in marking it as read. The only way to achieve that is to restart evolution. Upon startup, evolution says "Scanning <folder> for changed messages" or something to that effect. This action causes the messages to be correctly marked as (un)read, according to how they are marked on the IMAP server side. It would be nice if I could invoke that functionality from the menu, or if it were included in the "Refresh" functionality.
F5 ? did you just try to "refresh" (context menu)?
I went to Folder -> Refresh in the main menu.
sounds like this bug would be better labeled as "Refresh does not work on IMAP". I just reported a probably-related bug 571684 for "Evolution not updating IMAP mailbox"
Accessing one IMAP account simultaneously with two applications is considered a fault, as I understand it from this mail: http://mail.gnome.org/archives/evolution-list/2007-June/msg00112.html I tend to WontFix, as the Folder->Refresh calls camel_folder_refresh, which is called every time you change folder, and it checks for new messages only, not for all, for performance reasons. There is a way to do that, probably by using IMAP's IDLE extension, as is described in bug #233428. I tent to mark this one as a duplicate of it.
Changing to another folder and going back updates the view in 3.2.3 (tested with Thunderbird 10 as the other client and Gmail IMAP). Not sure if anything more can be done - looks like Thunderbird does not update at all. :-/
I'm closing this, one way is to Refresh the folder (either by moving elsewhere and back, or in the context menu of the folder, or when automatic update is run, or...), the other way is to use IDLE on the folder, which is done when it can be done. The notifications are not that spread, thus this is the most Evolution can do right now.