Bug 288208

Summary:	messages won't turn as read
Product:	[Applications] kmail2	Reporter:	Andrei Vasile <andreivasile>
Component:	message list	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	minor	CC:	amantia, korossy, kovin, silver.salonen
Priority:	NOR
Version:	4.7
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Andrei Vasile 2011-12-04 15:09:41 UTC

Version:           4.7 (using KDE 4.7.2) 
OS:                Linux

Read (opened) messages won't turn as read (they stay as unread).

Reproducible: Always

Steps to Reproduce:
Just open KMail.


Expected Results:  
Mark the message as read.

Comment 1 András Manţia 2011-12-09 08:20:06 UTC

Please give details on the type of the account you are using (IMAP, Maildir, Mixedmaildir). You can check that by running akonadiconsole and on the Agents tab click on the account and see in the information area below the Type.
FYI, I can't reproduce with Maildir or IMAP type.

Comment 2 Silver Salonen 2012-01-30 15:33:59 UTC

In my case it happens all the time with IMAP account - I go to a folder having a new e-mail(s), but reading it does not mark it read (most of the times). Sometimes the e-mail is marked as read, but when the next sync occurs, the e-mail is unread again. On the 2nd read it always stays as read.

Comment 3 Silver Salonen 2012-01-30 15:34:17 UTC

BTW, I use 4.8.0.

Comment 4 Petr Kovács 2012-09-05 17:43:37 UTC

I have Kmail 4.8.3 with IMAP accounts and this happens a lot. I will update to 4.8.5 (most recent stable KDE in portage) and see if this problem goes away...

Comment 5 Pal Körössy 2012-11-16 14:24:20 UTC

It randomly happens here in 4.9.3.

Comment 6 Denis Kurz 2016-09-24 18:10:51 UTC

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.

Comment 7 Denis Kurz 2017-01-07 21:59:25 UTC

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.