From: Michael J Gruber <michaeljgruber+grubix+git@gmail.com>
To: Teemu Likonen <tlikonen@iki.fi>
Cc: notmuch@notmuchmail.org
Subject: Re: Fixed Message-ID trouble
Date: Mon, 25 Sep 2023 12:59:25 +0200 [thread overview]
Message-ID: <CAA19uiRv-mg2Z=4ZzBy69zmo7hPkBjLDx4Y0j3p_7QaJNiK-pQ@mail.gmail.com> (raw)
In-Reply-To: <871qemsewr.fsf@iki.fi>
Am Mo., 25. Sept. 2023 um 12:53 Uhr schrieb Teemu Likonen <tlikonen@iki.fi>:
>
> * 2023-09-25 11:54:07+0300, Teemu Likonen wrote:
>
> > 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?
>
> I am no longer sure if this issue is caused by fixed "Message-ID" or
> wrong "References" or "In-Reply-To" values. Anyway, someone has created
> real mess anyway because Notmuch combines originally separate threads
> now and forever.
Yes, several sources of different badness ...
Still, if I understand correctly, a new message with a pre-existing
mid ends up being registered by notmuch as a second file for the
"same" message irrespective of differences in the actual files. For
message copies which you receive via different paths (say directly
plus via an ml) this may or may not be what you want. Used
intentionally, it may create harm - how do other mailers handle this?
Show them in parallel in the same thread (but as individual messages)?
Michael
next prev parent reply other threads:[~2023-09-25 11:05 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-25 8:54 Fixed Message-ID trouble Teemu Likonen
2023-09-25 10:52 ` Teemu Likonen
2023-09-25 10:59 ` Michael J Gruber [this message]
2023-09-25 11:33 ` Daniel Corbe
2023-09-25 12:00 ` Teemu Likonen
2023-09-25 13:10 ` Alexander Adolf
2023-09-26 10:13 ` David Bremner
2023-09-26 11:44 ` Alexander Adolf
2023-09-26 12:15 ` Andreas Kähäri
2023-09-26 16:22 ` Alexander Adolf
2023-09-26 10:07 ` David Bremner
2023-09-26 12:46 ` Teemu Likonen
2023-09-26 17:17 ` David Bremner
2023-09-25 21:53 ` Gregor Zattler
2023-09-25 23:00 ` Andy Smith
2023-09-25 22:45 ` Daniel Kahn Gillmor
2023-09-27 16:48 ` David Bremner
2023-09-28 5:51 ` Teemu Likonen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAA19uiRv-mg2Z=4ZzBy69zmo7hPkBjLDx4Y0j3p_7QaJNiK-pQ@mail.gmail.com' \
--to=michaeljgruber+grubix+git@gmail.com \
--cc=notmuch@notmuchmail.org \
--cc=tlikonen@iki.fi \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).