unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Gregor Zattler <telegraph@gmx.net>
To: Teemu Likonen <tlikonen@iki.fi>, notmuch@notmuchmail.org
Subject: Re: Fixed Message-ID trouble
Date: Mon, 25 Sep 2023 23:53:34 +0200	[thread overview]
Message-ID: <87o7hphqch.fsf@no.lan> (raw)
In-Reply-To: <874jjiskeo.fsf@iki.fi>

Hi Teemu, notmuch users,
* Teemu Likonen <tlikonen@iki.fi> [2023-09-25; 11:54 +03]:
> 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?

would you please give details of some such posts?  Then
other people are able to investigate.

Ciao; Gregor

  parent reply	other threads:[~2023-09-25 22: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
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 [this message]
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=87o7hphqch.fsf@no.lan \
    --to=telegraph@gmx.net \
    --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).