usefor-usepro-01 September 2004

7.6.  Duties of a Followup Agent

   A Followup Agent is a special case of a posting agent, and as such is
   bound by all the posting agent's requirements. Followup agents MUST
   create valid followups and are subject to special requirements
   involving certain inheritable (a-4.2.5.2) and other headers.
   Wherever in the following it is stated that, "by default", a header
   is to be taken from some header in the precursor, it means that its
   initial content (plus its extension-parameters, if any) are to be
   copied from those of that precursor header.  However, posters MAY
   then override that default before posting if they so wish.

        NOTE: There is no provision in this standard for a followup to
        have more than one precursor (though it might be permitted in
        some future extension).

   1. The Newsgroups-header (a-5.5) SHOULD by default be taken from the
      precursor's Followup-To-header if present, and otherwise from the
      precursor's Newsgroups-header. However, if the content of that
      Followup-To-header consists of "poster" (and the user does not
      override it), then the followup MUST NOT be posted but, rather, is
      to be emailed to the precursor's poster.

   2. The Subject-header SHOULD by default be taken from that of the
      precursor. The case sensitive string "Re: " MAY be prepended to
      its Subject-Content unless it already begins with that string.

   3. The Distribution-header (a-6.6) SHOULD by default be taken from
      the precursor's Distribution-header, if any.

   4. If the precursor did not have a References-header (a-6.10), the
      followup's References-content MUST be formed by the message
      identifier of the precursor. A followup to an article which had a
      References-header MUST have a References-header containing the
      precursor's References-content (subject to trimming as described
      below) plus the precursor's message identifier appended to the end
      of the list (separated from it by CFWS).

      Followup agents MAY trim References-headers which have grown to
      excessive length, but the first and last message identifiers from
      the precursor MUST NOT be removed.

   5. If the precursor contains a Mail-Copies-To-header (a-6.8), the
      actions to be taken, in accordance with the Mail-Copies-To-
      content, (and subject to manual override by the poster) are as
      follows:

      "nobody" (or when the header is absent)
  The followup agent SHOULD NOT email a copy of a posted
  followup to the poster of the precursor.

      "poster"
  The followup agent SHOULD (if it has the necessary
  capability) email a copy of a posted followup, 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.

      a copy-addr
  The followup agent SHOULD likewise email a copy of a posted
  followup, which MUST then be sent to the copy-addr.

      When emailing a copy, the followup agent SHOULD also include a
      "Posted-And-Mailed: yes" header (a-6.9).

      Followup agents SHOULD NOT attempt to send email to any address
      ending in ".invalid".

--- ../usefor-usepro-00/Duties_of_a_Followup_Agent.out          August 2004
+++ ../usefor-usepro-01/Duties_of_a_Followup_Agent.out          September 2004
@@ -1,4 +1,4 @@
-7.7.  Duties of a Followup Agent
+7.6.  Duties of a Followup Agent
 
    A Followup Agent is a special case of a posting agent, and as such is
    bound by all the posting agent's requirements. Followup agents MUST