usefor-usepro-00 August 2004

[< Prev] [TOC] [ Next >]
6.  Control Messages

   The following sections document the control messages.  "Message" is
   used herein as a synonym for "article" unless context indicates
   otherwise.

   The descriptions below set out REQUIREMENTS to be followed by sites
   that receive control messages and choose to honour them. However,
   nothing in these descriptions should be taken as overriding the right
   of any such site, in accordance with its local policy, to refuse to
   honour any particular control message, or to refer it to an
   administrator for approval (either as a class or on a case-by-case
   basis).

   Relaying Agents MUST propagate all control messages regardless of
   whether or not they are recognized or processed locally.

   In the following sections, each type of control message is defined
   syntactically by defining its verb, its arguments, and possibly its
   body.
[< Prev] [TOC] [ Next >]
#Diff to first older
NewerOlder
usefor-usepro February 2005
usefor-usepro December 2004
usefor-usepro September 2004
News Article Format and Transmission May 2004
News Article Format and Transmission November 2003
News Article Format June 2003
News Article Format April 2003
News Article Format February 2003
News Article Format August 2002
News Article Format May 2002
News Article Format November 2001
News Article Format July 2001
News Article Format April 2001
News Article Format February 2000
Son of 1036 June 1994
RFC 1036 December 1987

--- ../usefor-article-13/Control_Messages.out          May 2004
+++ ../usefor-usepro-00/Control_Messages.out          August 2004
@@ -1,25 +1,16 @@
-7.  Control Messages
+6.  Control Messages
 
    The following sections document the control messages.  "Message" is
    used herein as a synonym for "article" unless context indicates
    otherwise.
 
-   The Newsgroups-header of each control message SHOULD include the
-   newsgroup-name(s) for the group(s) affected (i.e. groups to be
-   created, modified or removed, or containing articles to be canceled).
-   This is to ensure that the message propagates to all sites which
-   receive (or would receive) that group(s). It MAY include other
-   newsgroup-names so as to improve propagation (but this practice may
-   cause the control message to propagate also to places where it is
-   unwanted, or even cause it not to propagate where it should, so it
-   should not be used without good reason).
-
    The descriptions below set out REQUIREMENTS to be followed by sites
    that receive control messages and choose to honour them. However,
    nothing in these descriptions should be taken as overriding the right
-   of any such site, in accordance with its local policy, to deny any
-   particular control message, or to refer it to an administrator for
-   approval (either as a class or on a case-by-case basis).
+   of any such site, in accordance with its local policy, to refuse to
+   honour any particular control message, or to refer it to an
+   administrator for approval (either as a class or on a case-by-case
+   basis).
 
    Relaying Agents MUST propagate all control messages regardless of
    whether or not they are recognized or processed locally.


Documents were processed to this format by Forrest J. Cavalier III