RFC-1036:[Previous][Up to Table of Contents] [Next]
RFC1036 2.2.6. Control

If a message contains a Control line, the message is a control message. Control messages are used for communication among USENET host machines, not to be read by users. Control messages are distributed by the same newsgroup mechanism as ordinary messages. The body of the Control header line is the message to the host.

For upward compatibility, messages that match the newsgroup pattern "all.all.ctl" should also be interpreted as control messages. If no Control header is present on such messages, the subject is used as the control message. However, messages on newsgroups matching this pattern do not conform to this standard.

Also for upward compatibility, if the first 4 characters of the Subject: line are "cmsg", the rest of the Subject: line should be interpreted as a control message.

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 2.2. Optional Headers

Examine in depth

RFC1036 3. Control Messages

RKT Rapid-Links:[Search] [RKT Tips] Path:For Developers / NNTProtocol / RFC1036 / Optional Header lines / 0053.htm