| Deutsch English Français Italiano |
|
<vc23hi$ndn5$1@news.trigofacile.com> View for Bookmarking (what is this?) Look up another Usenet article |
Path: ...!2.eu.feeder.erje.net!feeder.erje.net!proxad.net!feeder1-2.proxad.net!usenet-fr.net!news.trigofacile.com!.POSTED.2a01cb0805ebad00305abb3c8fafda28.ipv6.abo.wanadoo.fr!not-for-mail
From: =?UTF-8?Q?Julien_=C3=89LIE?= <iulius@nom-de-mon-site.com.invalid>
Newsgroups: news.software.nntp
Subject: Re: inn: recommended Message-ID question
Date: Fri, 13 Sep 2024 21:24:34 +0200
Organization: Groupes francophones par TrigoFACILE
Message-ID: <vc23hi$ndn5$1@news.trigofacile.com>
References: <82047ed9fe64034c6e2327f0131dddae8f595c4e@i2pn2.org>
<vc1hna$4ja$1@nntp.de> <47514706fa18eb665b51a417e58b4c9c$1@novabbs.org>
<MID-20240913180108@ram.dialup.fu-berlin.de>
<d11961524cae1eec2515f03c282393f1$1@novabbs.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Injection-Date: Fri, 13 Sep 2024 19:24:34 -0000 (UTC)
Injection-Info: news.trigofacile.com; posting-account="julien"; posting-host="2a01cb0805ebad00305abb3c8fafda28.ipv6.abo.wanadoo.fr:2a01:cb08:5eb:ad00:305a:bb3c:8faf:da28";
logging-data="767717"; mail-complaints-to="abuse@trigofacile.com"
User-Agent: Mozilla Thunderbird
Cancel-Lock: sha1:P33x3c6b8sR8l7qyIte7hLSMAHA= sha256:wWFKX82C1SM2CT6QzX5YI0vsgMlk2InGJhyNPPBCX8U=
sha1:dDwCiEAmW/2lg1h9WDVm3h1djJg= sha256:Us/twI4MyC6BwbehpY1zYxEl9v00BUXAus+exIRhnz8=
In-Reply-To: <d11961524cae1eec2515f03c282393f1$1@novabbs.org>
Bytes: 2914
Lines: 42
Hi Retro Guy,
> 'recommended Message-ID' line [...]
> is there a way to not send this info at all?
This information is always sent by INN and cannot be deactivated.
>> |b'340 Ok, recommended ID <A>\r\n'
>> |b'240 Article posted <B>\r\n'
>
> 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.
A news client is not supposed to do that. The data following the 340
and 240 codes are just comments, with no special meaning defined by the
NNTP protocol. See the example in RFC 3977:
[C] POST
[S] 340 Input article; end with <CR-LF>.<CR-LF>
[C] From: "Demo User" <nobody@example.net>
[C] Newsgroups: misc.test
[C] Subject: I am just a test article
[C] Organization: An Example Net
[C]
[C] This is just a test article.
[C] .
[S] 240 Article received OK
If a news client wants to parse the comments for possible Message-IDs as
INN and maybe other news servers provide them, let's trust the developer
to implement it right and take the one of the 240 response. That would
otherwise be a bug in the implementation.
And if not implemented, you don't mind.
--
Julien ÉLIE
« Il vaut mieux avoir de l'avenir que du passé. »