Path: ...!news.nobody.at!2.eu.feeder.erje.net!feeder.erje.net!nntp.de!.POSTED.akk21-int.akk.kit.edu!not-for-mail
From: Urs =?UTF-8?Q?Jan=C3=9Fen?= <urs@buil.tin.org>
Newsgroups: news.software.nntp
Subject: Re: inn: recommended Message-ID question
Date: Fri, 13 Sep 2024 14:20:26 -0000 (UTC)
Organization: tin.org
Archive: no
Message-ID: <vc1hna$4ja$1@nntp.de>
References: <82047ed9fe64034c6e2327f0131dddae8f595c4e@i2pn2.org>
Injection-Date: Fri, 13 Sep 2024 14:20:26 -0000 (UTC)
Injection-Info: nntp.de; posting-host="akk21-int.akk.kit.edu:2a00:1398:5:f602:cafe:cafe:cafe:21";
	logging-data="4714"; mail-complaints-to="abuse@nntp.de"
User-Agent: tin/2.6.4-20240801 ("Banff") (Linux/6.1.0-23-amd64 (x86_64))
Cancel-Lock: sha1:G6hljGzUzDBXZa+b/WfO8ktMah8=
X-No-Archive: yes
X-No-HTML: yes
Bytes: 1580
Lines: 15

In article <82047ed9fe64034c6e2327f0131dddae8f595c4e@i2pn2.org> Retro Guy wrote:
> I don't know if any readers use the 'recommended Message-ID' line for anything, but i

tin uses it
a) as message-id (not an issue if the posting ends up with a diffrent id)
b) for cancel-locks (that will be an issue)

tinews (nntp inews in perl) uses it
a) as message-id (not an issue if the posting ends up with a diffrent id)
b) for cancel-locks (that will be an issue)
c) for header signing (that will be an issue)

> so I guess the question is, is there a way to not send this info at all?

then the user/reader may still send it's own message-id and you should not
overwirte it as that may break cancel-locks or header signing.