Version: unspecified (using KDE 4.7.0) OS: Linux Whenever I get a new E-Mail, they are not marked as unread at all. Since filtering of E-Mails miracuously works, they are sorted in their respective folder but you never know if there are any new mails there. (Also, the "New mail notification" was disabled by default) Reproducible: Always Steps to Reproduce: Send yourself an E-Mail or get an E-Mail by somebody else Actual Results: The mails appear in inbox when Akonadi was looking for mail but they are not marked as unread Expected Results: The new mails must be marked as unread.
Works fine here.
Works fine on my notebook as well where I am using a blank install of Kubuntu Oneiric and a fresh KDE install and a fresh KMail2 install. On my main machine where I upgraded from KMail to KMail2 the thing is all screwed up :(
I confirm also that it doesn't show them as unread. I see them counted in the folder (under unread column) but I don't see them formated (blue colour) as unread. So, it is hard to find them unless you use the manual method described above. And like Kai, I also migrated and wouldn't like to reset and import everything manually. There must be a way to fix this. Thanks!
worked fine for a while, but stopped recently for no obvious reason (maybe after a minor update). Unread messages are not marked blue in the list, and no more counter in the system tray icon. Acoustic notification when new message arrives still works. kmail2: 4.7.4-3.27.2
marking new messages as unread still not working with version 4.8.0-325.2. (Manually marking as unread works and shows message line in blue and counter in tray icon)
news on the subject: incoming new messages are correctly marked as "unread" again! What happened ? no update, but I ran into the "retrieving folder contents bug" so I had to restart the Akonadi server. Since then new messages are marked unread correctly again!
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.