Bug 266498

Summary:	"New" messages are not recognised as such, and displayed using the "unread" colour in the message list.
Product:	[Applications] kmail2	Reporter:	Peter Lewis <pete>
Component:	message list	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED NOT A BUG
Severity:	normal	CC:	bugs.kde.org, der.ole.becker, kde, montel, prozac, vladimir.didenko
Priority:	NOR
Version:	2.0.89
Target Milestone:	---
Platform:	Arch Linux
OS:	Linux
Latest Commit:		Version Fixed In:

Description Peter Lewis 2011-02-17 01:21:13 UTC

Version:           2.0.89 (using KDE 4.6.0) 
OS:                Linux

As it says really, messages that are new are not displayed with the colour for "new messages" - in fact they are not recognised as being new, only unread.

This may be related:

kmail2(25598)/libakonadi Akonadi::MessageStatus::setStatusFromFlags: Unknown flag: "Old"

This is using IMAP, and the server is dovecot 2.0.9, in case that matters.


Reproducible: Always

Comment 1 eric 2011-02-23 01:27:27 UTC

This also happens with POP3 servers and this also happened with the latest few version of the previous Kmail/Kontact.

Comment 2 Peter Lewis 2011-02-23 09:53:28 UTC

Interesting. But to confirm, it is a regression since 1.13.6, since that version behaves correctly for me.

Comment 3 Oliver Becker 2011-06-16 10:43:27 UTC

It also happens with 2.1.0 with the Google IMAP server which worked well before.

Comment 4 Ronny Multrus 2011-10-10 12:19:20 UTC

I can confirm this for KDE 4.7.2. In the last days I switched from 4.6 to 4.7 (with KMail from 4.4 to 4.7) and I haven't seen a single new message in red color, new and unread ones are both in blue.

Comment 5 Laurent Montel 2011-10-26 17:44:48 UTC

"new message" is not valid in akonadi version.
Not a regression. We decided to remove this status.

Comment 6 Jonathan M Davis 2011-10-26 18:39:05 UTC

Then it needs to be removed from kmail. If the feature is removed, then it's removed. But leaving it in but not working is definitely not good.

Comment 7 Laurent Montel 2011-10-26 19:07:32 UTC

it was already removed in 4.7.3

Comment 8 Peter Lewis 2011-10-27 09:04:24 UTC

Wow, okay. Of course I respect your right to make decisions about the software, but that's a shame. It provided a really nice workflow, I thought.