Disclaimer: I know there are many issues on strict/non-strict
threading, it would be solved by grouping by subject ignoring RE,
but because of the way the headers are I'm wondering if it could
fit the "strict thread" model with a tweak or some work from
me.
There is a specific pattern in in-reply-to headers
I'm seeing a lot with github notifications especially, also some
from gitlab and other similar systems that send comments as
messages.
Message-ID: <LLNL/RAJA/pull/763/review/474761779@github.com>
In-Reply-To: <LLNL/RAJA/pull/763@github.com>
References: <LLNL/RAJA/pull/763@github.com>
Message-ID: <LLNL/RAJA/pull/763/review/474763194@github.com>
In-Reply-To: <LLNL/RAJA/pull/763@github.com>
References: <LLNL/RAJA/pull/763@github.com>
These are from two consecutive emails in a public thread on a
public repo on github (github.com/llnl/raja/pull/763 in case that's
useful somehow). All the messages from this thread use
"In-Reply-To:" <LLNL/RAJA/pull/763@github.com>.
If I do a "Same thread" search, only the current message shows up,
none of the others. I think this is because I didn't receive a
message with exactly that ID, if I get an email notification of the
original issue description, it normally has that ID and threading
works, but there are cases (usually when mentioned later or
similar) where that message may never exist in my IMAP account.
Is there some way either to get mailmate to pretend that email
exists, for me to create one, or get mailmate to include all
messages sharing the same "in-reply-to" in the same-thread set?