Bug 294074

Summary:	read IMAP mails are marked unread upon next folder sync
Product:	[Applications] kmail2	Reporter:	Silver Salonen <silver.salonen>
Component:	message list	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	normal	CC:	lukas.schneiderbauer, marc-schmitzer, mauspacker, rodney.baker, t.glaser
Priority:	NOR
Version:	4.9.0
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Silver Salonen 2012-02-14 14:45:41 UTC

Version:           4.8 (using KDE 4.8.0) 
OS:                Linux

For most of my e-mails in most of IMAP-folders on 2 IMAP-accounts (one of them GMail) the messages are permanently marked as read only after the 2nd reading.

This seems to be not related to how e-mails are marked read - it also happens with messages that are marked read by clicking "Mark All Mails as Read" on the message's folder.
Moving the message to another folder (right after reading it the 1st time) does not make any difference either.

Reproducible: Sometimes

Steps to Reproduce:
1) Wait for a new message to arrive
2) Navigate onto that message
3) Go onto some other message
4) Sync the folder again

Actual Results:  
The message is marked as read on the 1st reading
After syncing folder, the message is marked as unread again
After reading it the 2nd time, it stays marked as read

Expected Results:  
The message should stay marked as read on the 1st reading

I've started clicking "Mark Thread as Read" button on every new e-mail after reading it and sometimes (not on every e-mail that afterwards gets unread again) the conflict dialog pops up (to let me choose which e-mail I want to keep - left or right or both).

Comment 1 Lukas Schneiderbauer 2012-03-21 10:27:23 UTC

I experience the same behaviour with kde 4.8.1. (started around 4.7.*)

An additional sympton is, that the mails in the remote (imap) "sent mails" directory are initially marked as unread. (while this is somehow true, this is obviously not, how it should be.)

It should be mentioned, that this behaviour appears only in "disconnected" imap mode.

Comment 2 Silver Salonen 2012-03-21 10:33:09 UTC

In my case it happens with both types of IMAP-accounts.
I sometimes also experience sent mails being unread and this happens indeed with only GMail's disconnected IMAP-account.

Comment 3 Sebastian Ziebarth 2012-04-23 09:54:57 UTC

I can confirm this bug with KDE SC 4.8.2 on Archlinux.

Comment 4 Silver Salonen 2012-08-27 08:58:19 UTC

It still happens in 4.9.0.

Comment 5 Silver Salonen 2012-11-14 14:03:01 UTC

This does not happen in 4.9.3 for me.

BTW, I did not use KMail for quite a long time now, and I also re-created 1 of my 2 IMAP-accounts.

Comment 6 Silver Salonen 2012-11-19 09:03:52 UTC

Actually it still happens, but a lot less, and quite randomly.

Comment 7 Rodney Baker 2013-02-03 02:02:17 UTC

Still happening consistently on KMail2 4.9.5 Release 3. Has any work been done on this yet?

Comment 8 Marc Schmitzer 2013-04-29 18:50:17 UTC

Seeing the same problem here (KMail 4.10.2), but also deleted (not moved-to-trash) Mails re-appearing after folder sync.

Comment 9 Thorsten Glaser 2013-12-27 08:46:06 UTC

I can confirm this somewhat.

As described in http://thread.gmane.org/gmane.comp.kde.users.pim/22033 I cannot mark messages as read *at all* any more in Kontact 4.11.3 but this worked in 4.10.x (whatever was in Debian unstable before 4.11.3). Not on the second, third, etc. attempt.

Deleting messages works.

Marking messages as read in pine (accessing the same folder, whether over IMAP or locally when Kontact accesses it over uw-imapd on localhost) lets Kontact recognise that the message was marked as read.

Comment 10 Denis Kurz 2016-09-24 17:58:14 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 11 Denis Kurz 2017-01-07 22:37:03 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.