Teemu Likonen <tlikonen@iki.fi> writes: > Some person on debian-user mailing list seems to be sending messages > with fixed Message-ID field: the same ID in different messages. In > Notmuch it is creating trouble because it connects unrelated threads to > one. The person has different messages in different threads but Notmuch > thinks they are the same message because the Message-ID is the same. > > This is potentially a "denial of service" for Notmuch. Well, not quite, > but is harmful nonetheless. How would a Notmuch user fix the mess or > protect himself against it? By the way, if using the emacs front-end did you try the unthreaded view (U)? That would at least mitigate damage from people replying to the poisoned messages. I could imagine a future version of notmuch considering the identification of files with the same message id as part of "threading", and allowing an unthreaded view to just show all the files, effectively ignoring the message-id. The next step would be to do that selectively for some messages. This all requires a complete redesign of the database schema, so I don't know how realistic it is. d _______________________________________________ notmuch mailing list -- notmuch@notmuchmail.org To unsubscribe send an email to notmuch-leave@notmuchmail.org