On 2/12/19 8:09 AM, Stephen J. Turnbull wrote:
I suppose HyperKitty uses References (it works for messages that have proper Message-IDs ;-), but I don't know what algorithm it uses. Might be worth looking into, as well as considering a more Postelian parsing of Message-IDs. Specifically, take the field body, unfold it, strip leading and trailing whitespace and leading "<" and trailing ">", and whatever's left is the message ID.
Hyperkitty uses In-Reply-To: and if absent falls back to the last item in References: to determine a message's parent.
I haven't looked at what happens if the parent is not in the archive but arrives later.
We could look at earlier References: items to try to find one we know, but this could result in bad threading if a later reference arrives after we think we've determined the parent.
The unfolding of Message-ID: is now correct. See https://gitlab.com/mailman/hyperkitty/merge_requests/125.
-- Mark Sapiro firstname.lastname@example.org The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan