Version: (using KDE KDE 3.5.2) Installed from: Ubuntu Packages AFAICT unread messages in ignored folders are not displayed as unread, but are not marked read on the IMAP server. Result: * since the "ignored thread" flag is not stored on the server, accessing mail from other mail clients is very annoying for my typical mailing list folders, where most threads are ignored. * The folder tree shows many unread messages in all those mailing list folders, but when I click on such a folder, the number of unread mail drops down to the really unread (== unread and also not ignored) emails. Fixing it by "Mark folder as read" is not possible, because this action seems to only know about unread unignored emails and still ignores ignored email. I'm not quite 100% sure what I have at home, but I strongly suspect that it's KDE 3.5.3 from Debian unstable, and the bug is present there, too. (Ubuntu/3.5.2 is my Laptop)
Oh, yes: the bug seems to be in both cached and 'normal' imap.
I am seeing the same problem using KDE 3.5.2 on Gentoo and KDE 3.5.3 on Solaris.
We decided not to mark messages in ignored threads as read. IIRC our reasoning was that this way after un-ignoring a thread you still see which messages you've already read. I'm pretty sure there was also a more technical reason for this. If you want to know more details then please search the archive of kmail-devel. Having said this we understand that this behavior can cause problems. We will keep this in mind for KDE 4.
That is a sensible reason for not setting the ignored mails to unread on the server. It should still be possible to fix the symptom: The folder tree shows many unread messages in all those mailing list folders, but when I click on such a folder, the number of unread mail drops down to the really unread (== unread and also not ignored) emails. by showing the count of unread and not ignored mails rather than just unread mails. That way the tree view won't say that a folder has 50 unread messages, but when you click on it there are none, because all 50 are ignored.
*** Bug 135479 has been marked as a duplicate of this bug. ***
Created attachment 22052 [details] kernel knows best.
Grr. Ignore that patch. I hate bugzilla.
*** Bug 117997 has been marked as a duplicate of this bug. ***
*** Bug 157021 has been marked as a duplicate of this bug. ***
When I click on ignored messages and _read_ them, they are still shown as unread after the next mail check. That’s surely a bug? To my mind there should be a setting in KMail--whether ignored messages are to be included in the unread count. To the opener: KMail does store the ignored flag on the server. It uses $IGNORED.
the problem with the folder list still showing the unread count as if the thread(s) wasn't ignored still exists in kde 4.2.4. when opening the folder, the unread count in the list is corrected. this is very annoying as i have to track down ignored threads from time to time to mark all the messages in a thread as read after the thread has died out. if i don't do this, kmail will show these folders as having unread messages forever.
"We decided not to mark messages in ignored threads as read." This should be an option exposed so users who want it can do so.
There's a slight misconception, I think. `Ignore thread' should not affect the number of unread messages. Why should it?--you really _have_not_read_ them, so they're truly unread. The thing is that what we want KMail to grab our attention to are not ``unread'' emails, which, having been unread, we might not even want to read. We want KMail to track emails that we actually _want_to_read_ in the current environment. This is a separate concept and it (as far as I think) doesn't have the corresponding IMAP flag of some kind. So, these blue numbers over the tray icon and bold numbers near the folders should not be the ``unread'' messages, but ``to-read'' messages instead. Which surely proves that, given messages in ignored threads are certanly not ``to-read'', messages in ignored threads should not be shown in KMail interface in bold and blue. Marking them read in server is a related, but still a separate thing. And, if there are technical obstacles to separate these concepts, they should be overcome. So, having seen what you have marked as duplicates, I confirm the bug--something should really be fixed.
All nuances and slight misconceptions aside, I would look at this as wish rather than a bug, and so I posted a pragmatic wish as Bug #212897 to have an option for it.
Voted.
This is a *major* annoyance for me as well, so I'm joining and voting for Bug #212897 as well. I'm still posting a comment here because I think that if we don't address this problem (e.g. like in the aforementioned bug/wishlist) this function has IMHO no or even negative effect for an IMAP user. And as such it *is* a bug.
As the related 212897, does it applies to kmail2 too (>=4.5)?
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.
This is still an issue in KDE 4.14.