Sujet : Re: inn: recommended Message-ID question
De : retroguy (at) *nospam* novabbs.com (Retro Guy)
Groupes : news.software.nntpDate : 13. Sep 2024, 19:03:33
Autres entêtes
Organisation : Rocksolid Light
Message-ID : <d11961524cae1eec2515f03c282393f1$1@novabbs.org>
References : 1 2 3 4
User-Agent : 40tude_Dialog/2.0.15.41
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.