Creating/reusing response codes
From
InterLinked@nntp@phreaknet.org to
news.software.nntp on Fri Jun 26 00:25:08 2026
From Newsgroup: news.software.nntp
Separate from some other NNTP extensions, I've found it convenient to
port the ETRN command from SMTP to NNTP. I know somebody will say
"that's what UUCP is for", but it was infinitely simpler to do this
instead, to allow intermittently connected sites to request a peer to
flush its feed for it.
My inclination, to keep things simple, is to simply use the same
response codes for NNTP ETRN as in SMTP ETRN. Comparing RFC 1985 with
INN's nntp.h, which has all of the common codes as well as a few less
common ones, I don't see any conflicts. So even though the NNTP codes
are generally different than the SMTP ones, it feels like it would be
logical to use those.
In assigning the codes that already exist, was there any process that
went into it, e.g. deliberately making sure that the codes were
different than SMTP for the most part? Any guidance for reusing codes,
or does it not really matter?
--- Synchronet 3.22a-Linux NewsLink 1.2