Sujet : Re: inn: recommended Message-ID question
De : urs (at) *nospam* buil.tin.org (Urs Janßen)
Groupes : news.software.nntpDate : 13. Sep 2024, 15:20:26
Autres entêtes
Organisation : tin.org
Message-ID : <vc1hna$4ja$1@nntp.de>
References : 1
User-Agent : tin/2.6.4-20240801 ("Banff") (Linux/6.1.0-23-amd64 (x86_64))
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.