Re: Quick question for interest's sake

On Mittwoch, 7. März 2018 14:17:27 CET Erik Quaeghebeur wrote:
> On woensdag 7 maart 2018 13:23:53 CET, Ian Seeks wrote:
> > Why do none of the emails in this list from
> > <[email protected]> with the same subject ever form a
> > thread?

Ian, did you probably confused this list (kdepim-users) with the kde-pim list?


> I haven't seen any phabricator mails on this list, but my guess would be
> that phabricator does not (correctly?) set the In-Reply-To and References
> headers used for threading.
> 
> I do not know which threading algorithm KMail uses, but a well-known one is
> Jamie Zawinski's <https://www.jwz.org/doc/threading.html>.

I haven't check what Jamie Zawinski writes.

If the "Standard Mailing List" aggregration is enabled, then KMail threads (in 
this order of preference) by:
1.) In-Reply-To
2.) References
3.) Subject

A message that is threaded by Subject is put under the message that is closest 
in date.


> By having a look at the phabricator mails' headers, you can probably see
> what is going on and, if something can be corrected or improved, file a bug
> report
> <https://secure.phabricator.com/book/phabcontrib/article/bug_reports/>.

Here are some headers of such a message:

=====
Message-Id: <[email protected]>
References: <differential-rev-PHID-DREV-pnagm7x6ynd2f6dss5zr-
[email protected]>
In-Reply-To: <differential-rev-PHID-DREV-pnagm7x6ynd2f6dss5zr-
[email protected]>
=====

All Message-Id headers seem to have the same pattern. All messages belonging 
to the same Phabricator issue (e.g. a review request) seem to have identical 
References and In-Reply-To headers. Obviously, their format is completely 
different from the Message-Id headers.

So, it's not surprising that KMail is not able to thread the messages by In-
Reply-To or References. I don't understand why KMail doesn't thread by subject 
instead.


Regards,
Ingo

-----BEGIN PGP SIGNATURE-----

iF0EABECAB0WIQRxKgkQMhrHYtSAVAgadH5FMOC52AUCWqBAowAKCRAadH5FMOC5
2H7DAKC9LY48sQNrk5+ySQLjHQldZfX+CACffNbRMS3VZWHcPsLqValWNThFsyU=
=fB67
-----END PGP SIGNATURE-----