Bug 309984

Summary:	email clicked continue to stay unread
Product:	[Applications] kmail2	Reporter:	Marc Collin <marc.collin>
Component:	general	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	normal	CC:	daniel.moyne, devel, montel
Priority:	NOR
Version:	4.9.3
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Marc Collin 2012-11-12 19:27:37 UTC

i received some email, i clicked on it but they continue to stay unread

Reproducible: Didn't try

Steps to Reproduce:
1. click on a received email
2.
3.
Actual Results:  
email stay unread

Expected Results:  
email shoud be read

Comment 1 Marc Collin 2012-11-12 19:47:42 UTC

also sometime when i receive an email it's directly marked read

Comment 2 Laurent Montel 2012-11-13 09:33:44 UTC

Imap ? pop3 ?

Comment 3 Marc Collin 2012-11-13 09:40:52 UTC

pop3

Comment 4 Peter Mühlenpfordt 2012-11-14 12:32:17 UTC

I can confirm this problem with an IMAP server.
~50% of all new mails are not marked as read after opening - even after several times of closing and opening the mail.
I'm using dovecot as IMAP server, the mail is not flagged as read on the server. No errors logged on the server.
Explicit manual marking as read is sometimes the only way to set the flag.

Kontact/Kmail 4.9.2 on Kubuntu 12.10.

Comment 5 Marc Collin 2012-11-14 12:49:28 UTC

i got this problem since i added an imap server (gmail), problem continue after delete it.

Comment 6 Laurent Montel 2012-11-20 07:53:53 UTC

*** Bug 310201 has been marked as a duplicate of this bug. ***

Comment 7 Denis Kurz 2016-09-24 18:03:24 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 8 Denis Kurz 2017-01-07 22:41:41 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.