Path: ...!weretis.net!feeder9.news.weretis.net!i2pn.org!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 11:03:33 -0700
Organization: Rocksolid Light
Message-ID: <d11961524cae1eec2515f03c282393f1$1@novabbs.org>
References: <82047ed9fe64034c6e2327f0131dddae8f595c4e@i2pn2.org> <vc1hna$4ja$1@nntp.de> <47514706fa18eb665b51a417e58b4c9c$1@novabbs.org> <MID-20240913180108@ram.dialup.fu-berlin.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Injection-Info: i2pn2.org;
	logging-data="1935180"; 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: 1941
Lines: 24

On 13 Sep 2024 17:02:10 GMT, Stefan Ram wrote:

> Retro Guy <retroguy@novabbs.com> wrote or quoted:
>>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 :)
> 
>   Yeah, it's the same here. I write the message-ID I want in my
>   headers. Then I send my message with a small Python script.
>   That script shows the messages from the news server verbatim:
> 
>|b'340 Ok, recommended ID <A>\r\n'
>|b'240 Article posted <B>\r\n'
> 
>   , where <A> is the ID the server recommends and <B> is the 
>   message-ID from my header lines.

That sounds good.

What I want to avoid is a client using the "Ok, recommended ID", not
sending a MID, then relying on that recommended ID. My server creates a MID
for messages that do NOT contain a MID, after the message is received, but
before the connection is closed.

If you geneerate a MID at the client, that is what is used.