Bug 272232

Summary:	kmail reports duplicate messages when marking thread as read before mail download completes
Product:	[Applications] kmail2	Reporter:	Michal Hlavinka <mhlavink>
Component:	general	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	normal	CC:	sven.burmeister, torotil
Priority:	NOR
Version:	2.0.95
Target Milestone:	---
Platform:	Fedora RPMs
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Michal Hlavinka 2011-05-02 12:38:29 UTC

Version:           2.0.95 (using KDE 4.6.2) 
OS:                Linux

I use kmail with imap account. Emails are shown in threads. When going through mailing lists I click on first email and press key shortcut to mark whole thread as read. When I mark thread as read before email in that thread I've clicked on is downloaded, I get question that conflict was found and whether I want to keep left/right/both. It's not difficult to trigger this behaviour, because I have to wait for download to finish if I want avoid that conflict question.

Reproducible: Always

Steps to Reproduce:
1) set some key shortcut for "mark whole thread as read"
2) switch kmail to show messages in threads
3) get some unread thread
4) click on email in that thread
5) press "mark whole thread as read" key shortcut before email downloads

Actual Results:  
conflict resolution question

Expected Results:  
no conflict

Comment 1 S. Burmeister 2011-07-15 00:16:46 UTC

I can confirm this even with KDEPIM 4.7 RC2. bug 274973 and bug 275233 are the same/similar issue.

Comment 2 Roman Zimmermann 2012-11-14 15:26:42 UTC

I experience the same behavior while moving messages from one folder to another (on an IMAP account) - the only difference of the two versions of the message is 5-7s in the "Modified at" header.

Comment 3 Denis Kurz 2016-09-24 17:56:41 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 4 Denis Kurz 2017-01-07 22:30:31 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.