Re: inn: recommended Message-ID question

On Fri, 13 Sep 2024 14:20:26 -0000 (UTC), Urs Janßen wrote:

In article <82047ed9fe64034c6e2327f0131dddae8f595c4e@i2pn2.org> Retro Guy wrote:

I don't know if any readers use the 'recommended Message-ID' line for anything, but i

 
tin uses it
a) as message-id (not an issue if the posting ends up with a diffrent id)
b) for cancel-locks (that will be an issue)
 
tinews (nntp inews in perl) uses it
a) as message-id (not an issue if the posting ends up with a diffrent id)
b) for cancel-locks (that will be an issue)
c) for header signing (that will be an issue)
 

so I guess the question is, is there a way to not send this info at all?

 
then the user/reader may still send it's own message-id and you should not
overwirte it as that may break cancel-locks or header signing.

Thanks for this info!

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 :)