Version: 4.7 pre (using KDE 4.7.0) OS: Linux After starting kontact (kmail), and after my gmail messages have been retrieved, and after my filters have been applied and new messages have been moved to their appropriate folders, some folders show unread messages that never display in the preview window and cannot be opened. These message have, in fact, been read already. If more than one of these happens to be in some folder, the Go->Next Unread Message function loops over all of these and never moves to the next folder. Reproducible: Always Steps to Reproduce: Start kontact. Repeatedly do Go->Next Unread Message Actual Results: Eventually I hit one of these "unread" messages that I have actually read before. Expected Results: Message that has been read stays read unless I explicitly mark it as unread. kde 4.7.0 from fedora-kde47 repository
Created attachment 63000 [details] Log While Landing on Unread Message That is Not Unread
My setup is gmail POP3 and filters to sort messages into various directories. I attached the error log from a typical case. I do Go->Next Unread Message and that lands on a message marked unread that has been read. I just waited at that point until my POP account was polled. At that point, the message list selection jumped spontaneously to the last message in the current folder.
Disabling Nepomuk Semantic Desktop fixes the bogus unread messages problem.
Actually, the problem is still there -- it just takes longer to appear after disabling Nepomuk Semantic Desktop.
I can confirm this.
Updating has improved things. $ kmail --version Qt: 4.7.4 KDE Development Platform: 4.7.2 (4.7.2) KMail: 4.7.2 $ rpm -q kdepim kdepim-4.7.2-4.fc15.x86_64 $ Messages stay read in all folders except the inbox. The inbox folder often shows more unread messages than are actually unread. The index display most of the time does not show the additional messages as unread -- only the count is wrong in the folder tree view. Very occasionally an old message will show as unread in the index but now it will display and become read if I click on it or visit it with Go->Next Unread Message. Much improved. This bug should be closed. (Another irritating thing -- spontaneously jumping to another message when new messages have been retrieved -- is now fixed.)