usefor-article-09 February 2003

6.9.  Posted-And-Mailed

      header      =/ Posted-And-Mailed-header
      Posted-And-Mailed-header
        = "Posted-And-Mailed" ":" SP Posted-And-Mailed-content
             *( ";" extension-parameter )
      Posted-And-Mailed-content
        = [CFWS] ( "yes" / "no" ) [CFWS]

   This header, when used with the "yes" keyword, indicates that the
   article has been both posted to the specified newsgroups and emailed.
   It SHOULD be used when replying to the poster of an article to which
   this one is a followup (see the Mail-Copies-To-header in section 6.8)
   and it MAY be used when any article is also mailed to a recipient(s)
   identified in a To- and/or Cc-header that is also present. The "no"
   keyword is included for the sake of completeness; it MAY be used to
   indicate the opposite state, but is redundant insofar as it only
   describes the default state when this header is absent.

   This header, if present, MUST be included in both the posted and
   emailed versions of the article. The Newsgroups-header of the posted
   article SHOULD be included in the email version as recommended in
   section 5.5.  All other headers defined in this standard (excluding
   variant headers) MUST be identical in both the posted and mailed
   versions of the article, except that where they contain UTF8-xtra-
   chars, which in the mailed version MUST, to comply with section
   8.8.1.1, be encoded according to [RFC 2047] or [RFC 2231], or (in the
   case of headers containing a newsgroup-name) to section 5.5.2, they
   MAY, in the posted version, remain in UTF-8.  The bodies MUST be
   identical in both, apart from a possible change of Content-Transfer-
   Encoding.

        NOTE: This leaves open the question of whether a To- or a Cc-
        header should appear in the posted version. Naturally, a Bcc-
        header should not appear, except in a form which indicates that
        there are additional unspecified recipients.

--- ../usefor-article-08/Posted-And-Mailed.out          August 2002
+++ ../usefor-article-09/Posted-And-Mailed.out          February 2003
@@ -3,7 +3,7 @@
       header      =/ Posted-And-Mailed-header
       Posted-And-Mailed-header
         = "Posted-And-Mailed" ":" SP Posted-And-Mailed-content
-             *( ";" other-parameter )
+             *( ";" extension-parameter )
       Posted-And-Mailed-content
         = [CFWS] ( "yes" / "no" ) [CFWS]
 
@@ -22,12 +22,14 @@
    article SHOULD be included in the email version as recommended in
    section 5.5.  All other headers defined in this standard (excluding
    variant headers) MUST be identical in both the posted and mailed
-   versions of the article, except that headers containing UTF8-xtra-
-   chars in the posted version MAY be encoded according to [RFC 2047] or
-   [RFC 2231], or (in the case of a Newsgroups-header) to section 5.5.2,
-   in the emailed version. In particular, the Message-ID-headers MUST be
-   identical.  The bodies MUST be identical in both, apart from a
-   possible change of Content-Transfer-Encoding.
+   versions of the article, except that where they contain UTF8-xtra-
+   chars, which in the mailed version MUST, to comply with section
+   8.8.1.1, be encoded according to [RFC 2047] or [RFC 2231], or (in the
+   case of headers containing a newsgroup-name) to section 5.5.2, they
+   MAY, in the posted version, remain in UTF-8.  The bodies MUST be
+   identical in both, apart from a possible change of Content-Transfer-
+   Encoding.
+
         NOTE: This leaves open the question of whether a To- or a Cc-
         header should appear in the posted version. Naturally, a Bcc-
         header should not appear, except in a form which indicates that