Path: ...!weretis.net!feeder9.news.weretis.net!news.nk.ca!rocksolid2!i2pn2.org!.POSTED!not-for-mail
From: Retro Guy <retroguy@novabbs.com>
Newsgroups: news.software.nntp
Subject: Re: inn: recommended Message-ID question
Date: Fri, 13 Sep 2024 07:26:09 -0700
Organization: Rocksolid Light
Message-ID: <47514706fa18eb665b51a417e58b4c9c$1@novabbs.org>
References: <82047ed9fe64034c6e2327f0131dddae8f595c4e@i2pn2.org> <vc1hna$4ja$1@nntp.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
Injection-Info: i2pn2.org;
	logging-data="1914804"; mail-complaints-to="usenet@i2pn2.org";
	posting-account="PGd4t4cXnWwgUWG9VtTiCsm47oOWbHLcTr4rYoM0Edo";
User-Agent: 40tude_Dialog/2.0.15.41
X-Spam-Checker-Version: SpamAssassin 4.0.0
Bytes: 1878
Lines: 23

On Fri, 13 Sep 2024 14:20:26 -0000 (UTC), Urs Jan�en wrote:

> 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.

Thanks for this info!

On my servers if the client sends it's own message-id, that is the mid used
for the message, so if I'm reading properly it should not be an issue in
most cases. Hoping I understand correctly :)