"Naveen N. Rao" <naveen.n....@linux.vnet.ibm.com> writes: > In my case, I seem to be having the In-Reply-To headers. I end up with > two files per message: one from my inbox and one from the gmane archive > that I pull in. All the messages from the gmane archive seem to have a > re-written 'In-Reply-To' header, but 'Message-Id' and 'References' are > the same.
That sounds like essentially the same issue, due to the fact that notmuch prefers In-Reply-To when choosing a parent for a message. Currently the database is correct (or at least one not-crazy definition of correct): all of the reference and in-reply-to terms are attached to the message document in the database. On the other hand, the in memory data structures currently assume that In-reply-to is a unique value (with ties broken at indexing time). It might be that the solution is to read a list of in-reply-to values and use all of them in threading. At a quick glance, that looks doable; I'm just not sure about unintended consequences. d _______________________________________________ notmuch mailing list notmuch@notmuchmail.org https://notmuchmail.org/mailman/listinfo/notmuch