Bug 292952

Summary:	Kmail marks replied email as replied only for few seconds
Product:	[Applications] kmail2	Reporter:	masaj
Component:	message list	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	normal	CC:	woebbeking, wrana
Priority:	NOR
Version:	4.9.98 RC3
Target Milestone:	---
Platform:	Arch Linux
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description masaj 2012-01-31 10:49:53 UTC

Version:           4.8 (using KDE 4.8.0) 
OS:                Linux

When I reply to any mail in my 2 IMAP accounts configured, kmail won't remain such a mail marked as replied (or only for few seconds, then the replied icon disappears)

Reproducible: Always

Steps to Reproduce:
Reply to a mail

Actual Results:  
Mail not marked as replied

Expected Results:  
Mail marked as replied

Comment 1 Daniel Wrana 2012-07-02 08:32:36 UTC

I can confirm this bug. The flags are deleted when the imap-account is synced again. Also the flag for attachements is generally not set. Kmail2 4.8.3 on Kubuntu 12.04

Comment 2 masaj 2012-07-09 07:04:12 UTC

This is not the case for all accounts, as I mentioned in my initial comment. I'm having 2 accounts (Gmail & IMAP by Exchange), where Gmail account works in a proper way.

Comment 3 Daniel Wrana 2012-08-09 08:20:12 UTC

Further investigations. It is not the case on accounts running on OHV-Provider with Unix-Environment. It is the case for an exchange account. Connection with POP to the exchange account works as expected (current workaround), with imap-connection to the mailserver the marks are delted at the next syncing.

Comment 4 masaj 2013-01-31 11:18:16 UTC

Reply/Forward icons dissappear also in 4.10 RC3..

Comment 5 Denis Kurz 2016-09-24 18:13:44 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 6 Denis Kurz 2017-01-07 22:37:29 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.