Bug 303900

Summary:	Same-Subject-Problem: Mail was displayed as answer to a mail from someone else
Product:	[Applications] kmail2	Reporter:	Christian S. <christian.schlasza>
Component:	message list	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	normal
Priority:	NOR
Version:	4.8.4
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Christian S. 2012-07-21 20:09:19 UTC

Some week ago I received a mail with the subject "Hi".
Today I wrote a message to another person with the same subject "Hi".
When I received the answer to my mail I wrote today, this answer was misplaced by KMail in a way to show it as a sub-tree of the first message I received some week ago.
I noticed it only because the newly received mail was displayed in blue.

Today I also installed the akonadi-plugin for googlemail-data to synchronize my contacts. Maybe it could have happened because of that.

I made screenshot (blurred out all private data, eg. surnames) to demonstrate the behaviour.
Since I cannot load it up here, please contact me if you want to see it.

For the rest I want to thank you for the good experiences I have made with KMail!


Reproducible: Didn't try

Steps to Reproduce:
1. Receive a mail with a certain subject, eg. "Hi"
2. Write a mail to someone else with this subject
3. Receive the answer and see it placed sub-grouped with the first received mail from the first person.
Actual Results:  
Mail is placed in wrong sub-group

Expected Results:  
Mail should be placed in no subgroup

Comment 1 Denis Kurz 2016-09-24 18:06:25 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 21:55:52 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.