Sujet : Re: inn: recommended Message-ID question
De : iulius (at) *nospam* nom-de-mon-site.com.invalid (Julien ÉLIE)
Groupes : news.software.nntpDate : 13. Sep 2024, 20:24:34
Autres entêtes
Organisation : Groupes francophones par TrigoFACILE
Message-ID : <vc23hi$ndn5$1@news.trigofacile.com>
References : 1 2 3 4 5
User-Agent : Mozilla Thunderbird
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é. »