#1301 ✓duplicate
Antti Honkela

Honouring References header in threading

Reported by Antti Honkela | November 5th, 2015 @ 07:49 AM

It seems MailMate breaks threads whenever the parent is not listed in "In-Reply-To" but only in "References". (I have some examples of this if needed.)

This is very annoying, as by definition any replies to my replies can never be grouped with the original message.

Would it be possible to add an option to enhance threading by following "References" as well?



Comments and changes to this ticket

  • benny

    benny November 5th, 2015 @ 10:27 AM

    • State changed from “new” to “duplicate”

    If it's only listed in References then I assume it's because it's not really the parent message. Note that MailMate only has a very strict threading mode in which it only shows parent-child relationships. A more liberal mode (just grouping related messages) is often requested (#548) and hopefully I'll get around to implementing it at some point.

    (MailMate does look at “References” if no “In-Reply-To” header exists, but if it does exist then it is assumed to be correct.)

  • Antti Honkela

    Antti Honkela November 5th, 2015 @ 11:24 AM

    Thanks for the clarification!

    The problem I have with this mode is the following. Assume three messages:
    1. outsider -> me
    2. me -> outsider
    3. outsider -> me
    where each of these is a reply to the previous one. Typically I would only have 1 and 3 in the same mailbox while 2 would be in Sent Messages. With the current threading model, MailMate breaks 1 and 3 to separate threads.

    I don't mind if you only have a parent-child model, but what I would like is that MailMate could use the "References" header to bridge over gaps in the graph. It would not seem impossible to add an option that would link messages to the latest one appearing in references if there is no match for "In-Reply-To" in the current mailbox. I am not even asking making this the default, but an option.


  • benny

    benny November 5th, 2015 @ 12:00 PM

    Yes, this is the most common problem with strict threading. I'll note to check to see if this is an easy variation of the current strict threading. Might be a good stop-gap solution until a relaxed group threading mode is available.

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.

New-ticket Create new ticket

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป

Mac OS X email client.

Shared Ticket Bins

People watching this ticket