RFC-1036:[Previous][Up to Table of Contents] [Next]

RFC1036 3. Control Messages

This section lists the control messages currently defined. The body of the Control header line is the control message. Messages are a sequence of zero or more words, separated by white space (blanks or tabs). The first word is the name of the control message, remaining words are parameters to the message. The remainder of the header and the body of the message are also potential parameters; for example, the From line might suggest an address to which a response is to be mailed.

Implementors and administrators may choose to allow control messages to be carried out automatically, or to queue them for annual processing. However, manually processed messages should be dealt with promptly.

Failed control messages should NOT be mailed to the originator of the message, but to the local "usenet" account.

RFC1036 3.1. Cancel
RFC1036 3.2. Ihave/Sendme
RFC1036 3.3. Newgroup
RFC1036 3.4. Rmgroup
RFC1036 3.5. Sendsys
RFC1036 3.6. Version
RFC1036 3.7. Checkgroups
RFC1036: [Source:"RFC-1036"] [Last Changed:December 1987] [Copyright: 1987 M. Horton, R. Adams]
RFC-1036:[Previous][Up to Table of Contents] [Next]

(Corrections, notes, and links for Usenet RKT.)
by Mib Software, INN customization and consulting

-B-r-o-a-d-e-n- your knowledge

Up to RFC1036

Examine in depth

Optional Header Lines: RFC1036 2.2.6. Control

RKT Rapid-Links:[Search] [RKT Tips] Path:For Developers / NNTProtocol / RFC1036 / 0061.htm