RFC 977:Network News Transfer Protocol: ...
RFC-Ref

NNTP


Click on the red underlined text to get to the source

... NNTP specifies a protocol for the distribution, inquiry, retrieval, and posting of news articles using a reliable stream (such as TCP ...
... TCP) server-client model. NNTP is designed so that news articles need only be stored on one (presumably central) host, and subscribers ...
... NNTP is modelled upon the news article specifications in RFC 850(-> 1036), which describes the USENET ...
... 850(-> 1036), which describes the USENET news system. However, NNTP makes few demands upon the structure, content, or storage of news articles, and thus we believe it easily can be adapted to other non-USENET ...
... Typically, the NNTP server runs as a background process on one host, and would accept connections ...
... This specification does not cover the operation of slave NNTP servers. We merely suggest that slave servers are a logical addition to NNTP ...
... NNTP servers. We merely suggest that slave servers are a logical addition to NNTP server usage which would enhance operation on large local area networks. ...
... NNTP has commands which provide a straightforward method of exchanging articles between cooperating hosts ...
... network and who wish to actually obtain copies of news articles for local storage might well find NNTP to be a more efficient way to distribute news than more traditional transfer methods (such as UUCP). ...
... Using NNTP, hosts exchanging news articles have an interactive mechanism for deciding which articles are to be transmitted. A host ...
... desiring new news, or which has new news to send, will typically contact one or more of its neighbors using NNTP. First it will inquire if any new news groups have been created ...


... The NNTP Specification ...
... The following is a list of general response codes that may be sent by the NNTP server. These are not specific to any one command, but may be returned as the result of a connection, a failure, or some unusual ...
... In general, 1xx codes may be ignored or displayed as desired; code 200 or 201 is sent upon initial connection to the NNTP server depending upon posting permission; code 400 will be sent when the NNTP ...
... NNTP server depending upon posting permission; code 400 will be sent when the NNTP server discontinues service (by operator request, for example); and 5xx codes indicate that the command could not be performed for ...


... On the following pages are descriptions of each command recognized by the NNTP server and the responses which will be returned by those commands. ...
... Each command is shown in upper case for clarity, although case is ignored in the interpretation of commands by the NNTP server. Any parameters are shown in lower case. A parameter shown in [square brackets] is optional. For example, [GMT ...
... Every command described in this section must be implemented by all NNTP servers. ...
... by the server host's news software and not necessarily the NNTP server itself. ...
... moderator who will post them for the submitter. This is independent of the posting permission granted to a client by the NNTP server. Please note that an empty list (i.e., the text body returned by this ...
... client to indicate that it has finished all its transactions with the NNTP server. ...
... implementation dependent, and may vary from one host to another. In NNTP servers which do not give priority to slave servers, this command must nonetheless be recognized and acknowledged. ...


... connection on TCP port 119) S: 201 Foobar NNTP server ready (no posting) (client ...
... session) C: QUIT S: 205 Foobar NNTP server bids you farewell. ...
... The following are the commands recognized and responses returned by the NNTP server. ...



Google
Web
RFC-Ref