usefor-article-07 May 2002
[< Prev]
[TOC] [ Next >]
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 '%' path-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, and
it SHOULD reject any article which contains any header deprecated
for Netnews (4.2.1).
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 '%' path-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 MUST NOT alter the body of the article in any
way. It MAY add other headers not already provided by the poster,
but SHOULD NOT alter, delete, or reorder any existing header, with
the specific exception of "tracing" headers such as Injector-Info
and Complaints-To, which are to be removed as already mentioned.
NOTE: The addition of non-mandatory headers by the injecting
agent may alter the posting agent's preferred presentation of
information. In particular, adding a Sender-header that exposes
a sender's mailbox has privacy implications; where the main or
only purpose for doing so is as tracing information, it is
preferable to use instead one of the options provided for the
Injector-Info header (6.19.1).
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".
[If the IDNS people come up with specific proposals before this draft is
finally submitted, we may be able to replace the following paragraph.]
In the event that the newsgroup-name contains any UTF8-xtra-
char, this will result in an addr-spec whose local-part is not
consistent the present email standards ([RFC2822]). It is
anticipated that extensions to those standards currently under
consideration will in due course provide means for encoding such
local-parts but, in the meantime, agencies responsible for
creating moderated newsgroups with such names will need to make
special arrangements.
12.Otherwise, the injecting agent forwards the article to one or more
relaying or serving agents.
[< Prev]
[TOC] [ Next >]
#Diff to first older
--- ../usefor-article-06/Procedure_to_be_followed_by_Injecting_Agents.out November 2001
+++ ../usefor-article-07/Procedure_to_be_followed_by_Injecting_Agents.out May 2002
@@ -10,12 +10,12 @@
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.
+ second '%' path-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
+ 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.
@@ -25,43 +25,51 @@
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
+ 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.
+ which contains any header that does not have legal contents, and
+ it SHOULD reject any article which contains any header deprecated
+ for Netnews (4.2.1).
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
+ 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
+ 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
+ 8. The path-identity of the injecting agent with a '%' path-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
+ 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.
+ 10.The injecting agent MUST NOT alter the body of the article in any
+ way. It MAY add other headers not already provided by the poster,
+ but SHOULD NOT alter, delete, or reorder any existing header, with
+ the specific exception of "tracing" headers such as Injector-Info
+ and Complaints-To, which are to be removed as already mentioned.
+ NOTE: The addition of non-mandatory headers by the injecting
+ agent may alter the posting agent's preferred presentation of
+ information. In particular, adding a Sender-header that exposes
+ a sender's mailbox has privacy implications; where the main or
+ only purpose for doing so is as tracing information, it is
+ preferable to use instead one of the options provided for the
+ Injector-Info header (6.19.1).
11.If the Newsgroups line contains one or more moderated groups and
- the article does NOT contain an Approved header, then the
+ 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
@@ -77,7 +85,17 @@
'.' 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.]
+[If the IDNS people come up with specific proposals before this draft is
+finally submitted, we may be able to replace the following paragraph.]
+
+ In the event that the newsgroup-name contains any UTF8-xtra-
+ char, this will result in an addr-spec whose local-part is not
+ consistent the present email standards ([RFC2822]). It is
+ anticipated that extensions to those standards currently under
+ consideration will in due course provide means for encoding such
+ local-parts but, in the meantime, agencies responsible for
+ creating moderated newsgroups with such names will need to make
+ special arrangements.
12.Otherwise, the injecting agent forwards the article to one or more
relaying or serving agents.