Bug 295032

Summary:	KMail complains about conflict when sending a mail to a message list I'm subscribed to
Product:	[Applications] kmail2	Reporter:	Marcus Harrison <marcus>
Component:	general	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	normal
Priority:	NOR
Version:	1.99.0
Target Milestone:	---
Platform:	Unlisted Binaries
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Marcus Harrison 2012-02-28 22:38:02 UTC

Version:           1.99.0
OS:                Linux

I have KMail configured so that my accounts all use their own Inbox folder as their, "Sent Messages" folder, so as soon as an E-mail is sent it is sent to my Inbox. This is for clarity when reading threaded E-mail conversations.

However, this presents a problem when sending E-mail to a mailing list that I'm subscribed to - as both the E-mail I have just sent and the new E-mail coming in from the mailing list both go to my Inbox, it results in a conflict between the two messages every single time.

This could potentially happen with, "Keep Replies in This Folder" option selected on the Inbox (or another folder if you're using E-mail filters) as well.

Reproducible: Always

Steps to Reproduce:
1. Compose a new message to the KDE-PIM mailing list (if you are subscribed) or alternatively, to the same E-mail address as you are sending it from
2. Click View --> Sent-Mail Folder and select your current inbox as the sent-mail folder
3. Write yourself a nice message. Put a smiley face on the end.
4. Send it
5. If necessary, click "Check Mail" or right-click on your inbox and click "Update Folder" (I didn't find this necessary)

Actual Results:  
A nasty pop-up box about resolving conflicts pops up.

Expected Results:  
The Inbox folder should display both messages as separate and distinct objects.

OS: Linux (i686) release 3.0.0-16-generic
Compiler: gcc

Comment 1 Denis Kurz 2016-09-24 18:23:57 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 2 Denis Kurz 2017-01-07 22:13:40 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.