ietf-nntp MODE READER

[Andrew Gierth]

>>>>> "Stan" == Stan O Barber <sob at verio.net> writes:

 > Russ Allbery wrote:
 >> At the very least, if we're going to be suddenly declaring the way
 >> that INN has behaved since 1991 is non-compliant with the NNTP
 >> protocol, I would like to see this standard standardize a second
 >> port number for the use of server-to-server connections.  It seems
 >> like the least that the standard could offer given a change of
 >> this magnitude.

 Stan> Since when did INN require MODE READER? In my experience with
 Stan> INN, any "reader" command caused it to shift to "reader" mode.

INN requires MODE READER from any client address that is authorised as
both a transit feeder and a reader.

In such cases the client is assumed to be a transit peer until such
time as it issues a MODE READER command, and virtually none of the
reader commands work until then (HEAD <message-id> is supposed to work
on some versions, but no group-oriented commands work at all).

INN does not switch modes other than in response to MODE READER.
However it does automatically start in reader mode in response to
connections from addresses that are not authorised for incoming feeds.

-- 
Andrew.