Hello, This sounds like a nasty problem indeed. OTOH, “there’s nothing that couldn’t be” as my granny would have put it.
Bearing in mind that re-recognising a message which has arrived multiple times via different routes is a worthwhile feature, it would seem to me that a hash over the invariant part of the message, that is the body, would allow for such detection. In that light, it would seem to me that the tuple (body_hash, message_id) could be a candidate for a “unique enough”(tm) identifier? --alex -- www.condition-alpha.com / @c_alpha Sent from my iPhone; apologies for brevity and autocorrect weirdness. > On 25. Sep 2023, at 14:00, Teemu Likonen <tliko...@iki.fi> wrote: > > * 2023-09-25 07:33:23-0400, Daniel Corbe wrote: > >> Silly question, I know, but have you actually tried reaching out to >> the user? > > Not silly, but I don't even know who the person is. All I see is the > mess, and everything else is my interpretation of the cause. Notmuch > Emacs tree mode shows messages' relations but they are not accurate if > references are messed up. It's difficult to dig into Message-ID level of > relations. > > Perhaps my wish is that there was an easy way to break threads: mark a > message as origin of a new thread. Or perhaps I just use my custom > ignore mechanism to mark messed threads automatically as read and move > on. > > -- > /// Teemu Likonen - .-.. https://www.iki.fi/tlikonen/ > // OpenPGP: 6965F03973F0D4CA22B9410F0F2CAE0E07608462 > _______________________________________________ > notmuch mailing list -- notmuch@notmuchmail.org > To unsubscribe send an email to notmuch-le...@notmuchmail.org
signature.asc
Description: Binary data
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ notmuch mailing list -- notmuch@notmuchmail.org To unsubscribe send an email to notmuch-le...@notmuchmail.org
