Mark Walters <markwalters1009@gmail.com> writes:

>>> I haven't tracked through all the logic of the existing algorithm for
>>> this case. But I don't like hearing that notmuch constructs different
>>> threads for the same messages presented in different orders. This sounds
>>> like a bug separate from what we've discussed above. 
>
> I think I have now found this bug and it is separate from the malformed
> In-Reply-To problems.
>
> The problem is that when we merge threads we update all the thread-ids
> of documents in the loser thread. But we don't (if I understand the code
> correctly) update dangling "metadata" references to threads which don't
> (yet) have any documents.

This bug seems fixed by the introduction of ghost messages discussed
later in the thread, so marking it fixed. The question of malformed
In-Reply-To headers (and whether there is a bug handling those) is
discussed in the thread id:20211226161716.2079457-1-david@tethera.net.
_______________________________________________
notmuch mailing list -- notmuch@notmuchmail.org
To unsubscribe send an email to notmuch-leave@notmuchmail.org