Sujet : Re: inn: recommended Message-ID question
De : retroguy (at) *nospam* novabbs.com (Retro Guy)
Groupes : news.software.nntpDate : 13. Sep 2024, 22:48:00
Autres entêtes
Organisation : Rocksolid Light
Message-ID : <e26083cfe6dcb2558ed43bd8da24989f@www.novabbs.org>
References : 1 2 3 4 5 6
User-Agent : Rocksolid Light
On Fri, 13 Sep 2024 19:24:34 +0000, Julien ÉLIE wrote:
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:
<snip>
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.
Thank you for the info Julian!
I'll then continue as I am now, producing a mid for articles which do
not already contain one.
-- Retro Guy