INTERNET-DRAFT                               Charles H. Lindsey
Usenet Format Working Group                  University of Manchester
                                             July 2001

8.2.2. Procedure to be followed by Injecting Agents

8.2.2.  Procedure to be followed by Injecting Agents
   A injecting agent receives proto-articles from posting and followup
   agents. It verifies them, adds headers where required and then either
   forwards them to a moderator or injects them by passing them to
   serving or relaying agents.

   If an injecting agent receives an otherwise valid article that has
   already been injected it SHOULD either act as if it is a relaying
   agent or else pass the article on to a relaying agent completely
   unaltered. Exceptionally, it MAY reinject the article, perhaps as a
   part of some complex gatewaying process (in which case it will add a
   second '%' delimiter to the Path header).  It MUST NOT forward an
   already injected article to a moderator.

   An injecting agent processes articles as follows:

   1. It MUST remove any Injector-Info or Complaints-To header already
      present (though it might be useful to copy them to suitable X-
      headers). It SHOULD likewise remove any NNTP-Posting-Host or other
      undocumented tracing header.

   2. It SHOULD verify that the article is from a trusted source.
      However, it MAY allow articles in which headers contain "forged"
      email addresses, that is, addresses which are not valid for the
      known and trusted source, especially if they end in ".invalid".

   3. It MUST reject any article whose Date header is more than 24 hours
      into the past or into the future (cf. 5.1).

   4. It MUST reject any article that does not have the correct
      mandatory headers for a proto-article (5 and 8.2.1) present, or
      which contains any header that does not have legal contents.

   5. If the article is rejected, or is otherwise incorrectly formatted
      or unacceptable due to site policy, the posting agent MUST be
      informed (such as via an NNTP 44x response code) that posting has
      failed and the article MUST NOT then be processed further.

   6. The Message-ID and Date headers (and their content) MUST be added
      when not already present.

   7. A Path header with a tail-entry (5.6.3) MUST be correctly added if
      not already present (except that it SHOULD NOT be added if the
      article is to be forwarded to a moderator).

   8. The path-identity of the injecting agent with a '%' delimiter
      (5.6.2) MUST be prepended to the Path header; moreover, that
      path-identity MUST be an FQDN mailable address (5.6.2).

   9  An Injector-Info header (6.19) SHOULD be added, identifying the
      trusted source of the article, and a suitable Complaints-To header
      (6.20) MAY be added (except that these two headers SHOULD NOT be
      added if the article is to be forwarded to a moderator).

   10.The injecting agent MAY add other headers not already provided by
      the poster, but SHOULD NOT alter, delete or reorder any headers
      already present in the article (except for headers intended for
      tracing purposes, such as Injector-Info and Complaints-To, as
      already mentioned). The injecting agent MUST NOT alter the body of
      the article in any way.

   11.If the Newsgroups line contains one or more moderated groups and
      the article does NOT contain an Approved header, then the
      injecting agent MUST forward it to the moderator of the first
      (leftmost) moderated group listed in the Newsgroups line via
      email. The complete article SHOULD be encapsulated (headers and
      all) within the email, preferably using the Content-Type
      "application/news-transmission" (6.21.6.1).

        NOTE: This standard does not prescribe how the email address of
        the moderator is to be determined, that being a matter of policy
        to be arranged by the agency responsible for the oversight of
        each hierarchy. Nevertheless, there do exist various agents
        worldwide which provide the service of forwarding to moderators,
        and the address to use with them is obtained by replacing each
        '.' in the newsgroups-name with a '-'. For example, articles
        intended for "news.announce.important" would be emailed to
        "new-announce-important@forwardingagent.example".

[There is an issue with regard to newsgroup-names using UTF-8.]

   12.Otherwise, the injecting agent forwards the article to one or more
      relaying or serving agents.

Diffs to previous draft

--- {draft-04}	Wed Jul 11 21:56:12 2001
+++ {draft-05}	Wed Jul 11 21:56:13 2001
@@ -19,8 +19,6 @@
       headers). It SHOULD likewise remove any NNTP-Posting-Host or other
       undocumented tracing header.
 
-
-
    2. It SHOULD verify that the article is from a trusted source.
       However, it MAY allow articles in which headers contain "forged"
       email addresses, that is, addresses which are not valid for the
@@ -68,6 +66,18 @@
       email. The complete article SHOULD be encapsulated (headers and
       all) within the email, preferably using the Content-Type
       "application/news-transmission" (6.21.6.1).
+
+        NOTE: This standard does not prescribe how the email address of
+        the moderator is to be determined, that being a matter of policy
+        to be arranged by the agency responsible for the oversight of
+        each hierarchy. Nevertheless, there do exist various agents
+        worldwide which provide the service of forwarding to moderators,
+        and the address to use with them is obtained by replacing each
+        '.' in the newsgroups-name with a '-'. For example, articles
+        intended for "news.announce.important" would be emailed to
+        "new-announce-important@forwardingagent.example".
+
+[There is an issue with regard to newsgroup-names using UTF-8.]
 
    12.Otherwise, the injecting agent forwards the article to one or more
       relaying or serving agents.