draft-ietf-nntpext-base-07.txt   draft-ietf-nntpext-base-08.txt 
INTERNET DRAFT S. Barber INTERNET DRAFT S. Barber
Expires: June 7, 1999 Academ Consulting Services Expires: February, 10, 2000 Academ Consulting Services
December 1998 August 1999
Network News Transport Protocol Network News Transport Protocol
draft-ietf-nntpext-base-07.txt draft-ietf-nntpext-base-08.txt
1. Status of this Document 1. Status of this Document
This document is an Internet-Draft. Internet-Drafts are This document is an Internet-Draft and is in full conformance
working documents of the Internet Engineering Task Force with Section 10 of RFC 2026. Internet-Drafts are working
(IETF), its areas, and its working groups. Note that other documents of the Internet Engineering Task Force (IETF),
its areas, and its working groups. Note that other
groups may also distribute working documents as Internet- groups may also distribute working documents as Internet-
Drafts. Drafts.
Internet-Drafts are draft documents valid for a maximum of six Internet-Drafts are draft documents valid for a maximum of six
months and may be updated, replaced, or made obsolete by other months and may be updated, replaced, or made obsolete by other
documents at any time. It is inappropriate to use Internet- documents at any time. It is inappropriate to use Internet-
Drafts as reference material or to cite them other than as Drafts as reference material or to cite them other than as
"work in progress." "work in progress."
To learn the current status of any Internet-Draft, please The list of current Internet-Drafts can be accesses at
check the "1id-abstracts.txt" listing contained in the http://www.ietf.org/ietf/1id-abstracts.txt.
Internet-Drafts Shadow Directories on ftp.is.co.za (Africa),
nic.nordu.net (Europe), munnari.oz.au (Pacific Rim), The list of Internet-Draft shadown directories can be accessed
ftp.ietf.org (US East Coast), or ftp.isi.edu (US West at http://www.ietf.org/shadow.html.
Coast).
This section will be updated with the appropriate verbiage
from RFC 2223 should this document has been found ready for
publication as an RFC.
This document is a product of the NNTP Working Group, chaired This document is a product of the NNTP Working Group, chaired
by Ned Freed and Stan Barber. by Ned Freed and Stan Barber.
2. Abstract 2. Abstract
The Network News Transport Protocol has been in use in the The Network News Transport Protocol has been in use in the
Internet for a decade and remains one of the most popular Internet for a decade and remains one of the most popular
protocols (by volume) in use today. This document is a protocols (by volume) in use today. This document is a
replacement for RFC 977 and officially updates the protocol replacement for RFC 977 and officially updates the protocol
specification. It clarifies some vagueness in RFC 977, specification. It clarifies some vagueness in RFC 977,
skipping to change at line 55 skipping to change at page 2, line 8
(NNTP), which is used for the distribution, inquiry, (NNTP), which is used for the distribution, inquiry,
retrieval, and posting of net news articles using a reliable retrieval, and posting of net news articles using a reliable
stream-based mechanism. For news reading clients, NNTP enables stream-based mechanism. For news reading clients, NNTP enables
retrieval of news articles that are stored in a central retrieval of news articles that are stored in a central
database, giving subscribers the ability to select only those database, giving subscribers the ability to select only those
articles they wish to read. articles they wish to read.
The netnews model provides for indexing, cross-referencing, The netnews model provides for indexing, cross-referencing,
and expiration of aged messages. For server-to-server and expiration of aged messages. For server-to-server
interaction, NNTP is designed for efficient transmission of interaction, NNTP is designed for efficient transmission of
Barber [Page 1]
net news articles over a reliable full duplex communication net news articles over a reliable full duplex communication
method. method.
Every attempt is made to insure that the protocol Every attempt is made to insure that the protocol
specification in this document is compatible with the version specification in this document is compatible with the version
specified in RFC 977[1]. However, this version does not specified in RFC 977[1]. However, this version does not
support the ill-defined SLAVE command and permits four digit support the ill-defined SLAVE command and permits four digit
years to be specified in the NEWNEWS and NEWGROUPS commands. years to be specified in the NEWNEWS and NEWGROUPS commands.
It changes the default character set to UTF-8[2] instead of It changes the default character set to UTF-8[2] instead of
US-ASCII[3]. It also extends the newsgroup name matching US-ASCII[3]. It also extends the newsgroup name matching
skipping to change at line 105 skipping to change at page 3, line 4
represent the client host and a "[S]" will be used to represent the client host and a "[S]" will be used to
represent the server host. represent the server host.
4. Basic Operation. 4. Basic Operation.
Every NNTP session MUST involve the following in this order: Every NNTP session MUST involve the following in this order:
CONNECTION CONNECTION
GREETING GREETING
DISCONNECTION DISCONNECTION
Other steps may occur between the GREETING and DISCONNECTION Other steps may occur between the GREETING and DISCONNECTION
step. They are: step. They are:
Barber [Page 2]
CAPABILITIES DISCOVERY CAPABILITIES DISCOVERY
NEWS EXCHANGE NEWS EXCHANGE
CONCLUSION CONCLUSION
NNTP operates over any reliable data stream 8-bit-wide NNTP operates over any reliable data stream 8-bit-wide
channel. When running over TCP/IP, the official port for the channel. When running over TCP/IP, the official port for the
NNTP service is 119. Initially, the server host starts the NNTP service is 119. Initially, the server host starts the
NNTP service by listening on a TCP port. When a client host NNTP service by listening on a TCP port. When a client host
wishes to make use of the service, it MUST establish a TCP wishes to make use of the service, it MUST establish a TCP
connection with the server host by connecting to that host on connection with the server host by connecting to that host on
skipping to change at line 152 skipping to change at page 3, line 49
NOT exceed 12 US-ASCII characters. Command lines MUST NOT NOT exceed 12 US-ASCII characters. Command lines MUST NOT
exceed 512 octets, which includes the terminating US-ASCII exceed 512 octets, which includes the terminating US-ASCII
CRLF pair. Arguments MUST NOT exceed 497 octets. CRLF pair. Arguments MUST NOT exceed 497 octets.
Each response MUST start with a three-digit response code that Each response MUST start with a three-digit response code that
is sufficient to distinguish all responses. Unless is sufficient to distinguish all responses. Unless
specifically specified as one of the valid responses for a specifically specified as one of the valid responses for a
command (such as those described later in this document), each command (such as those described later in this document), each
response is contained in a single line. However, certain response is contained in a single line. However, certain
commands MAY permit multi-line responses. All multi-line commands MAY permit multi-line responses. All multi-line
responses MUST adhear to the following format: After sending responses MUST adhere to the following format: After sending
the first line of the response and an US-ASCII CRLF, any the first line of the response and an US-ASCII CRLF, any
additional lines are sent, each terminated by an US-ASCII CRLF additional lines are sent, each terminated by an US-ASCII CRLF
pair. When all lines of the response have been sent, a final pair. When all lines of the response have been sent, a final
line MUST be sent, consisting of a termination octet (US-ASCII line MUST be sent, consisting of a termination octet (US-ASCII
decimal code 046, ".") and an US-ASCII CRLF pair. If any line decimal code 046, ".") and an US-ASCII CRLF pair. If any line
of the multi-line response begins with the termination octet, of the multi-line response begins with the termination octet,
the line MUST be "byte-stuffed" by pre-pending the termination the line MUST be "byte-stuffed" by pre-pending the termination
octet to that line of the response. Hence, a multi-line octet to that line of the response. Hence, a multi-line
response is terminated with the five octets "CRLF.CRLF" (in response is terminated with the five octets "CRLF.CRLF" (in
US-ASCII). When examining a multi-line response, the client US-ASCII). When examining a multi-line response, the client
MUST check to see if the line begins with the termination MUST check to see if the line begins with the termination
Barber [Page 3]
octet. If so and if octets other than US-ASCII CRLF follow, octet. If so and if octets other than US-ASCII CRLF follow,
the first octet of the line (the termination octet) MUST be the first octet of the line (the termination octet) MUST be
stripped away. If so and if US-ASCII CRLF immediately follows stripped away. If so and if US-ASCII CRLF immediately follows
the termination character, then the response from the NNTP the termination character, then the response from the NNTP
server is ended and the line containing ".CRLF" (in US-ASCII) server is ended and the line containing ".CRLF" (in US-ASCII)
MUST NOT considered part of the multi-line response. The MUST NOT considered part of the multi-line response. The
keywords that support multi-line responses have the format of keywords that support multi-line responses have the format of
those responses described in the responses section. those responses described in the responses section.
A NNTP server MAY have an inactivity autologout timer. Such a A NNTP server MAY have an inactivity autologout timer. Such a
skipping to change at line 218 skipping to change at page 5, line 8
The exact response codes that can be returned in response to a The exact response codes that can be returned in response to a
given command are detailed in the description of the keyword given command are detailed in the description of the keyword
that is the first part of the command. In addition, below is that is the first part of the command. In addition, below is
listed a general set of response codes that MAY be received at listed a general set of response codes that MAY be received at
any time. any time.
Certain response codes contain parameters such as numbers and Certain response codes contain parameters such as numbers and
names in addition to the status indicator. In those cases, the names in addition to the status indicator. In those cases, the
number and type of such parameters MUST be fixed for each number and type of such parameters MUST be fixed for each
Barber [Page 4]
response code to simplify interpretation of the response. In response code to simplify interpretation of the response. In
all other cases, the client MUST only use the status indicator all other cases, the client MUST only use the status indicator
itself to determine the nature of the response. itself to determine the nature of the response.
Parameters MUST be separated from the numeric status indicator Parameters MUST be separated from the numeric status indicator
and from each other by a single US-ASCII space. All numeric and from each other by a single US-ASCII space. All numeric
parameters MUST be in base 10 (decimal) format, and may have parameters MUST be in base 10 (decimal) format, and may have
leading zeros. All string parameters MUST begin after the leading zeros. All string parameters MUST begin after the
separating space, and MUST end before the following separating separating space, and MUST end before the following separating
space or the US-ASCII CRLF pair at the end of the line. space or the US-ASCII CRLF pair at the end of the line.
skipping to change at line 267 skipping to change at page 6, line 4
A server MUST respond to an unrecognized, unimplemented, or A server MUST respond to an unrecognized, unimplemented, or
syntactically invalid command with a negative response syntactically invalid command with a negative response
code(status indicators of the form 5XX). A server MUST code(status indicators of the form 5XX). A server MUST
respond to a command issued when the session is in an respond to a command issued when the session is in an
incorrect state by responding with a negative status incorrect state by responding with a negative status
indicator. This may be from either the 4XX or 5XX group as indicator. This may be from either the 4XX or 5XX group as
appropriate. appropriate.
5. The WILDMAT format 5. The WILDMAT format
The WILDMAT format[5] described here is based on the version The WILDMAT format[5] described here is based on the version
first developed by Rich Salz which was derived from the format first developed by Rich Salz which was derived from the format
used in the UNIX "find" command to articulate file names. It used in the UNIX "find" command to articulate file names. It
was developed to provide a uniform mechanism for matching was developed to provide a uniform mechanism for matching
Barber [Page 5]
patterns in the same manner that the UNIX shell matches patterns in the same manner that the UNIX shell matches
filenames. Patterns are implicitly anchored at the beginning filenames. Patterns are implicitly anchored at the beginning
and end of each string when testing for a match. There are and end of each string when testing for a match. There are
six pattern-matching operations other than a strict one-to-one six pattern-matching operations other than a strict one-to-one
match between the pattern and the source to be checked for a match between the pattern and the source to be checked for a
match. The first is an asterisk (*) to match any sequence of match. The first is an asterisk (*) to match any sequence of
zero or more UTF-8 characters. The second is a question mark zero or more UTF-8 characters. The second is a question mark
(?) to match any single UTF-8 character. The third specifies a (?) to match any single UTF-8 character. The third specifies a
specific set of characters. The set is specified as a list of specific set of characters. The set is specified as a list of
characters, or as a range of characters where the beginning characters, or as a range of characters where the beginning
skipping to change at line 323 skipping to change at page 7, line 4
begins with a and ends with d. begins with a and ends with d.
6. Format for Keyword Descriptions 6. Format for Keyword Descriptions
On the following pages are descriptions of each keyword On the following pages are descriptions of each keyword
recognized by the NNTP server and the responses that will be recognized by the NNTP server and the responses that will be
returned by those commands. These keywords are grouped by the returned by those commands. These keywords are grouped by the
functional step in which they are used. functional step in which they are used.
Each keyword is shown in upper case for clarity, although the Each keyword is shown in upper case for clarity, although the
NNTP server ignores case in the interpretation of commands. NNTP server ignores case in the interpretation of commands.
Any parameters are shown in lower case. A parameter shown in Any parameters are shown in lower case. A parameter shown in
[square brackets] is optional. For example, [GMT] indicates [square brackets] is optional. For example, [GMT] indicates
that the triglyph GMT may be present or omitted. A parameter that the triglyph GMT may be present or omitted. A parameter
that may be repeated is followed by an ellipsis. Mutually that may be repeated is followed by an ellipsis. Mutually
Barber [Page 6]
exclusive parameters are separated by a vertical bar (|) exclusive parameters are separated by a vertical bar (|)
character. For example, ggg|<message-id> indicates that a character. For example, ggg|<message-id> indicates that a
group name or a <message-id> may be specified, but not both. group name or a <message-id> may be specified, but not both.
Some parameters may be case or language specific. See RFC Some parameters may be case or language specific. See RFC
1036[6] for these details. 1036[6] for these details.
In addition, certain commands make use of a pattern for In addition, certain commands make use of a pattern for
selection of multiple news groups. The pattern in all cases is selection of multiple news groups. The pattern in all cases is
based on the WILDMAT format. Arguments expected to be in based on the WILDMAT format. Arguments expected to be in
wildmat format will be represented by the string wildmat. This wildmat format will be represented by the string wildmat. This
skipping to change at line 366 skipping to change at page 7, line 46
not authorized to post articles using the POST keyword. not authorized to post articles using the POST keyword.
The server MUST present a 502 greeting code if the client is The server MUST present a 502 greeting code if the client is
not permitted under any circumstances to interact with the not permitted under any circumstances to interact with the
server. The server should immediately close the connection server. The server should immediately close the connection
with the client after presenting this code. with the client after presenting this code.
In all other cases, the server MUST present a 400 greeting In all other cases, the server MUST present a 400 greeting
code. code.
7.1.1 MODE READER 7.1.1 Initial Connection Example
Example of a normal connection from an authorized client
[C] Initial TCP connection completed
[S] 200 NNTP Service Ready, posting permitted
Client can send commands at this point. In this example, the
client jumps directly to the conclusion step (See section
10.1).
[C] QUIT
[S] 205 NNTP Service exits normally
Example of a normal connection from an unauthorized client
[C] Initial TCP connection completed
[S] 502 NNTP Service Unavailable
At this point, the server closes the TCP connection.
Example of a normal connection from an authorized client that
is not permitted to post
[C] Initial TCP connection completed
[S] 201 NNTP Service Ready, posting prohibited
Client can send commands at this point. In this example, the
client jumps directly to the conclusion step (See section
10.1).
[C] QUIT
[S] 205 NNTP Service exits normally
Example of a connection from any client where the server is
unable to provide service
[C] Initial TCP connection completed
[S] 400 NNTP Service temporarily unavailable
At this point, the server closes the TCP connection.
7.1.2 MODE READER
MODE READER MODE READER
MODE READER MAY be used by the client to indicate to the MODE READER MAY be used by the client to indicate to the
server that it is a news reading client. This command may be server that it is a news reading client. This command may be
entered at any time. The server must present a greeting code entered at any time. The server must present a greeting code
(as described in section 7.1.1.1) appropriate to the server's (as described in section 7.1.2.1) appropriate to the server's
ability to provide service to this client in this mode. ability to provide service to this client in this mode.
7.1.1.1 Responses 7.1.2.1 Responses
200 Hello, you can post 200 Hello, you can post
201 Hello, you can't post 201 Hello, you can't post
400 Service temporarily unavailable 400 Service temporarily unavailable
Barber [Page 7]
502 Service unavailable 502 Service unavailable
7.1.2.2 MODE READER Examples
Example of use of the MODE READER command by an authorized
client
[C] MODE READER
[S] 200 NNTP Service Ready, posting permitted
Client can send commands at this point. In this example, the
client jumps directly to the conclusion step (See section
10.1).
[C] QUIT
[S] 205 NNTP Service exits normally
Example of use of MODE READER by a client not authorized to
receive service from the server as a news reader
[C] MODE READER
[S] 502 NNTP Service Unavailable
At this point, the server closes the TCP connection.
Example of a normal connection from an authorized client that
is not permitted to post
[C] MODE READER
[S] 201 NNTP Service Ready, posting prohibited
Client can send commands at this point. In this example, the
client jumps directly to the conclusion step (See section
10.1).
[C] QUIT
[S] 205 NNTP Service exits normally
Example of a connection from any client where the server is
unable to provide news reader service
[C] MODE READER
[S] 400 NNTP Service temporarily unavailable
At this point, the server closes the TCP connection.
8. The CAPABILITIES DISCOVERY Step 8. The CAPABILITIES DISCOVERY Step
A client NNTP supporting NNTP service extensions should query A client NNTP supporting NNTP service extensions should query
a server early in the session for extensions session by a server early in the session for extensions session by
issuing the LIST EXTENSIONS command. If the NNTP server issuing the LIST EXTENSIONS command. If the NNTP server
supports the NNTP service extensions it MUST give a successful supports the NNTP service extensions it MUST give a successful
response (see section 8.1.1), a failure response (see section response (see section 8.1.1), a failure response (see section
8.1.2), or an error response (see section 8.1.3). If the NNTP 8.1.2), or an error response (see section 8.1.3). If the NNTP
server does not support any NNTP service extensions, it MUST server does not support any NNTP service extensions, it MUST
generate an error response (see section 8.1.4). generate an error response (see section 8.1.4).
skipping to change at line 432 skipping to change at page 11, line 18
syntax of other reply lines is precisely defined, and if syntax of other reply lines is precisely defined, and if
present, MUST be exactly as specified. present, MUST be exactly as specified.
Each line listing an extension in the extension-listing begins Each line listing an extension in the extension-listing begins
with a single space. That space IS NOT optional, nor does it with a single space. That space IS NOT optional, nor does it
indicate general white space. This space guarantees that the indicate general white space. This space guarantees that the
line can never be misinterpreted as the end of the extension- line can never be misinterpreted as the end of the extension-
listing, but is required even where there is no possibility of listing, but is required even where there is no possibility of
ambiguity. ambiguity.
Barber [Page 8]
Each extension supported MUST be listed on a separate line to Each extension supported MUST be listed on a separate line to
facilitate the possible inclusion of parameters supported by facilitate the possible inclusion of parameters supported by
each extension command. The extension-label to be used in the each extension command. The extension-label to be used in the
response to the LIST EXTENSIONS command will be specified as response to the LIST EXTENSIONS command will be specified as
each new extension is added to the NNTP command set. Often it each new extension is added to the NNTP command set. Often it
will be the name of a new command added; however this IS NOT will be the name of a new command added; however this IS NOT
required. In fact, it IS NOT required that a new feature required. In fact, it IS NOT required that a new feature
actually add a new command or keyword. Any parameters actually adds a new command or keyword. Any parameters
included are to be specified with the definition of the included are to be specified with the definition of the
command concerned. command concerned.
That specification SHALL also specify how any parameters That specification SHALL also specify how any parameters
present are to be interpreted and how each parameter is present are to be interpreted and how each parameter is
seperated from other parameters. separated from other parameters.
The extension-label is nominally case sensitive, however the The extension-label is nominally case sensitive, however the
definitions of specific labels and parameters specify the definitions of specific labels and parameters specify the
precise interpretation, and it is to be expected that those precise interpretation, and it is to be expected that those
definitions will usually specify the label in a case definitions will usually specify the label in a case
independent manner. Where this is done, implementations are independent manner. Where this is done, implementations are
recommended to use US-ASCII upper case letters when recommended to use US-ASCII upper case letters when
transmitting the extension response. transmitting the extension response.
The LIST EXTENSIONS command itself is not included in the list The LIST EXTENSIONS command itself is not included in the list
skipping to change at line 472 skipping to change at page 12, line 4
by itself. by itself.
A typical example reply to the LIST EXTENSIONS command might A typical example reply to the LIST EXTENSIONS command might
be a multiline reply of the form: be a multiline reply of the form:
[C] LIST EXTENSIONS [C] LIST EXTENSIONS
[S] 202 Extensions supported: [S] 202 Extensions supported:
[S] OVER [S] OVER
[S] PAT [S] PAT
[S] LISTGROUP [S] LISTGROUP
[S] . [S] .
The particular extensions shown here are simply examples of The particular extensions shown here are simply examples of
what may be defined in other places, no particular meaning what may be defined in other places, no particular meaning
should be attributed to them. Recall also, that the extension should be attributed to them. Recall also, that the extension
Barber [Page 9]
names returned are not command names, as such, but simply names returned are not command names, as such, but simply
indications that the server possesses some attribute or other. indications that the server possesses some attribute or other.
The order in which the extensions are returned is of no The order in which the extensions are returned is of no
importance, NNTP server processes are not required to importance, NNTP server processes are not required to
implement any particular order, or even to consistently return implement any particular order, or even to consistently return
the same order when the command is repeated. the same order when the command is repeated.
8.1.2 Failure response 8.1.2 Failure response
skipping to change at line 532 skipping to change at page 13, line 15
In the case of any error response outlined in this section, In the case of any error response outlined in this section,
the client NNTP should issue the QUIT command (see section the client NNTP should issue the QUIT command (see section
10.1). 10.1).
8.1.4 Responses from servers without extensions 8.1.4 Responses from servers without extensions
A server NNTP that conforms to this memo but does not support A server NNTP that conforms to this memo but does not support
the extensions specified here will not recognize the LIST the extensions specified here will not recognize the LIST
EXTENSIONS command and MUST consequently return code 500 or EXTENSIONS command and MUST consequently return code 500 or
code 501. The server NNTP SHALL stay in the same state after code 501. The server NNTP SHALL stay in the same state after
Barber [Page 10]
returning this code. The client NNTP may try the extensions returning this code. The client NNTP may try the extensions
either as the need arises or configure itself for the basic either as the need arises or configure itself for the basic
NNTP functionality defined in this document. NNTP functionality defined in this document.
8.1.5 Responses from improperly implemented servers 8.1.5 Responses from improperly implemented servers
A server NNTP that improperly implements the LIST EXTENSIONS A server NNTP that improperly implements the LIST EXTENSIONS
command may return an empty list. Clients SHALL accommodate command may return an empty list. Clients SHALL accommodate
this protocol violation and interpret it as a response code this protocol violation and interpret it as a response code
402. 402.
skipping to change at line 585 skipping to change at page 14, line 16
order of arrival timestamp; that is, articles arriving later order of arrival timestamp; that is, articles arriving later
MUST have higher numbers than those that arrive earlier. The MUST have higher numbers than those that arrive earlier. The
server SHOULD allocate the next sequential unused number to server SHOULD allocate the next sequential unused number to
each new article. each new article.
Article numbers MUST lie between 1 and 4,294,967,295 Article numbers MUST lie between 1 and 4,294,967,295
inclusive. The client and server SHOULD NOT use leading zeroes inclusive. The client and server SHOULD NOT use leading zeroes
in specifying article numbers, and MUST NOT use more than 16 in specifying article numbers, and MUST NOT use more than 16
digits. In some situations, the value zero replaces an article digits. In some situations, the value zero replaces an article
number to show some special situation. One case involves number to show some special situation. One case involves
Barber [Page 11]
responses to the ARTICLE, STAT, BODY and HEAD commands where a responses to the ARTICLE, STAT, BODY and HEAD commands where a
<message-id> is specified as the argument. In those cases, the <message-id> is specified as the argument. In those cases, the
"current article pointer" is not changed. "current article pointer" is not changed.
9.1.1 Article Retrieval by News Group Name and Article Number 9.1.1 Article Retrieval by News Group Name and Article Number
The following commands are used to set the current news group The following commands are used to set the current news group
name and the "current article pointer" which is used by other name and the "current article pointer" which is used by other
commands for article retrieval. commands for article retrieval.
skipping to change at line 639 skipping to change at page 15, line 16
. All three numbers will be zero. . All three numbers will be zero.
. The high water mark is greater than or equal to the low water . The high water mark is greater than or equal to the low water
mark; the estimated article count might be zero or non-zero; mark; the estimated article count might be zero or non-zero;
if non-zero, the same requirements apply as for a non-empty if non-zero, the same requirements apply as for a non-empty
group. group.
The set of articles in a group may change after the GROUP The set of articles in a group may change after the GROUP
command is carried out. That is: command is carried out. That is:
. articles may be removed from the group . articles may be removed from the group
Barber [Page 12]
. articles may be reinstated in the group with the same article . articles may be reinstated in the group with the same article
number, but those articles MUST have numbers no less than the number, but those articles MUST have numbers no less than the
reported low water mark (note that this is a reinstatement of reported low water mark (note that this is a reinstatement of
the previous article, not a new article reusing the number) the previous article, not a new article reusing the number)
. new articles may be added with article numbers greater than . new articles may be added with article numbers greater than
the reported high water mark (if an article that was the one the reported high water mark (if an article that was the one
with the highest number has been removed, the next new article with the highest number has been removed, the next new article
will not have the number one greater than the reported high will not have the number one greater than the reported high
water mark) water mark)
skipping to change at line 680 skipping to change at page 16, line 4
invalid group is specified, the previously selected group and invalid group is specified, the previously selected group and
article MUST remain selected. If an empty news group is article MUST remain selected. If an empty news group is
selected, the "current article pointer" is in an indeterminate selected, the "current article pointer" is in an indeterminate
state and MUST NOT be used. state and MUST NOT be used.
The GROUP keyword MUST be used by a client and a successful The GROUP keyword MUST be used by a client and a successful
response received before the any other command is used that response received before the any other command is used that
depends on having the "current article pointer" be valid. depends on having the "current article pointer" be valid.
9.1.1.1.1 Responses 9.1.1.1.1 Responses
211 n f l s group selected 211 n f l s group selected
(n = estimated number of articles in group, f = first (n = estimated number of articles in group, f = first
article number in the group, l = last article number in article number in the group, l = last article number in
the group, s = name of the group.) the group, s = name of the group.)
411 no such news group 411 no such news group
9.1.1.1.2 GROUP Examples
Example for a group known to the server
[C] GROUP misc.test
[S] 211 1234 3000234 3002322 misc.test
Example for a group unknown to the server
[C] GROUP example.is.sob.bradner.or.barber
[S] 411 example.is.sob.bradner.or.barber is unknown
9.1.1.2 LAST 9.1.1.2 LAST
LAST LAST
Barber [Page 13]
The internally maintained "current article pointer" MUST be The internally maintained "current article pointer" MUST be
set to the previous article in the current news group. If set to the previous article in the current news group. If
already positioned at the first article of the news group, an already positioned at the first article of the news group, an
error message MUST be returned and the current article MUST error message MUST be returned and the current article MUST
remain selected. remain selected.
There MAY be no previous article in the group, although the There MAY be no previous article in the group, although the
current article number is not the reported low water mark. current article number is not the reported low water mark.
There MUST NOT be a previous article when the current article There MUST NOT be a previous article when the current article
number is the reported low water mark. number is the reported low water mark.
Because articles can be removed and added, the results of Because articles can be removed and added, the results of
multiple LAST and NEXT commands MAY not be consistent over the multiple LAST and NEXT commands MAY not be consistent over the
life of a particular NNTP session. life of a particular NNTP session.
The internally-maintained "current article pointer" MUST be The internally-maintained "current article pointer" MUST be
set by this command. set by this command.
A response indicating the current article number and a A response indicating the current article number and a
message-id string MUST be returned. No text is sent in message-id string MUST be returned. No article text is sent in
response to this command. response to this command.
9.1.1.2.1 Responses 9.1.1.2.1 Responses
223 n a article retrieved - request text separately (n = 223 n a article retrieved - request text separately (n =
article number, a = unique article id) article number, a = unique article id)
412 no news group selected 412 no news group selected
420 no current article has been selected 420 no current article has been selected
422 no previous article in this group 422 no previous article in this group
9.1.1.2.2 LAST Examples
Example of a successful article retrieval using LAST
[S] 200 NNTP Service Ready
[C] GROUP misc.test
[S] 211 1234 3000234 3002322 misc.test
[C] NEXT
[S] 223 3000237 <668929@domain.com> retrieved
[C] LAST
[S] 223 3000234 <45223423@to.to> retrieved
Example of an attempt to retrieve an article without having
selected a group (via the GROUP command) first
[S] 200 NNTP Service ready
[C] LAST
[S] 412 no newsgroup selected
Example of an attempt to retrieve an article using the LAST
command when the current article pointer is pointing at the
first article in the group
[S] 200 NNTP Service Ready
[C] GROUP misc.test
[S] 211 1234 3000234 3002322 misc.test
[C] LAST
[S] 422 No previous article to retrieve
Example of an attempt to retrieve an article using the LAST
command when the current group selected is empty
[S] 200 NNTP Service Ready
[C] GROUP example.empty.newsgroup
[S] 211 0 0 0 example.empty.newsgroup
[C] LAST
[S] 420 No current article selected
9.1.1.3 NEXT 9.1.1.3 NEXT
NEXT NEXT
The internally maintained "current article pointer" MUST be The internally maintained "current article pointer" MUST be
advanced to the next article in the current news group. If no advanced to the next article in the current news group. If no
more articles remain in the current group, an error message more articles remain in the current group, an error message
MUST be returned and the current article MUST remain selected. MUST be returned and the current article MUST remain selected.
The internally-maintained "current article pointer" MUST be The internally-maintained "current article pointer" MUST be
set by this command. set by this command.
A response indicating the current article number and the A response indicating the current article number and the
message-id string MUST be returned. No text is sent in message-id string MUST be returned. No text is sent in
response to this command. response to this command.
9.1.1.3.1 Responses 9.1.1.3.1 Responses
223 n a article retrieved - request text separately (n = 223 n a article retrieved - request text separately (n =
article number, a = unique article id) article number, a = unique article id)
Barber [Page 14]
412 no news group selected 412 no news group selected
420 no current article has been selected 420 no current article has been selected
421 no next article in this group 421 no next article in this group
9.1.1.3.2 NEXT Examples
Example of a successful article retrieval using NEXT
[S] 200 NNTP Service Ready
[C] GROUP misc.test
[S] 211 1234 3000234 3002322 misc.test
[C] NEXT
[S] 223 3000237 <668929@domain.com> retrieved
Example of an attempt to retrieve an article without having
selected a group (via the GROUP command) first
[S] 200 NNTP Service ready
[C] NEXT
[S] 412 no newsgroup selected
Example of an attempt to retrieve an article using the NEXT
command when the current article pointer is pointing at the
first article in the group
[S] 200 NNTP Service Ready
[C] GROUP misc.test
[S] 211 1234 3000234 3002322 misc.test
[C] ARTICLE 3002322
[S] 220 3002322 <411@whitehouse.gov> retrieved
Path: pathost!demo!whitehouse!not-for-mail
From: nobody@whitehouse.gov(Demo User)
Newsgroups: misc.test
Subject: I am just a test article
Date: 6 Oct 1998 04:38:40 -0500
Organization: The White House, Washington, DC
Message-ID: <411@whitehouse.gov>
This is just a test article.
.
[C] NEXT
[S] 422 No next article to retrieve
Example of an attempt to retrieve an article using the NEXT
command when the current group selected is empty
[S] 200 NNTP Service Ready
[C] GROUP example.empty.newsgroup
[S] 211 0 0 0 example.empty.newsgroup
[C] NEXT
[S] 420 No current article selected
9.2 Retrieval of Articles and Article Sections 9.2 Retrieval of Articles and Article Sections
There are two forms to the ARTICLE command (and the related There are two forms to the ARTICLE command (and the related
BODY, HEAD, and STAT commands), each using a different method BODY, HEAD, and STAT commands), each using a different method
of specifying which article is to be retrieved. When the of specifying which article is to be retrieved. When the
ARTICLE keyword is followed by a message-id in angle brackets ARTICLE keyword is followed by a message-id in angle brackets
("<" and ">"), the first form of the command MUST be used; ("<" and ">"), the first form of the command MUST be used;
when a numeric parameter or no parameter is supplied, the when a numeric parameter or no parameter is supplied, the
second form MUST be invoked. In the cases where the argument second form MUST be invoked. In the cases where the argument
is a message-id, the article number specified in the response is a message-id, the article number specified in the response
skipping to change at line 779 skipping to change at page 20, line 37
ARTICLE [<message-id>|nnn] ARTICLE [<message-id>|nnn]
This response displays the header, a blank line, then the body This response displays the header, a blank line, then the body
(text) of the specified article. The optional parameter nnn is (text) of the specified article. The optional parameter nnn is
the numeric id of an article in the current news group and the numeric id of an article in the current news group and
SHOULD be chosen from the range of articles provided when the SHOULD be chosen from the range of articles provided when the
news group was selected. If it is omitted, the current news group was selected. If it is omitted, the current
article is assumed. Message-id is the message id of an article article is assumed. Message-id is the message id of an article
as shown in that article's header. as shown in that article's header.
The internally-maintained "current article pointer" MUST NOT The internally maintained "current article pointer" MUST NOT
be altered when the message-id argument is used. This is both be altered when the message-id argument is used. This is both
to facilitate the presentation of articles that may be to facilitate the presentation of articles that may be
referenced within an article being read, and because of the referenced within an article being read, and because of the
semantic difficulties of determining the proper sequence and semantic difficulties of determining the proper sequence and
membership of an article which may have been posted to more membership of an article which may have been posted to more
than one news group. than one news group.
The internally-maintained "current article pointer" MUST be The internally-maintained "current article pointer" MUST be
set when a valid article number is specified as the argument. set when a valid article number is specified as the argument.
This includes the case when an article number is implied by This includes the case when an article number is implied by
the use of no argument. the use of no argument.
A previously valid article number MAY become invalid if the A previously valid article number MAY become invalid if the
article has been removed. A previously invalid article number article has been removed. A previously invalid article number
MAY become valid if the article has been reinstated, but such MAY become valid if the article has been reinstated, but such
Barber [Page 15]
an article number MUST be no less than the reported low water an article number MUST be no less than the reported low water
mark for that group. mark for that group.
If there is a valid article to present in a reply to this If there is a valid article to present in a reply to this
command, a response indicating the current article number (or command, a response indicating the current article number (or
zero when the message-id argument is used), a message-id zero when the message-id argument is used), a message-id
string, and that text is to follow MUST be returned. string, and that text is to follow MUST be returned.
The message-id string is an identification string contained The message-id string is an identification string contained
within angle brackets ("<" and ">"), which is derived from the within angle brackets ("<" and ">"), which is derived from the
skipping to change at line 827 skipping to change at page 21, line 34
9.2.1.1 Responses 9.2.1.1 Responses
220 n <a> article retrieved - head and body follow (n = 220 n <a> article retrieved - head and body follow (n =
article number, <a> = message-id) article number, <a> = message-id)
412 no news group has been selected 412 no news group has been selected
420 no current article has been selected 420 no current article has been selected
423 no such article number in this group 423 no such article number in this group
430 no such article found 430 no such article found
502 Service unavailable 502 Service unavailable
9.2.1.2 Examples
Example of a successful retrieval of an article (using no
article number)
[S] 200 NNTP Service Ready
[C] GROUP misc.test
[S] 211 1234 3000234 3002322 misc.test
[C] ARTICLE
[S] 220 3000234 <45223423@to.to>
Path: pathost!demo!somewhere!not-for-mail
From: nobody@nowhere.to (Demo User)
Newsgroups: misc.test
Subject: I am just a test article
Date: 6 Oct 1998 04:38:40 -0500
Organization: Nowhere, To
Message-ID: <45223423@to.to>
This is just a test article.
.
Example of a successful retrieval of an article by message-id
[S] 200 NNTP Service Ready
[C] ARTICLE <45223423@to.to>
[S] 220 0 <45223423@to.to>
Path: pathost!demo!somewhere!not-for-mail
From: nobody@nowhere.to (Demo User)
Newsgroups: misc.test
Subject: I am just a test article
Date: 6 Oct 1998 04:38:40 -0500
Organization: Nowhere, To
Message-ID: <45223423@to.to>
This is just a test article.
.
Example of an unsuccessful retrieval of an article by message-
id
[S] 200 NNTP Service Ready
[C] ARTICLE <i.am.not.there@nowhere.to>
[S] 430 No Such Article Found
Example of an unsuccessful retrieval of an article by number
[S] 200 NNTP Service Ready
[C] GROUP misc.test
[S] 211 1234 3000234 3002322 news.groups
[C] ARTICLE 300256
[S] 423 No such article number in this group
Example of an unsuccessful retrieval of an article by number
because no news group was selected first
[S] 200 NNTP Service Ready
[C] ARTICLE 300256
[S] 412 No news group selected
Example of an attempt to retrieve an article when the current
group selected is empty
[S] 200 NNTP Service Ready
[C] GROUP example.empty.newsgroup
[S] 211 0 0 0 example.empty.newsgroup
[C] ARTICLE
[S] 420 No current article selected
Example of a failure due to the service being unavailable
[S] 200 NNTP Service Ready
[C] ARTICLE <i.am.a.test.article@nowhere.to>
[S] 500 Service unavailable
9.2.2 HEAD 9.2.2 HEAD
HEAD [<message-id>|nnn] HEAD [<message-id>|nnn]
This response displays the header of the specified article. This response displays the header of the specified article.
The optional parameter nnn is the numeric id of an article in The optional parameter nnn is the numeric id of an article in
the current news group and SHOULD be chosen from the range of the current news group and SHOULD be chosen from the range of
articles provided when the news group was selected. If it is articles provided when the news group was selected. If it is
omitted, the current article is assumed. Message-id is the omitted, the current article is assumed. Message-id is the
message id of an article as shown in that article's header. message id of an article as shown in that article's header.
The internally-maintained "current article pointer" MUST NOT The internally maintained "current article pointer" MUST NOT
be altered when the message-id argument is used. This is both be altered when the message-id argument is used. This is both
to facilitate the presentation of articles that may be to facilitate the presentation of articles that may be
referenced within an article being read, and because of the referenced within an article being read, and because of the
semantic difficulties of determining the proper sequence and semantic difficulties of determining the proper sequence and
membership of an article which may have been posted to more membership of an article which may have been posted to more
than one news group. than one news group.
The internally-maintained "current article pointer" MUST be The internally-maintained "current article pointer" MUST be
set when a valid article number is specified as the argument. set when a valid article number is specified as the argument.
This includes the case when an article number is implied by This includes the case when an article number is implied by
the use of no argument. the use of no argument.
Barber [Page 16]
A previously valid article number MAY become invalid if the A previously valid article number MAY become invalid if the
article has been removed. A previously invalid article number article has been removed. A previously invalid article number
MAY become valid if the article has been reinstated, but such MAY become valid if the article has been reinstated, but such
an article number MUST be no less than the reported low water an article number MUST be no less than the reported low water
mark for that group. mark for that group.
If there is a valid article to present in a reply to this If there is a valid article to present in a reply to this
command, a response indicating the current article number (or command, a response indicating the current article number (or
zero when the message-id argument is used), a message-id zero when the message-id argument is used), a message-id
string, and that text is to follow MUST be returned. string, and that text is to follow MUST be returned.
skipping to change at line 883 skipping to change at page 24, line 42
than one news group. than one news group.
9.2.2.1 Responses 9.2.2.1 Responses
221 n <a> article retrieved - head follows 221 n <a> article retrieved - head follows
412 no news group has been selected 412 no news group has been selected
420 no current article has been selected 420 no current article has been selected
423 no such article number in this group 423 no such article number in this group
430 no such article found 430 no such article found
502 Service unavailable 502 Service unavailable
9.2.2.2 Examples
Example of a successful retrieval of the headers in an article
(using no article number)
[S] 200 NNTP Service Ready
[C] GROUP misc.test
[S] 211 1234 3000234 3002322 misc.test
[C] HEAD
[S] 220 3000234 <45223423@to.to>
Path: pathost!demo!somewhere!not-for-mail
From: nobody@nowhere.to (Demo User)
Newsgroups: misc.test
Subject: I am just a test article
Date: 6 Oct 1998 04:38:40 -0500
Organization: Nowhere, To
Message-ID: <45223423@to.to>
.
Example of a successful retrieval of the headers in an article
by message-id
[S] 200 NNTP Service Ready
[C] HEAD <45223423@to.to>
[S] 220 0 <45223423@to.to>
Path: pathost!demo!somewhere!not-for-mail
From: nobody@nowhere.to (Demo User)
Newsgroups: misc.test
Subject: I am just a test article
Date: 6 Oct 1998 04:38:40 -0500
Organization: Nowhere, To
Message-ID: <45223423@to.to>
.
Example of an unsuccessful retrieval of the header of an
article by message-id
[S] 200 NNTP Service Ready
[C] HEAD <i.am.not.there@nowhere.to>
[S] 430 No Such Article Found
Example of an unsuccessful retrieval of the header of an
article by number
[S] 200 NNTP Service Ready
[C] GROUP misc.test
[S] 211 1234 3000234 3002322 misc.test
[C] HEAD 300256
[S] 423 No such article number in this group
Example of an unsuccessful retrieval the header of an article
by number because no news group was selected first
[S] 200 NNTP Service Ready
[C] HEAD 300256
[S] 412 No news group selected
Example of an attempt to retrieve the header of an article
when the current group selected is empty
[S] 200 NNTP Service Ready
[C] GROUP example.empty.newsgroup
[S] 211 0 0 0 example.empty.newsgroup
[C] HEAD
[S] 420 No current article selected
Example of a failure due to the service being unavailable
[S] 200 NNTP Service Ready
[C] HEAD <i.am.a.test.article@nowhere.to>
[S] 500 Service unavailable
9.2.3 BODY 9.2.3 BODY
BODY [<message-id>|nnn] BODY [<message-id>|nnn]
This response displays the body (text) of the specified This response displays the body (text) of the specified
article. The optional parameter nnn is the numeric id of an article. The optional parameter nnn is the numeric id of an
article in the current news group and SHOULD be chosen from article in the current news group and SHOULD be chosen from
the range of articles provided when the news group was the range of articles provided when the news group was
selected. If it is omitted, the current article is assumed. selected. If it is omitted, the current article is assumed.
Message-id is the message id of an article as shown in that Message-id is the message id of an article as shown in that
article's header. article's header.
The internally-maintained "current article pointer" MUST NOT The internally maintained "current article pointer" MUST NOT
be altered when the message-id argument is used. This is both be altered when the message-id argument is used. This is both
to facilitate the presentation of articles that may be to facilitate the presentation of articles that may be
referenced within an article being read, and because of the referenced within an article being read, and because of the
semantic difficulties of determining the proper sequence and semantic difficulties of determining the proper sequence and
membership of an article which may have been posted to more membership of an article which may have been posted to more
than one news group. than one news group.
Barber [Page 17]
The internally-maintained "current article pointer" MUST be The internally-maintained "current article pointer" MUST be
set when a valid article number is specified as the argument. set when a valid article number is specified as the argument.
This includes the case when an article number is implied by This includes the case when an article number is implied by
the use of no argument. the use of no argument.
A previously valid article number MAY become invalid if the A previously valid article number MAY become invalid if the
article has been removed. A previously invalid article number article has been removed. A previously invalid article number
MAY become valid if the article has been reinstated, but such MAY become valid if the article has been reinstated, but such
an article number MUST be no less than the reported low water an article number MUST be no less than the reported low water
mark for that group. mark for that group.
skipping to change at line 940 skipping to change at page 27, line 45
than one news group. than one news group.
9.2.3.1 Responses 9.2.3.1 Responses
222 n <a> article retrieved - body follows 222 n <a> article retrieved - body follows
412 no news group has been selected 412 no news group has been selected
420 no current article has been selected 420 no current article has been selected
423 no such article number in this group 423 no such article number in this group
430 no such article found 430 no such article found
502 Service unavailable 502 Service unavailable
9.2.3.2 Examples
Example of a successful retrieval of the body of an article
(using no article number)
[S] 200 NNTP Service Ready
[C] GROUP misc.test
[S] 211 1234 3000234 3002322 misc.test
[C] BODY
[S] 222 3000234 <45223423@to.to>
This is just a test article.
.
Example of a successful retrieval of the body of an article by
message-id
[S] 200 NNTP Service Ready
[C] BODY <45223423@to.to>
[S] 222 0 <45223423@to.to>
This is just a test article.
.
Example of an unsuccessful retrieval of the body of an article
by message-id
[S] 200 NNTP Service Ready
[C] BODY <i.am.not.there@nowhere.to>
[S] 430 No Such Article Found
Example of an unsuccessful retrieval of the body of an article
by number
[S] 200 NNTP Service Ready
[C] GROUP misc.test
[S] 211 1234 3000234 3002322 misc.test
[C] BODY 300256
[S] 423 No such article number in this group
Example of an unsuccessful retrieval of the body of an article
by number because no news group was selected first
[S] 200 NNTP Service Ready
[C] BODY 300256
[S] 412 No news group selected
Example of an attempt to retrieve the body of an article when
the current group selected is empty
[S] 200 NNTP Service Ready
[C] GROUP example.empty.newsgroup
[S] 211 0 0 0 example.empty.newsgroup
[C] BODY
[S] 420 No current article selected
Example of a failure due to the service being unavailable
[S] 200 NNTP Service Ready
[C] BODY <i.am.a.test.article@nowhere.to>
[S] 500 Service unavailable
9.2.4 STAT 9.2.4 STAT
STAT [<message-id>|nnn] STAT [<message-id>|nnn]
This response returns only status information; no article This response returns only status information; no article
contents are returned. The optional parameter nnn is the contents are returned. The optional parameter nnn is the
numeric id of an article in the current news group and SHOULD numeric id of an article in the current news group and SHOULD
be chosen from the range of articles provided when the news be chosen from the range of articles provided when the news
group was selected. If it is omitted, the current article is group was selected. If it is omitted, the current article is
assumed. Message-id is the message id of an article as shown assumed. Message-id is the message id of an article as shown
in that article's header. in that article's header.
The internally-maintained "current article pointer" MUST NOT The internally maintained "current article pointer" MUST NOT
be altered when the message-id argument is used. This is both be altered when the message-id argument is used. This is both
to facilitate the presentation of articles that may be to facilitate the presentation of articles that may be
referenced within an article being read, and because of the referenced within an article being read, and because of the
semantic difficulties of determining the proper sequence and semantic difficulties of determining the proper sequence and
Barber [Page 18]
membership of an article which may have been posted to more membership of an article which may have been posted to more
than one news group. than one news group.
The internally-maintained "current article pointer" MUST be The internally-maintained "current article pointer" MUST be
set when a valid article number is specified as the argument. set when a valid article number is specified as the argument.
This includes the case when an article number is implied by This includes the case when an article number is implied by
the use of no argument. the use of no argument.
A previously valid article number MAY become invalid if the A previously valid article number MAY become invalid if the
article has been removed. A previously invalid article number article has been removed. A previously invalid article number
skipping to change at line 998 skipping to change at page 30, line 22
than one news group. than one news group.
9.2.4.1 Responses 9.2.4.1 Responses
223 n <a> article retrieved - request text separately 223 n <a> article retrieved - request text separately
412 no news group has been selected 412 no news group has been selected
420 no current article has been selected 420 no current article has been selected
423 no such article number in this group 423 no such article number in this group
430 no such article found 430 no such article found
502 Service unavailable 502 Service unavailable
9.2.4.2 Examples
Example of STAT on an existing article (using no article
number)
[S] 200 NNTP Service Ready
[C] GROUP misc.test
[S] 211 1234 3000234 3002322 misc.test
[C] STAT
[S] 223 3000234 <45223423@to.to>
Example of a STAT of an existing article by message-id
[S] 200 NNTP Service Ready
[C] STAT <45223423@to.to>
[S] 223 0 <45223423@to.to>
Example of an STAT of an article not on the server by message-
id
[S] 200 NNTP Service Ready
[C] STAT <i.am.not.there@nowhere.to>
[S] 430 No Such Article Found
Example of STAT of an article not in the server by number
[S] 200 NNTP Service Ready
[C] GROUP misc.test
[S] 211 1234 3000234 3002322 misc.test
[C] STAT 300256
[S] 423 No such article number in this group
Example of STAT of an article by number when no news group was
selected first
[S] 200 NNTP Service Ready
[C] STAT 300256
[S] 412 No news group selected
Example of STAT of an article when the current group selected
is empty
[S] 200 NNTP Service Ready
[C] GROUP example.empty.newsgroup
[S] 211 0 0 0 example.empty.newsgroup
[C] STAT
[S] 420 No current article selected
Example of a failure due to the service being unavailable
[S] 200 NNTP Service Ready
[C] STAT <i.am.a.test.article@nowhere.to>
[S] 500 Service unavailable
9.3 Article Posting 9.3 Article Posting
Article posting is done in one of two modes: individual Article posting is done in one of two modes: individual
article posting from news reading clients and article transfer article posting from news reading clients and article transfer
from other news servers. from other news servers.
9.3.1 POST 9.3.1 POST
POST POST
Barber [Page 19]
If posting is allowed, response code 340 MUST be returned to If posting is allowed, response code 340 MUST be returned to
indicate that the article to be posted should be sent. indicate that the article to be posted should be sent.
Response code 440 MUST be sent if that posting is prohibited Response code 440 MUST be sent if that posting is prohibited
for some installation-dependent reason. for some installation-dependent reason.
If posting is permitted, the article MUST be presented to the If posting is permitted, the article MUST be presented to the
server by the client in the format specified by RFC 1036. The server by the client in the format specified by RFC 1036. The
text forming the header and body of the message to be posted text forming the header and body of the message to be posted
MUST be sent by the client using the conventions for text MUST be sent by the client using the conventions for text
received from the news server: A single period (".") on a line received from the news server: A single period (".") on a line
skipping to change at line 1040 skipping to change at page 32, line 35
be posted to the server installation's news posting software, be posted to the server installation's news posting software,
which is not part of this specification. which is not part of this specification.
9.3.1.1 Responses 9.3.1.1 Responses
240 article received ok 240 article received ok
340 send article to be posted. End with <CR-LF>.<CR-LF> 340 send article to be posted. End with <CR-LF>.<CR-LF>
440 posting not allowed 440 posting not allowed
441 posting failed 441 posting failed
9.3.1.2 Examples
Example of a successful posting
[S] 200 NNTP Service Ready
[C] POST
[S] 340 Input article. End with <CR-LF>.<CR-LF>
[C] From: demo@testdomain.com(Demo User)
Newsgroups: misc.test
Subject: I am just a test article
Organization: Testdomain, USA
This is just a test article.
.
[S] 240 Article received ok
Example of an unsuccessful posting
[S] 200 NNTP Service Ready
[C] POST
[S] 340 Input article. End with <CR-LF>.<CR-LF>
[C] From: demo@testdomain.com(Demo User)
Newsgroups: misc.test
Subject: I am just a test article
Organization: Testdomain, USA
This is just a test article.
.
[S] 441 Posting failed
Example of an attempt to posting when posting is not allowed
[S] 201 NNTP Service Ready, read-only
[C] POST
[S] 440 Posting not permitted
9.3.2 IHAVE 9.3.2 IHAVE
IHAVE <message-id> IHAVE <message-id>
The IHAVE command informs the server that the client has an The IHAVE command informs the server that the client has an
article whose id is <message-id>. If the server desires a copy article whose id is <message-id>. If the server desires a copy
of that article, it MUST return a response instructing the of that article, it MUST return a response instructing the
client to send the entire article. If the server does not want client to send the entire article. If the server does not want
the article (if, for example, the server already has a copy of the article (if, for example, the server already has a copy of
it), a response indicating that the article is not wanted MUST it), a response indicating that the article is not wanted MUST
skipping to change at line 1061 skipping to change at page 34, line 10
If transmission of the article is requested, the client MUST If transmission of the article is requested, the client MUST
send the entire article, including header and body, in the send the entire article, including header and body, in the
manner specified for text transmission from the server. The manner specified for text transmission from the server. The
server MUST return a response code indicating success or server MUST return a response code indicating success or
failure of the transferal of the article. failure of the transferal of the article.
This function differs from the POST command in that it is This function differs from the POST command in that it is
intended for use in transferring already-posted articles intended for use in transferring already-posted articles
between hosts. It SHOULD NOT be used when the client is a between hosts. It SHOULD NOT be used when the client is a
Barber [Page 20]
personal news reading program. In particular, this function personal news reading program. In particular, this function
will invoke the server's news posting program with the will invoke the server's news posting program with the
appropriate settings (flags, options, etc.) to indicate that appropriate settings (flags, options, etc.) to indicate that
the forthcoming article is being forwarded from another host. the forthcoming article is being forwarded from another host.
However, the server MAY elect not to post or forward the However, the server MAY elect not to post or forward the
article if after further examination of the article it deems article if after further examination of the article it deems
it inappropriate to do so. Reasons for such subsequent it inappropriate to do so. Reasons for such subsequent
rejection of an article may include such problems as rejection of an article may include such problems as
inappropriate news groups or distributions, disk space inappropriate news groups or distributions, disk space
skipping to change at line 1093 skipping to change at page 34, line 40
436 transfer failed - try again later 436 transfer failed - try again later
437 article rejected - do not try again 437 article rejected - do not try again
Because some host news posting software may not be able to Because some host news posting software may not be able to
immediately render status on the whether an article is immediately render status on the whether an article is
inappropriate for posting or forwarding, an NNTP server MAY inappropriate for posting or forwarding, an NNTP server MAY
acknowledge the successful transfer of the article and later acknowledge the successful transfer of the article and later
silently discard it. Thus, an NNTP server MAY return the 235 silently discard it. Thus, an NNTP server MAY return the 235
acknowledgment code and later discard the received article. acknowledgment code and later discard the received article.
9.4 The LIST Keyword 9.3.2.2 Examples
Example of successfully sending an article to another site
[S] 200 NNTP Service Ready
[C] IHAVE <i.am.an.article.you.will.want@nowhere.to>
[S] 335 Send it. End with <CR-LF>.<CR-LF>
[C] Path: pathost!demo!somewhere!not-for-mail
From: nobody@nowhere.to (Demo User)
Newsgroups: misc.test
Subject: I am just a test article
Date: 6 Oct 1998 04:38:40 -0500
Organization: Nowhere, To
Message-ID: <i.am.a.test.article@nowhere.to>
This is just a test article.
.
[S] 235 Article transferred ok
Example of sending an article to another site that rejects it
[S] 200 NNTP Service Ready
[C] IHAVE <i.am.an.article.you.will.want@nowhere.to>
[S] 335 Send it. End with <CR-LF>.<CR-LF>
[C] Path: pathost!demo!somewhere!not-for-mail
From: nobody@nowhere.to (Demo User)
Newsgroups: misc.test
Subject: I am just a test article
Date: 6 Oct 1998 04:38:40 -0500
Organization: Nowhere, To
Message-ID: <i.am.a.test.article@nowhere.to>
This is just a test article.
.
[S] 437 Article rejected. Don't send again
Example of sending an article to another site where the
transfer fails
[S] 200 NNTP Service Ready
[C] IHAVE <i.am.an.article.you.will.want@nowhere.to>
[S] 335 Send it. End with <CR-LF>.<CR-LF>
[C] Path: pathost!demo!somewhere!not-for-mail
From: nobody@nowhere.to (Demo User)
Newsgroups: misc.test
Subject: I am just a test article
Date: 6 Oct 1998 04:38:40 -0500
Organization: Nowhere, To
Message-ID: <i.am.a.test.article@nowhere.to>
This is just a test article.
.
[S] 436 Transfer failed
Example of sending an article to another site that rejects it
[S] 200 NNTP Service Ready
[C] IHAVE <i.am.an.article.you.will.want@nowhere.to>
[S] 335 Send it. End with <CR-LF>.<CR-LF>
[C] Path: pathost!demo!somewhere!not-for-mail
From: nobody@nowhere.to (Demo User)
Newsgroups: misc.test
Subject: I am just a test article
Date: 6 Oct 1998 04:38:40 -0500
Organization: Nowhere, To
Message-ID: <i.am.a.test.article@nowhere.to>
This is just a test article.
.
[S] 435 Don't send it again
9.4 The LIST Keyword
9.4.1 LIST 9.4.1 LIST
LIST [ACTIVE [wildmat]] LIST [ACTIVE [wildmat]]
The response to the LIST keyword with no parameters returns a The response to the LIST keyword with no parameters returns a
list of valid news groups and associated information. Each list of valid news groups and associated information. Each
news group is sent as a line of text in the following format: news group is sent as a line of text in the following format:
group last first status group first last status
where <group> is the name of the news group, <last> is the where <group> is the name of the news group, <last> is the
number of the last known article currently in that news group, number of the last known article currently in that news group,
<first> is the number of the first article currently in the <first> is the number of the first article currently in the
news group, and <status> indicates the current status of the news group, and <status> indicates the current status of the
group on this server. Typically, the <status> will be consist group on this server. Typically, the <status> will be consist
of the US-ASCII character `y' where posting is permitted, `n' of the US-ASCII character `y' where posting is permitted, `n'
where posting is not permitted and `m' where postings will be where posting is not permitted and `m' where postings will be
forwarded to the news group moderator by the news server. forwarded to the news group moderator by the news server.
Barber [Page 21]
Other status strings may exist. The definition of these other Other status strings may exist. The definition of these other
values are covered in other specifications. values is covered in other specifications.
The <first> and <last> fields will always be numeric. They The <first> and <last> fields will always be numeric. They
may have leading zeros. If the <last> field evaluates to less may have leading zeros. If the <last> field evaluates to less
than the <first> field, there are no articles currently on than the <first> field, there are no articles currently on
file in the news group. file in the news group.
Note that posting may still be prohibited to a client although Note that posting may still be prohibited to a client although
the LIST command indicates that posting is permitted to a the LIST command indicates that posting is permitted to a
particular news group. See the POST command for an explanation particular news group. See the POST command for an explanation
of client prohibitions. The posting flag exists for each news of client prohibitions. The posting flag exists for each news
skipping to change at line 1142 skipping to change at page 37, line 49
Please note that an empty list (i.e., the text body returned Please note that an empty list (i.e., the text body returned
by this command consists only of the terminating period) is a by this command consists only of the terminating period) is a
possible valid response, and indicates that there are possible valid response, and indicates that there are
currently no valid news groups. currently no valid news groups.
If the optional matching parameter is specified, the list is If the optional matching parameter is specified, the list is
limited to only the groups that match the pattern. limited to only the groups that match the pattern.
Specifying a single group is usually very efficient for the Specifying a single group is usually very efficient for the
server, and multiple groups may be specified by using wildmat server. Multiple groups may be specified by using wildmat
patterns (described in section 5), not regular expressions. patterns (described in section 5), not regular expressions.
9.4.1.1 Responses 9.4.1.1 Responses
215 list of news groups follows 215 list of news groups follows
9.4.1.2 Examples
Example of LIST returning a list of news groups
[S] 200 NNTP Service Ready
[C] LIST
[S] 215 list of news groups follows
misc.test 3000234 3002322 y
alt.fc-writers.recovery 1 4 y
tx.natives.recovery 56 89 y
.
Example of LIST returning no news groups
[S] 200 NNTP Service Ready
[C] LIST
[S] 215 list of news groups follows
.
9.4.2 LIST ACTIVE.TIMES 9.4.2 LIST ACTIVE.TIMES
LIST ACTIVE.TIMES [wildmat] LIST ACTIVE.TIMES [wildmat]
The active.times file is maintained by some news transport The active.times file is maintained by some news transport
systems to contain information about when and who created a systems to contain information about when and who created a
particular news group. The format of this file generally particular news group. The format of this file generally
includes three fields. The first field is the name of the news includes three fields. The first field is the name of the news
group. The second is the time when this group was created on group. The second is the time when this group was created on
skipping to change at line 1168 skipping to change at page 38, line 50
January 1, 1970. The third is the email address of the entity January 1, 1970. The third is the email address of the entity
that created the news group. When executed, the information is that created the news group. When executed, the information is
displayed following the 215 response. When display is displayed following the 215 response. When display is
completed, the server will send a period on a line by itself. completed, the server will send a period on a line by itself.
If the information is not available, the server will return If the information is not available, the server will return
the 503 error response. the 503 error response.
If the optional matching parameter is specified, the list is If the optional matching parameter is specified, the list is
limited to only the groups that match the pattern. limited to only the groups that match the pattern.
Barber [Page 22]
Specifying a single group is usually very efficient for the Specifying a single group is usually very efficient for the
server, and multiple groups may be specified by using wildmat server. Multiple groups may be specified by using wildmat
patterns (described in section 5), not regular expression patterns (described in section 5), not regular expression
9.4.2.1 Responses 9.4.2.1 Responses
215 information follows 215 information follows
503 program error, function not performed 503 program error, function not performed
9.4.2.2 Examples
Example of LIST ACTIVE.TIMES returning a list of news groups
[S] 200 NNTP Service Ready
[C] LIST ACTIVE.TIMES
[S] 215 information follows
misc.test 930445408 <creatme@isc.org>
alt.rfc-writers.recovery 930562309 <m@nowhere.to>
tx.natives.recovery 930678923 <sob@academ.com>
.
Example of LIST ACTIVE.TIMES returning an error
[S] 200 NNTP Service Ready
[C] LIST ACTIVE.TIMES
[S] 503 program error, function not performed
9.4.3 LIST DISTRIBUTIONS 9.4.3 LIST DISTRIBUTIONS
LIST DISTRIBUTIONS LIST DISTRIBUTIONS
The distributions file is maintained by some news transport The distributions file is maintained by some news transport
systems to contain information about valid values for the systems to contain information about valid values for the
Distribution: line in a news article header and about what the Distribution: line in a news article header and about what the
values mean. Each line contains two fields, the value and a values mean. Each line contains two fields, the value and a
short explanation on the meaning of the value. When executed, short explanation on the meaning of the value. When executed,
the information is displayed following the 215 response. When the information is displayed following the 215 response. When
display is completed, the server will send a period on a line display is completed, the server will send a period on a line
by itself. If the information is not available, the server by itself. If the information is not available, the server
will return the 503 error response. will return the 503 error response.
9.4.3.1 Responses 9.4.3.1 Responses
215 information follows 215 information follows
503 program error, function not performed 503 program error, function not performed
9.4.3.2 Examples
Example of LIST DISTRIBUTIONS returning a list of news groups
[S] 200 NNTP Service Ready
[C] LIST DISTRIBUTIONS
[S] 215 information follows
usa United States of America
na North America
world All over the World
.
Example of LIST DISTRIBUTIONS returning an error
[S] 200 NNTP Service Ready
[C] LIST DISTRIBUTIONS
[S] 503 program error, function not performed
9.4.4 LIST DISTRIB.PATS 9.4.4 LIST DISTRIB.PATS
LIST DISTRIB.PATS LIST DISTRIB.PATS
The distrib.pats file is maintained by some news transport The distrib.pats file is maintained by some news transport
systems to contain default values for the Distribution: line systems to contain default values for the Distribution: line
in a news article header when posting to particular news in a news article header when posting to particular news
groups. This information could be used to provide a default groups. This information could be used to provide a default
value for the Distribution: line in the header when posting an value for the Distribution: line in the header when posting an
article. The information returned contains three fields article. The information returned contains three fields
skipping to change at line 1220 skipping to change at page 40, line 49
line that should be used when the group name matches and the line that should be used when the group name matches and the
weight value is the highest. All this processing is done by weight value is the highest. All this processing is done by
the news posting client and not by the server itself. The the news posting client and not by the server itself. The
server provides this information to the client for it to use server provides this information to the client for it to use
or ignore as it chooses. When executed, the information is or ignore as it chooses. When executed, the information is
displayed following the 215 response. When display is displayed following the 215 response. When display is
completed, the server will send a period on a line by itself. completed, the server will send a period on a line by itself.
If the information is not available, the server will return If the information is not available, the server will return
the 503 error response. the 503 error response.
Barber [Page 23]
9.4.4.1 Responses 9.4.4.1 Responses
215 information follows 215 information follows
503 program error, function not performed 503 program error, function not performed
9.4.4.2 Examples
Example of LIST DISTRIB.PATS returning a list of news groups
[S] 200 NNTP Service Ready
[C] LIST DISTRIB.PATS
[S] 215 information follows
10:local.*:local
.
Example of LIST DISTRIB.PATS returning an error
[S] 200 NNTP Service Ready
[C] LIST DISTRIB.PATS
[S] 503 program error, function not performed
9.4.5 LIST NEWSGROUPS 9.4.5 LIST NEWSGROUPS
LIST NEWSGROUPS [wildmat] LIST NEWSGROUPS [wildmat]
The newsgroups file is maintained by some news transport The newsgroups file is maintained by some news transport
systems to contain the name of each news group that is systems to contain the name of each news group that is
active on the server and a short description about the active on the server and a short description about the
purpose of each news group. Each line in the file contains purpose of each news group. Each line in the file contains
two fields, the news group name and a short explanation of two fields, the news group name and a short explanation of
skipping to change at line 1253 skipping to change at page 41, line 51
usually very efficient for the server, and multiple groups usually very efficient for the server, and multiple groups
may be specified by using wildmat patterns (see section 5), may be specified by using wildmat patterns (see section 5),
not regular expressions. If nothing is matched an empty list not regular expressions. If nothing is matched an empty list
is returned, not an error. is returned, not an error.
9.4.5.1 Responses 9.4.5.1 Responses
215 information follows 215 information follows
503 program error, function not performed 503 program error, function not performed
9.4.5.2 Examples
Example of LIST NEWSGROUPS returning a list of news groups
[S] 200 NNTP Service Ready
[C] LIST NEWSGROUPS
[S] 215 information follows
misc.test General Usenet testing
alt.rfc-writers.recovery RFC Writers Recovery
tx.natives.recovery Texas Natives Recovery
.
Example of LIST NEWSGROUPS returning an error
[S] 200 NNTP Service Ready
[C] LIST NEWSGROUPS
[S] 503 program error, function not performed
9.4.6 LIST OVERVIEW.FMT 9.4.6 LIST OVERVIEW.FMT
LIST OVERVIEW.FMT LIST OVERVIEW.FMT
The overview.fmt file is maintained by some news transport The overview.fmt file is maintained by some news transport
systems to contain the order in which header information is systems to contain the order in which header information is
stored in the overview databases for each news group. When stored in the overview databases for each news group. When
executed, news article header fields are displayed one line at executed, news article header fields are displayed one line at
a time in the order in which they are stored in the overview a time in the order in which they are stored in the overview
database[7] following the 215 response. When display is database[7] following the 215 response. When display is
completed, the server will send a period on a line by itself. completed, the server will send a period on a line by itself.
If the information is not available, the server will return If the information is not available, the server will return
the 503 response. the 503 response.
If the header has the word "full" (without quotes) after the If the header has the word "full" (without quotes) after the
colon, the header's name is prepended to its field in the colon, the header's name is prepended to its field in the
output returned by the server. output returned by the server.
Barber [Page 24]
This is command is part of the optional OVER extension which This is command is part of the optional OVER extension which
includes the OVER command defined in section 9.4.9. If the includes the OVER command defined in section 9.4.8. If the
OVER extension is not implemented, then this command MUST NOT OVER extension is not implemented, then this command MUST NOT
be implemented. be implemented.
9.4.6.1 Responses 9.4.6.1 Responses
215 information follows 215 information follows
503 program error, function not performed 503 program error, function not performed
9.4.7 LIST SUBSCRIPTIONS 9.4.6.2 Examples
Example of LIST OVERVIEW.FMT returning a list of news groups
[S] 200 NNTP Service Ready
LIST SUBSCRIPTIONS [C] LIST OVERVIEW.FMT
This command is used to get a default subscription list for [S] 215 Order of fields in overview database.
new users of this server. The order of groups is significant.
When this list is available, it is preceded by the 215 Subject:
response and followed by a period on a line by itself. When
this list is not available, the server returns a 503 response
code.
9.4.7.1 Responses From:
215 information follows Date:
503 program error, function not performed
9.4.8 LISTGROUP Message-ID:
.
Example of LIST OVERVIEW.FMT returning an error
[S] 200 NNTP Service Ready
[C] LIST OVERVIEW.FMT
[S] 503 program error, function not performed
9.4.7 LISTGROUP
LISTGROUP [ggg] LISTGROUP [ggg]
The LISTGROUP command is used to get a listing of all the The LISTGROUP command is used to get a listing of all the
article numbers in a particular news group. article numbers in a particular news group.
The optional parameter ggg is the name of the news group to The optional parameter ggg is the name of the news group to
be selected (e.g. "news.software.b"). A list of valid news be selected (e.g. "news.software.b"). A list of valid news
groups may be obtained from the LIST command. If no group is groups may be obtained from the LIST command. If no group is
specified, the current group is used as the default specified, the current group is used as the default
skipping to change at line 1321 skipping to change at page 43, line 50
The successful selection response will be a list of the The successful selection response will be a list of the
article numbers in the group followed by a period on a line article numbers in the group followed by a period on a line
by itself. by itself.
When a valid group is selected by means of this command, the When a valid group is selected by means of this command, the
internally maintained "current article pointer" MUST be set internally maintained "current article pointer" MUST be set
to the first article in the group. If an invalid group is to the first article in the group. If an invalid group is
specified, the previously selected group and article remain specified, the previously selected group and article remain
selected. If an empty news group is selected, the "current selected. If an empty news group is selected, the "current
Barber [Page 25]
article pointer" may be in an indeterminate state and should article pointer" may be in an indeterminate state and should
not be used. not be used.
The group name MUST match a news group obtained from the The group name MUST match a news group obtained from the
LIST command or an error will result, else the server will LIST command or an error will result, else the server will
response with the 411 error code. respond with the 411 error code.
The LISTGROUP command is an optional extension. It MAY be The LISTGROUP command is an optional extension. It MAY be
implemented. If it is not implemented, then the LISTGROUP implemented. If it is not implemented, then the LISTGROUP
label MUST NOT be included in the response to the LIST label MUST NOT be included in the response to the LIST
EXTENSIONS command. EXTENSIONS command.
9.4.8.1 Responses 9.4.7.1 Responses
211 list of article numbers follow 211 list of article numbers follow
411 No such group 411 No such group
412 Not currently in news group 412 Not currently in news group
9.4.9 OVER 9.4.7.2 Examples
Example of a successful execution with a group that exists on
the server
[S] 200 NNTP Service Ready
[C] LISTGROUP misc.test
[S] 211 list of article numbers follow
3000234
3000237
3000238
3000239
3002322
.
Example of an unsuccessful execution with a group that does
not exist on the server
[S] 200 NNTP Service Ready
[C] LISTGROUP this.group.is.not.here
[S] 411 no such group
Example of an attempt to retrieve an article when the current
group selected is empty
[S] 200 NNTP Service Ready
[C] LISTGROUP example.empty.newsgroup
[S] 412 No current article selected
9.4.8 OVER
OVER [range] OVER [range]
The OVER command returns information from the overview The OVER command returns information from the overview
database for the article(s) specified. The information database for the article(s) specified. The information
returned in the response to this command can be used by returned in the response to this command can be used by
clients to follow discussion threads. clients to follow discussion threads.
The optional range argument may be any of the following: The optional range argument may be any of the following:
skipping to change at line 1374 skipping to change at page 45, line 37
If no articles are in the range specified, the server returns If no articles are in the range specified, the server returns
a 420 error response. A 502 response will be returned if the a 420 error response. A 502 response will be returned if the
client only has permission to transfer articles. client only has permission to transfer articles.
Each line of output MUST be formatted with the article number, Each line of output MUST be formatted with the article number,
followed by each of the headers in the overview database or followed by each of the headers in the overview database or
the article itself (when the data is not available in the the article itself (when the data is not available in the
overview database) for that article separated by a US-ASCII overview database) for that article separated by a US-ASCII
tab character. The sequence of fields must be in this order: tab character. The sequence of fields must be in this order:
subject, author, date, message-id, references, byte count, and subject, author, date, message-id, references, byte count, and
Barber [Page 26]
line count. Other optional fields may follow line count. These line count. Other optional fields may follow line count. These
fields are specified by examining the response to the LIST fields are specified by examining the response to the LIST
OVERVIEW.FMT command. Where no data exists, a null field must OVERVIEW.FMT command. Where no data exists, a null field must
be provided (i.e. the output will have two tab characters be provided (i.e. the output will have two tab characters
adjacent to each other). Servers should not output fields for adjacent to each other). Servers should not output fields for
articles that have been removed since the overview database articles that have been removed since the overview database
was created. was created.
Note that all US-ASCII tab characters in any header data that Note that all US-ASCII tab characters in any header data that
is returned will be converted to a single US-ASCII space is returned will be converted to a single US-ASCII space
character. A contiguous sequence of US-ASCII non-printing character. A contiguous sequence of US-ASCII non-printing
characters will be compressed to a single US-ASCII space characters will be compressed to a single US-ASCII space
character in any output response. character in any output response.
The OVER command is part of the OVER extension, which includes The OVER command is part of the OVER extension, which includes
the LIST OVERVIEW.FMT command. The OVER extension is optional. the LIST OVERVIEW.FMT command. The OVER extension is optional.
If it is not implemented, the response to the LIST EXTENSIONS If it is not implemented, the response to the LIST EXTENSIONS
command must not include the OVER label. command must not include the OVER label.
9.4.9.1 Responses 9.4.8.1 Responses
224 Overview information follows 224 Overview information follows
412 No news group current selected 412 No news group current selected
420 No article(s) selected 420 No article(s) selected
502 no permission 502 no permission
9.4.10 PAT 9.4.8.2 Examples
Example of a successful retrieval of overview information for
an article (using no article number)
[S] 200 NNTP Service Ready
[C] GROUP misc.test
[S] 211 1234 3000234 3002322 misc.test
[C] OVER
[S] 224 Overview information follows
300234|I am just a test article|nobody@nowhere.to
(Demo User)|6 Oct 1998 04:38:40 -0500|
<45223423@to.to>
.
[Please note that the line that begins with 200234 is all one
line that has been wrapped for readability. A vertical bar has
been inserted to show where the US-ASCII TAB should actually
be.]
Example of an unsuccessful retrieval of overview information
on an article by number
[S] 200 NNTP Service Ready
[C] GROUP misc.test
[S] 211 1234 3000234 3002322 misc.test
[C] OVER 300256
[S] 420 No such article in this group
Example of an unsuccessful retrieval of overview information
by number because no news group was selected first
[S] 200 NNTP Service Ready
[C] OVER
[S] 412 No news group selected
Example of an attempt to retrieve an article when the current
group selected is empty
[S] 200 NNTP Service Ready
[C] GROUP example.empty.newsgroup
[S] 211 0 0 0 example.empty.newsgroup
[C] OVER
[S] 420 No current article selected
9.4.9 PAT
PAT header range|<message-id> [pat [pat...]] PAT header range|<message-id> [pat [pat...]]
The PAT command is used to retrieve specific headers from The PAT command is used to retrieve specific headers from
specific articles, based on pattern matching on the contents specific articles, based on pattern matching on the contents
of the header. of the header.
The required header parameter is the name of a header line The required header parameter is the name of a header line
(e.g. "subject") in a news group article. See RFC-1036 for a (e.g. "subject") in a news group article. See RFC-1036 for a
list of valid header lines. The required range argument may be list of valid header lines. The required range argument may be
skipping to change at line 1428 skipping to change at page 47, line 45
article number. article number.
The required message-id argument indicates a specific article. The required message-id argument indicates a specific article.
The range and message-id arguments are mutually exclusive. If The range and message-id arguments are mutually exclusive. If
there are additional arguments, they are joined together there are additional arguments, they are joined together
separated by a single space to form one complete pattern. If separated by a single space to form one complete pattern. If
there are no additional arguments, a wildmat "*" is the there are no additional arguments, a wildmat "*" is the
default. Successful responses start with a 221 response default. Successful responses start with a 221 response
followed by article number, an US-ASCII space, and the header followed by article number, an US-ASCII space, and the header
from that message in which the pattern matched the contents of from that message in which the pattern matched the contents of
the specified header line. A valid response includes an empty the specified header line. A valid response includes an empty
list (indicating that there were no matches). Once the output
Barber [Page 27]
list (indicating that there was no matches). Once the output
is complete, a period is sent on a line by itself. If the is complete, a period is sent on a line by itself. If the
optional argument is a message-id and no such article exists, optional argument is a message-id and no such article exists,
the 430 error response shall be returned. A 502 response shall a 430 error response shall be returned. A 502 response shall
be returned if the client only has permission to transfer be returned if the client only has permission to transfer
articles. articles.
The PAT command is optional. If it is not implemented, the The PAT command is optional. If it is not implemented, the
response to the LIST EXTENSIONS command must not include the response to the LIST EXTENSIONS command must not include the
PAT label. PAT label.
9.4.10.1 Responses 9.4.9.1 Responses
221 Header follows 221 Header follows
412 no newsgroup selected
430 no such article 430 no such article
502 no permission 502 no permission
9.4.9.2 Examples
Example of a successful retrieval of subject lines from a
range of articles
[S] 200 NNTP Service Ready
[C] GROUP misc.test
[S] 211 1234 3000234 3002322 misc.test
[C] PAT Subject 3000234-300238
[S] 221 Header Follows
3000234 I am just a test article
3000237 Re: I am just a test article
3000238 Ditto
.
Example of a successful retrieval of header from an article by
message-id
[S] 200 NNTP Service Ready
[C] pat subject <i.am.a.test.article@nowhere.to>
[S] 221 Header information follows
3000345 I am just a test article
.
Example of an unsuccessful retrieval of a header from an
article by message-id
[S] 200 NNTP Service Ready
[C] pat subject <i.am.not.there@nowhere.to>
[S] 430 No Such Article Found
Example of an unsuccessful retrieval of headers from articles
by number because no news group was selected first
[S] 200 NNTP Service Ready
[C] pat subject 300256-
[S] 412 No news group selected
Example of retrieving header information when the current
group selected is empty
[S] 200 NNTP Service Ready
[C] GROUP example.empty.newsgroup
[S] 211 0 0 0 example.empty.newsgroup
[C] path subject 0-
[S] 221 Headers follow
.
Example of a failure due to restrictions configured into the
server
[S] 200 NNTP Service Ready
[C] GROUP news.group
[S] 211 1234 3000234 3002322 misc.test
[C] PAT Subject 3000234-300238
[S] 502 access denied
10. The CONCLUSION Step 10. The CONCLUSION Step
10.1 QUIT 10.1 QUIT
QUIT QUIT
The server process MUST acknowledge the QUIT command and then The server process MUST acknowledge the QUIT command and then
closes the connection to the client. This is the preferred closes the connection to the client. This is the preferred
method for a client to indicate that it has finished all its method for a client to indicate that it has finished all its
transactions with the NNTP server. transactions with the NNTP server.
If a client simply disconnects (or the connection times out or If a client simply disconnects (or the connection times out or
some other fault occurs), the server SHALL gracefully cease some other fault occurs), the server SHALL gracefully cease
its attempts to service the client. its attempts to service the client.
10.1.1 Responses 10.1.1 Responses
205 closing connection - goodbye! 205 closing connection - goodbye!
10.1.2 Example
[S] 200 NNTP Service Ready
[C] QUIT
[S] 205 closing connection
11. Other Keywords 11. Other Keywords
There are other keywords that may be used at any time between There are other keywords that may be used at any time between
the beginning of a session and its termination. Using these the beginning of a session and its termination. Using these
keywords do not alter any state information, but the response keywords do not alter any state information, but the response
generated from the use of these keywords may provide useful generated from the use of these keywords may provide useful
information to clients that use them. information to clients that use them.
11.1 DATE 11.1 DATE
DATE DATE
This command exists to help clients find out the current time This command exists to help clients find out the current time
from the server's perspective. This command SHOULD NOT be from the server's perspective. This command SHOULD NOT be
Barber [Page 28]
used as a substitute for NTP[8], but to provide information used as a substitute for NTP[8], but to provide information
that might be useful when using the NEWNEWS command (see that might be useful when using the NEWNEWS command (see
section 11.4). section 0).
This command returns a one-line response code of 111 followed This command returns a one-line response code of 111 followed
by the UTC (or GMT) date and time on the server in the form by the UTC (or GMT) date and time on the server in the form
YYYYMMDDhhmmss. YYYYMMDDhhmmss.
11.1.1 Responses 11.1.1 Responses
111 YYYYMMDDhhmmss 111 YYYYMMDDhhmmss
11.1.2 Example
[S] 200 NNTP Service Ready
[C] DATE
[S] 19990623135624
11.2 The HELP Command 11.2 The HELP Command
HELP HELP
This command provides a short summary of commands that are This command provides a short summary of commands that are
understood by this implementation of the server. The help text understood by this implementation of the server. The help text
will be presented as a textual response terminated by a single will be presented as a textual response terminated by a single
period on a line by itself. period on a line by itself.
This text is not guaranteed to be in any particular format and This text is not guaranteed to be in any particular format and
SHALL NOT be used by clients as a replacement for the LIST SHALL NOT be used by clients as a replacement for the LIST
EXTENSIONS command described in section 8.1. EXTENSIONS command described in section 8.1.
11.2.1 Responses 11.2.1 Responses
100 help text follows 100 help text follows
11.2.2 Example
[S] 200 NNTP Service Ready
[C] HELP
[S] 100 Help text follows
This is some help text. There is no specific
formatting requirement for this test, though
it is customary for it to list the valid commands
and give a brief definition of what they do
.
11.3 NEWGROUPS 11.3 NEWGROUPS
NEWGROUPS date time [GMT|UTC] NEWGROUPS date time [GMT|UTC]
A list of newsgroups created since <date and time> MUST be A list of newsgroups created since <date and time> MUST be
listed in the same format as the LIST command. listed in the same format as the LIST command.
The date is sent as 6 or 8 digits in the format [XX]YYMMDD, The date is sent as 6 or 8 digits in the format [XX]YYMMDD,
where XX is the first two digits of the year, YY is the last where XX is the first two digits of the year, YY is the last
two digits of the year, MM is the two digits of the month two digits of the year, MM is the two digits of the month
skipping to change at line 1532 skipping to change at page 51, line 51
month (with leading zero, if appropriate). If the first two month (with leading zero, if appropriate). If the first two
digits of the year are not specified, the year is to be taken digits of the year are not specified, the year is to be taken
from the current century if YY is smaller than or equal to the from the current century if YY is smaller than or equal to the
current year, otherwise the year is from the previous century. current year, otherwise the year is from the previous century.
Time must also be specified. It must be as 6 digits HHMMSS Time must also be specified. It must be as 6 digits HHMMSS
with HH being hours in the 24-hour clock 00-23, MM minutes 00- with HH being hours in the 24-hour clock 00-23, MM minutes 00-
59, and SS seconds 00-60, which allows for leap seconds. The 59, and SS seconds 00-60, which allows for leap seconds. The
tokens "GMT" and "UTC" specifies that the date and time are tokens "GMT" and "UTC" specifies that the date and time are
given in UTC. If the tokens "GMT" and "UTC" are omitted then given in UTC. If the tokens "GMT" and "UTC" are omitted then
Barber [Page 29]
the date and time are specified in the server's local the date and time are specified in the server's local
timezone. Note that there is no way within this specification timezone. Note that there is no way within this specification
of NNTP to establish the server's local timezone. of NNTP to establish the server's local timezone.
Note that an empty list (i.e., the text body returned by this Note that an empty list (i.e., the text body returned by this
command consists only of the terminating period) is a possible command consists only of the terminating period) is a possible
valid response, and indicates that there are currently no new valid response, and indicates that there are currently no new
newsgroups. newsgroups.
Clients SHOULD make all queries using GMT/UTC time when Clients SHOULD make all queries using GMT/UTC time when
possible. possible.
11.3.1 Responses 11.3.1 Responses
231 list of new newsgroups follows 231 list of new newsgroups follows
11.3.2 Examples
Example where there are new groups
[S] 200 NNTP Service Ready
[C] NEWGROUPS 19990624 000000 UTC
[S] 230 list of new newsgroups follows
alt.rfc-writers.recovery
tx.natives.recovery
.
Example where there are no new groups
[S] 200 NNTP Service Ready
[C] NEWGROUPS 19990624 000000 UTC
[S] 230 list of new newsgroups follows
.
11.4 NEWNEWS 11.4 NEWNEWS
NEWNEWS newsgroups date time [GMT] NEWNEWS newsgroups date time [GMT]
A list of message-ids of articles posted or received to the A list of message-ids of articles posted or received to the
specified news group since "date" will be listed. The format specified news group since "date" will be listed. The format
of the listing will be one message-id per line, as though text of the listing will be one message-id per line, as though text
were being sent. A single line consisting solely of one were being sent. A single line consisting solely of one
period followed by CR-LF will terminate the list. period followed by CR-LF will terminate the list.
skipping to change at line 1576 skipping to change at page 53, line 16
command consists only of the terminating period) is a possible command consists only of the terminating period) is a possible
valid response, and indicates that there is currently no new valid response, and indicates that there is currently no new
news. news.
Clients SHOULD make all queries in GMT/UTC time when possible. Clients SHOULD make all queries in GMT/UTC time when possible.
11.4.1 Responses 11.4.1 Responses
230 list of new articles by message-id follows 230 list of new articles by message-id follows
11.4.2 Examples
Example where there are new articles
[S] 200 NNTP Service Ready
[C] NEWNEWS news.*,sci.* 19990624 000000
[S] 230 list of new articles by message-id follows
<i.am.a.new.article@nowhere.to>
<i.am.another.new.article@nowhere.to>
.
Example where there are no new articles
[S] 200 NNTP Service Ready
[C] NEWNEWS alt.* 19990624 000000
[S] 230 list of new articles by message-id follows
.
12. Framework for NNTP Extensions 12. Framework for NNTP Extensions
Although NNTP is widely and robustly deployed, some parts of Although NNTP is widely and robustly deployed, some parts of
the Internet community might wish to extend the NNTP service. the Internet community might wish to extend the NNTP service.
This memo defines a means whereby an extended NNTP client may This memo defines a means whereby an extended NNTP client may
query the server to determine the service extensions that it query the server to determine the service extensions that it
supports. supports.
Barber [Page 30]
It must be emphasized that any extension to the NNTP service It must be emphasized that any extension to the NNTP service
should not be considered lightly. NNTP's strength comes should not be considered lightly. NNTP's strength comes
primarily from its simplicity. Experience with many protocols primarily from its simplicity. Experience with many protocols
has shown that: has shown that:
Protocols with few options tend towards ubiquity, whilst Protocols with few options tend towards ubiquity, whilst
protocols with many options tend towards obscurity. protocols with many options tend towards obscurity.
This means that each and every extension, regardless of its This means that each and every extension, regardless of its
benefits, must be carefully scrutinized with respect to its benefits, must be carefully scrutinized with respect to its
skipping to change at line 1639 skipping to change at page 54, line 51
. the increment by which the extension is increasing the maximum . the increment by which the extension is increasing the maximum
length of the any commands over that specified in this length of the any commands over that specified in this
document. document.
In addition, any NNTP keyword value that starts with an upper In addition, any NNTP keyword value that starts with an upper
or lower case "X" refers to a local NNTP service extension, or lower case "X" refers to a local NNTP service extension,
which is used through bilateral, rather than standardized, which is used through bilateral, rather than standardized,
agreement. Keywords beginning with "X" MUST NOT be used in a agreement. Keywords beginning with "X" MUST NOT be used in a
registered service extension. registered service extension.
Barber [Page 31]
Any keyword values presented in the NNTP response that do not Any keyword values presented in the NNTP response that do not
begin with "X" must correspond to a standard, standards-track, begin with "X" must correspond to a standard, standards-track,
or IESG-approved experimental NNTP service extension or IESG-approved experimental NNTP service extension
registered with IANA. A conforming server MUST NOT offer non registered with IANA. A conforming server MUST NOT offer non
"X" prefixed keyword values that are not described in a "X" prefixed keyword values that are not described in a
registered extension. registered extension.
Additional verbs are bound by the same rules as NNTP keywords; Additional verbs are bound by the same rules as NNTP keywords;
specifically, verbs beginning with "X" are local extensions specifically, verbs beginning with "X" are local extensions
that MUST NOT be registered or standardized and verbs not that MUST NOT be registered or standardized and verbs not
skipping to change at line 1688 skipping to change at page 55, line 46
augument = parameter ; excluding sequence ".." augument = parameter ; excluding sequence ".."
body-command = "BODY" [1*WSP (msg-id / article-number)] *WSP body-command = "BODY" [1*WSP (msg-id / article-number)] *WSP
CRLF CRLF
command = article-command / command = article-command /
body-command / body-command /
date-command / date-command /
group-command / group-command /
head-command / head-command /
help-command / help-command /
ihave-command / ihave-command /
Barber [Page 32]
last-command / last-command /
list-active-times-command / list-active-times-command /
list-distrib-pats-command / list-distrib-pats-command /
list-distributions-command / list-distributions-command /
list-extensions-command / list-extensions-command /
list-newsgroups-command / list-newsgroups-command /
list-overview-fmt-command / list-overview-fmt-command /
list-subscriptions-command / list-subscriptions-command /
list-command / list-command /
listgroup-command / listgroup-command /
skipping to change at line 1744 skipping to change at page 56, line 51
*WSP CRLF *WSP CRLF
list-overview-fmt-command = "LIST" 1*WSP "OVERVIEW.FMT" *WSP list-overview-fmt-command = "LIST" 1*WSP "OVERVIEW.FMT" *WSP
CRLF CRLF
list-subscriptions-command = "LIST" 1*WSP "SUBSCRIPTIONS" *WSP list-subscriptions-command = "LIST" 1*WSP "SUBSCRIPTIONS" *WSP
CRLF CRLF
listgroup-command = "LISTGROUP" [1*WSP newsgroup] *WSP CRLF listgroup-command = "LISTGROUP" [1*WSP newsgroup] *WSP CRLF
mode-reader-command = "MODE" 1*WSP "READER" *WSP CRLF mode-reader-command = "MODE" 1*WSP "READER" *WSP CRLF
msg-id = <defined in RFC822> msg-id = <defined in RFC822>
newgroups-command = "NEWGROUPS" 1*WSP date 1*WSP time [1*WSP newgroups-command = "NEWGROUPS" 1*WSP date 1*WSP time [1*WSP
"GMT"/"UTC"] *WSP CRLF "GMT"/"UTC"] *WSP CRLF
Barber [Page 33]
newnews-command = "NEWNEWS" 1*WSP newsgroup *("," newsgroup) newnews-command = "NEWNEWS" 1*WSP newsgroup *("," newsgroup)
1*WSP date 1*WSP time [1*WSP "GMT"/"UTC"] 1*WSP date 1*WSP time [1*WSP "GMT"/"UTC"]
*WSP CRLF *WSP CRLF
newsgroup = parameter newsgroup = parameter
next-command = "NEXT" *WSP CRLF next-command = "NEXT" *WSP CRLF
over-command = "OVER" [1*WSP range] *WSP CRLF over-command = "OVER" [1*WSP range] *WSP CRLF
parameter = 1*(%x21-FF) ; generic command parameter parameter = 1*(%x21-FF) ; generic command parameter
pat-command = "PAT" 1*WSP header 1*WSP (range / msg-id) pat-command = "PAT" 1*WSP header 1*WSP (range / msg-id)
*(1*WSP wildmat) *WSP CRLF *(1*WSP wildmat) *WSP CRLF
post-command = "POST" *WSP CRLF post-command = "POST" *WSP CRLF
skipping to change at line 1797 skipping to change at page 57, line 48
in it which make it possible to add authentication and in it which make it possible to add authentication and
identification mechanisms, but none are included in this identification mechanisms, but none are included in this
specification. It is expected that those mechanisms will be specification. It is expected that those mechanisms will be
defined as specific extensions using the extension mechanism defined as specific extensions using the extension mechanism
specified in this document. specified in this document.
15. Notes 15. Notes
UNIX is a registered trademark of the X/Open Consortium. UNIX is a registered trademark of the X/Open Consortium.
Barber [Page 34] 16. Acknowledgments
16. References
[1] Kantor, B and P. Lapsley, "Network News Transfer Protocol",
RFC-977, U.C. San Diego and U.C. Berkeley.
[2] Yergeau, F., "UTF-8, a transformation format of ISO 10646",
RFC 2278, Alis Technologies.
[3] Coded Character Set-7-bit American Standard Code for
Information Interchange, ANSI x3.4-1986.
[4] Bradner, Scott, "Key words for use in RFCs to Indicate
Requirement Levels", RFC-2119, Harvard University.
[5] Salz, Rich, Manual Page for wildmat(3) from the INN 1.4
distribution, UUNET Technologies, Revision 1.10, April, 1992.
[6] Horton, M.R. and R. Adams, "Standard for interchange of
USENET messages", RFC-1036, AT&T Bell Laboratories and Center
for Seismic Studies, December, 1987.
[7] Robertson, Rob, "FAQ: Overview database / NOV General
Information", ftp://ftp.uu.net/networking/news/nntp/inn/faq-
nov.Z, January, 1995.
[8] Mills, David L., "Network Time Protocol (Version 3),
Specification, Implementation and Analysis", RFC-1305,
University of Delaware, March 1992.
[9] Crocker, D. and Overell, P., "Augmented BNF for Syntax
Specifications: ABNF", RFC-2234, Internet Mail Consortium and
Demon Internet, Ltd.
Barber [Page 35]
17. Acknowledgments
The author acknowledges the original authors of NNTP as The author acknowledges the original authors of NNTP as
documented in RFC 977: Brian Kantor and Phil Lapsey. documented in RFC 977: Brian Kantor and Phil Lapsey.
The author gratefully acknowledges the work of the NNTP The author gratefully acknowledges the work of the NNTP
committee chaired by Eliot Lear. The organization of this committee chaired by Eliot Lear. The organization of this
document was influenced by the last available draft from this document was influenced by the last available draft from this
working group. A special thanks to Eliot for generously working group. A special thanks to Eliot for generously
providing the original machine readable sources for that providing the original machine readable sources for that
document. document.
skipping to change at line 1871 skipping to change at page 58, line 35
authors and newsserver authors, which includes those listed authors and newsserver authors, which includes those listed
below: below:
. Rick Adams -- Original author of the NNTP extensions to the RN . Rick Adams -- Original author of the NNTP extensions to the RN
newsreader and last maintainer of Bnews newsreader and last maintainer of Bnews
. Stan Barber -- Original author of the NNTP extensions to the . Stan Barber -- Original author of the NNTP extensions to the
newsreaders that are part of Bnews. newsreaders that are part of Bnews.
. Geoff Collyer -- Original author of the OVERVIEW database . Geoff Collyer -- Original author of the OVERVIEW database
proposal and one of the original authors of CNEWS proposal and one of the original authors of CNEWS
. Dan Curry -- Original author of the xvnews newsreader . Dan Curry -- Original author of the xvnews newsreader
. Wayne Davision"Author of the first threading extensions to the . Wayne Davision -- Author of the first threading extensions to
the
RN newsreader (commonly called TRN). RN newsreader (commonly called TRN).
. Geoff Huston -- Original author of ANU NEWS . Geoff Huston -- Original author of ANU NEWS
. Phil Lapsey -- Original author of the UNIX reference . Phil Lapsey -- Original author of the UNIX reference
implementation implementation
. Ian Lea -- Maintainer of the TIN newsreader . Ian Lea -- Maintainer of the TIN newsreader
. Chris Lewis -- First known implementor of the AUTHINFO GENERIC
extension
. Rich Salz -- Original author of INN . Rich Salz -- Original author of INN
. Henry Spencer -- One of the original authors of CNEWS . Henry Spencer -- One of the original authors of CNEWS
. Kim Storm -- Original author of the NN newsreader . Kim Storm -- Original author of the NN newsreader
18. References
[1] Kantor, B and P. Lapsley, "Network News Transfer Protocol",
RFC-977, U.C. San Diego and U.C. Berkeley.
18. Author's Address [2] Yergeau, F., "UTF-8, a transformation format of ISO 10646",
RFC 2278, Alis Technologies.
[3] Coded Character Set-7-bit American Standard Code for
Information Interchange, ANSI x3.4-1986.
[4] Bradner, Scott, "Key words for use in RFCs to Indicate
Requirement Levels", RFC-2119, Harvard University.
[5] Salz, Rich, Manual Page for wildmat(3) from the INN 1.4
distribution, UUNET Technologies, Revision 1.10, April, 1992.
[6] Horton, M.R. and R. Adams, "Standard for interchange of
USENET messages", RFC-1036, AT&T Bell Laboratories and Center
for Seismic Studies, December, 1987.
[7] Robertson, Rob, "FAQ: Overview database / NOV General
Information", ftp://ftp.uu.net/networking/news/nntp/inn/faq-
nov.Z, January, 1995.
[8] Mills, David L., "Network Time Protocol (Version 3),
Specification, Implementation and Analysis", RFC-1305,
University of Delaware, March 1992.
[9] Crocker, D. and Overell, P., "Augmented BNF for Syntax
Specifications: ABNF", RFC-2234, Internet Mail Consortium and
Demon Internet, Ltd.
19. Author's Address
Stan Barber Stan Barber
P.O. Box 300481 P.O. Box 300481
Houston, Texas, 77230 Houston, Texas 77230
Email: <sob@academ.com> Email: <sob@academ.com>
This document expires June 7, 1999. This document expires Feburary 10, 2000.
Barber [Page 36]
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/