Version: 4.7 (using KDE 4.7.2) OS: Linux If I set KMail to jump to the first unread message in a folder (Configure KMail->Misc->Folders->When entering a folder), and leave KMail in the Inbox (leave a message in the Inbox selected), when new messages are downloaded automatically, they are first jumped to, then marked read, and filters are only applied after that. If messages are moved to another folder automatically (by filters), one will not notice new messages because of this behaviour. Reproducible: Always Steps to Reproduce: Just set up some filters to sort messages into folders, leave a message in your Inbox selected, and wait for new mail (for which filter rules apply) to arrive. Actual Results: Messages first marked read and then moved to the folder specified by the filter. Expected Results: Messages should be moved to their place by the filter, but they should be left unread.
WE improved a lot filter in 4.8 We can't backport to 4.7.x sorry
I think it is not a bug in the filtering part, but rather in the logic of folder handling: if a new message arrives, kmail should first call the filters, and then do whatever it does when new mail arrives. Or even better: "when opening a folder, jump to the first unread message" should mean it jumps to the first unread message when the folder is opened, and not if it is already open, but new mail arrives into it.
*** Bug 294828 has been marked as a duplicate of this bug. ***
I dont think it is a bug in the filtering part. This will also happend when you are reading an e-mail as well. What is used is highlighting the e-mail and read it in the preview pan. Tony
*** Bug 295225 has been marked as a duplicate of this bug. ***
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present? If noone confirms this bug for a Framework-based version of kmail2 (version 5.0 or later, as part of KDE Applications 15.12 or later), it gets closed in about three months.
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.