Bug 222757 - kmail threading is broken
Summary: kmail threading is broken
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Debian testing Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-01-14 21:03 UTC by Ritesh Raj Sarraf
Modified: 2015-04-12 10:07 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
screenshot of problem (92.22 KB, image/jpeg)
2010-01-14 21:09 UTC, Ritesh Raj Sarraf
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Ritesh Raj Sarraf 2010-01-14 21:03:00 UTC
Version:            (using KDE 4.3.4)
OS:                Linux
Installed from:    Debian testing/unstable Packages

The kmail threading system looks to be weird. Any usual client (though I haven't used the other ones lately) seems to be threading messages based on its message headers, but in case of kmail, the threading seems to be done on the basis of subject keyword.
If kmail finds a subject keyword match, it groups those messages into a single thread, which is wrong.

For example, say, I send a "Hi" message to Person X 2 weeks ago. Now 2 weeks later, I send another "Hi" message to Person X.
These 2 messages are unique. Right ?
Kmail groups both these messages into a single thread.
Comment 1 Ritesh Raj Sarraf 2010-01-14 21:09:07 UTC
Created attachment 39899 [details]
screenshot of problem

As you can see in the screen shot, all messages with subject "Hi" as grouped together.

In fact, I sent a "Hi" message to a different recipient. That message is also grouped into the same incorrect thread.
Comment 2 Ritesh Raj Sarraf 2010-01-14 21:11:56 UTC
Another point to add to the screenshot in Comment #1 is that message threading is broken on another point also. The date. I sent a latest different "Hi" message on the 13th of Jan, 2010. The reply to it has been mis-grouped by kmail into the same old thread.
Comment 3 Björn Ruberg 2010-03-13 00:25:31 UTC
Kmails threading is based on some kind of a thread-ID. Clients that reply to an email will copy this ID. kmail groups all mails with the same ID together. There is no bug here.
Comment 4 Ritesh Raj Sarraf 2010-04-07 14:40:11 UTC
(In reply to comment #3)
> Kmails threading is based on some kind of a thread-ID. Clients that reply to an
> email will copy this ID. kmail groups all mails with the same ID together.
> There is no bug here.

Could you please give it some more thought ?

I don't know the very details of how threading is done but if the other clients are threading differently (and correctly), kmail should do the same. If kmail's threading is based on some kind of thread-ID, which is incorrect, then it should be fixed to be rebased on something else.

Grouping 2 very different messages into one thread because both have the same Subject looks to be the wrong way of associating messages.
Comment 5 Bernd Oliver Sünderhauf 2011-12-14 01:21:25 UTC
Hi Ritesh,
comment #3 is only halfway correct, however this is indeed no bug, but a feature. Admittedly it doesn't work correct in all cases, so this is a valid bug.

While RFC-compatible clients use the "thread-ID" and "references" headers, Microsoft does not, so if the one answering you uses an Outlook client, most other mailreaders can't aggregate them to a thread.
For these cases, Kmail has an additional threading method based on subject. You can turn it on or off in Configure->Appearance->Message List->Default Aggregation->Configure->Groups and Threading->Threading.
Normally it should be off IMHO.

Regards, Pancho
Comment 6 Ritesh Raj Sarraf 2011-12-14 06:18:30 UTC
Yes, that could have been the cause. My environment does have Exchange also. Thanks for the explanation.


I don't have the permissions to change this bugzilla to a feature request, so I'll hope the kdepim folks would do it.
Comment 7 Laurent Montel 2015-04-12 10:07:00 UTC
Thank you for taking the time to file a bug report.

KMail2 was released in 2011, and the entire code base went through significant changes. We are currently in the process of porting to Qt5 and KF5. It is unlikely that these bugs are still valid in KMail2.

We welcome you to try out KMail 2 with the KDE 4.14 release and give your feedback.