Version: 1.1.1 (using KDE KDE 3.4.1) Installed from: Mandriva RPMs OS: Linux I usually started KMail automatically as part of KDE default session and never explicitly terminated it doing simply halt or reboot as needed. KNode was usually started on demand and quitted. It was always annoyed to see messages in KMail that I have already read marked as "old unread" (I believe, blue color means this by default) after logging back in; I have never seen it in KNode. Recently I switched over to using Kontact (again as part of default session and no explicit exit) and the same problem now started for KNode too - after logging in and going into news I see "new" messages in group that I already marked as read in previous login session. I would expect kontact to immediately and synchronously update status of messages; apparently this does not happen.
well, I still have the same problem in KDE 3.5. It is pretty annoying as it means, I have to manually stop kmail/knode before logging out or shutdown.
I think this was fixed in 3.5.3/4.
Are you using disconnected IMAP? If so, then an explicit mail check is needed to write the changes back.
To comment #2: I definitely had the same problem with 3.5.4; have to check 3.5.5. To comment #3: I do not have IMAP, I am using POP accounts only.
Thank you for taking the time to file a bug report. KMail2 was released in 2011, and the entire code base went through significant changes. We are currently in the process of porting to Qt5 and KF5. It is unlikely that these bugs are still valid in KMail2. We welcome you to try out KMail 2 with the KDE 4.14 release and give your feedback.