Bug 129973

Summary:	References threading breaks when original message is not available
Product:	[Applications] kmail2	Reporter:	Francis J. Lacoste <francis.lacoste>
Component:	general	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	normal	CC:	bjoern, jjm, montel, nick
Priority:	NOR
Version:	4.11.1
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Francis J. Lacoste 2006-06-28 16:16:26 UTC

Version:            (using KDE KDE 3.5.3)
Installed from:    Ubuntu Packages

I have a set of messages which are related (they share the same References: field) but the message actually referenced is not available (was deleted for example or I never got because subscribed to the list later on).

Ex:
Msg1: Original Msg (Missing)
   Msg2 (References: Msg1)
   Msg3 (References: Msg1)
   Msg4 (References: Msg1)

The messages won't be grouped together and will be considered separate messages:

Ex:
Msg2
Some other message
Msg3
Yet anot message
Msg4 

mutt will thread those messages correctly, it even display a broken line to show that the original message
is not there:

| Msg2
| Msg3
| Msg4

Evolution, also threads those messages, but in a somewhat not exactly correct way:

|  Msg2
   | Msg3
   | Msg4


I hope this is fixable in KMail.

Comment 1 Jonathan Marten 2013-06-12 19:10:11 UTC

Possible duplicate of bug 279115.

Comment 2 Nick Leverton 2013-09-17 12:01:39 UTC

Still an issue in 4.11.1

Comment 3 Laurent Montel 2013-09-17 12:45:21 UTC

I will look at how I can fix it.
It's right I saw it.

Comment 4 Denis Kurz 2016-09-24 18:07:58 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 5 Denis Kurz 2017-01-07 22:29:38 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.