Version: 4.7 (using KDE 4.7.0) OS: Linux Mark as read only marks as read until the folder is selected again. Reproducible: Sometimes Steps to Reproduce: It doesn't happen always, but it does most of the time. - Mark all mails in a folder as read. (either individually or by right-clicking a folder) - Select another folder - Now select the first folder again. Actual Results: The mails that were marked as read before will now be marked as unread again. Expected Results: Mails that were marked as read before should not be automatically unmarked again. Folders belong to a DIMAP account (Kolab)
Looks like a duplicate of bug #278737 .
Can you try if it is reproducible with KMail2 from KDE 4.8.0?
Yes. I upgraded to KMail2 from 4.8.0 and it was still impossible to keep messages in some folders read.
Can you please enable imap logging as described here http://techbase.kde.org/Projects/PIM/Akonadi/Debug_IMAP , reproduce the bug and post here or send the log to me? You can rename sensitive info from the log, if there is any (user name, folder names, etc.)
I'm sorry, but not long ago, I erased all akonadi/kmail related settings and recreated them with only 1 small account. There were too many problems. (Errors or crashes on send) I'm using the exact same version of Kontact now, but with far less folders and mails. So far, mark as read isn't a problem. The only things I can tell about the previous situation is that the mails that couldn't be permanently marked as read were in sub folders on a Kolab server. (DIMAP only. The kolab proxy doesn't work because my server runs on non-standard ports and/or the correct server couldn't be set in the kolab resource.) Alls mails in the INBOX of that same server could be marked as read just fine.
Ok, let's close it now. I use daily DIMAP on a kolab server, and marking the mails as read works for me in subfolders as well. If you see it again, please reopen the bug or create a new one. As for the kolab proxy problem, can you please create a new report describing what is your setup and why you can't use the proxy. Thank you.
Ok, If I ever have this problem again, I'll reopen. The Kolab proxy problems were reported as bug #280193 and bug #280194