From: Daniel Corbe <daniel@corbe.net>
To: Teemu Likonen <tlikonen@iki.fi>
Cc: notmuch@notmuchmail.org
Subject: Re: Fixed Message-ID trouble
Date: Mon, 25 Sep 2023 07:33:23 -0400 [thread overview]
Message-ID: <9F44B9F8-E2DB-4B01-8196-2AA48036A992@corbe.net> (raw)
In-Reply-To: <871qemsewr.fsf@iki.fi>
[-- Attachment #1.1: Type: text/plain, Size: 1265 bytes --]
> On Sep 25, 2023, at 06:52, Teemu Likonen <tlikonen@iki.fi> 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.
Silly question, I know, but have you actually tried reaching out to the user? No MUA that I’m aware of acts like this and it’s pretty clear from documentation and standards tracks that Message-ID is meant to be globally unique per message.
If the user is knowledgeable enough to have a boutique mail reader, they’re probably also knowledgeable enough to correct the defect too.
[-- Attachment #1.2: Message signed with OpenPGP --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2023-09-25 11:33 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 [this message]
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=9F44B9F8-E2DB-4B01-8196-2AA48036A992@corbe.net \
--to=daniel@corbe.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).