usefor-article-11 June 2003

6.8.  Mail-Copies-To

   The Mail-Copies-To-header indicates whether or not the poster wishes
   to have followups to an article emailed in addition to being posted
   to Netnews and, if so, establishes the address to which they should
   be sent.



   The content syntax makes use of syntax defined in [RFC 2822].

      header      =/ Mail-Copies-To-header
      Mail-Copies-To-header
        = "Mail-Copies-To" ":" SP Mail-Copies-To-content
      Mail-Copies-To-content
        = copy-addr / [CFWS] ( "nobody" / "poster" ) [CFWS]
      copy-addr   = address-list

   The keyword "nobody" indicates that the poster does not wish copies
   of any followup postings to be emailed. This indication is widely
   seen as a very strong wish, and is to be taken as the default when
   this header is absent.

   The keyword "poster" indicates that the poster wishes a copy of any
   followup postings to be emailed to him.

   Otherwise, this header contains a copy-addr to which the poster
   wishes a copy of any followup postings to be sent.

        NOTE: Some existing practice uses the keyword "never" in place
        of "nobody" and "always" in place of "poster". These usages are
        deprecated, but followup agents MAY observe them.  The actions
        to be taken by by followup agent when following up to an article
        containing a Mail-Copies-To header are set out in section 8.6.

   Whether or not this header will also find similar usage for replies
   to messages sent to mailing lists falls outside the scope of this
   standard.

--- ../usefor-article-10/Mail-Copies-To.out          April 2003
+++ ../usefor-article-11/Mail-Copies-To.out          June 2003
@@ -5,6 +5,8 @@
    to Netnews and, if so, establishes the address to which they should
    be sent.
 
+
+
    The content syntax makes use of syntax defined in [RFC 2822].
 
       header      =/ Mail-Copies-To-header
@@ -27,37 +29,11 @@
 
         NOTE: Some existing practice uses the keyword "never" in place
         of "nobody" and "always" in place of "poster". These usages are
-        deprecated, but followup agents MAY observe them.
-
-   The automatic actions of a followup agent in the various cases
-   (subject to manual override by the user) are as follows:
-
-   nobody (or when the header is absent)
-      The followup agent SHOULD NOT, by default, email such a copy and
-      Ought, especially when there is an explicit "nobody", to issue a
-      warning and ask for confirmation if the user attempts to do so.
-
-   poster
-      The followup agent Ought, by default, to email a copy, which MUST
-      then be sent to the address(es) in the Reply-To-header, and in the
-      absence of that to the address(es) in the From-header.
-
-   copy-addr
-      The followup agent Ought, by default, to email a copy, which MUST
-      then be sent to the copy-addr.
-
-        NOTE: This header is only relevant when posting followups to
-        Netnews articles, and is to be ignored when sending pure email
-        replies to the poster, which are handled as prescribed under the
-        Reply-To-header (6.1).  Whether or not this header will also
-        find similar usage for replies to messages sent to mailing lists
-        falls outside the scope of this standard.
-
-   When emailing a copy, the followup agent SHOULD also include a
-   "Posted-And-Mailed: yes" header (6.9).
-
-        NOTE: In addition to the Posted-And-Mailed-header, some followup
-        agents also include within the body a mention that the article
-        is both posted and mailed, for the benefit of reading agents
-        that do not normally show that header.
+        deprecated, but followup agents MAY observe them.  The actions
+        to be taken by by followup agent when following up to an article
+        containing a Mail-Copies-To header are set out in section 8.6.
+
+   Whether or not this header will also find similar usage for replies
+   to messages sent to mailing lists falls outside the scope of this
+   standard.