Proposal for a standardized LIST MODERATORS command
Julien ÉLIE
In case you have any comments or special need on that command, do not
hesitate to speak up.
Expectations from news readers, how it can be used, implementation
on news servers, etc.
Usage
Syntax
LIST MODERATORS
Responses
215 Moderators list follows (multi-line)
Description
See Section 7.6.1 of [RFC3977] for general requirements of the LIST
command.
The moderators list is maintained by some NNTP servers to make
clients aware of the submission address the news server will use when
an article is locally posted to a moderated newsgroup.
The information is returned as a multi-line data block following the
215 response code. Each line of this list MUST consist of two fields
separated from each other by a colon (":" or %x3A). The first field
is a wildmat (which may be a simple newsgroup name), and the second
field is the submission address for newsgroups matching that wildmat.
There are no leading or trailing whitespaces in a line. The
submission address MAY contain colons (":").
The order of lines in the list is significant: the first matching
line is used. Consequently, specific patterns should be listed
before general patterns.
When an unapproved article is locally posted to a moderated
newsgroup, it is forwarded to a moderator (see Section 3.5.1 of
[RFC5537]), using the submission address for that newsgroup. This
submission address is the second field of the first matching line in
the moderators list. It is an e-mail address with one exception: at
most one occurrence of the case-sensitive string "%s" (%x25.73) may
occur anywhere in the address. If present, the news server will
replace it, when forwarding the article to the moderator, with the
name of the matching newsgroup, with all periods ("." or %x2E) in the
name changed to dashes ("-" or %x2D). If there is a literal "%" in
the submission address, it MUST be written as "%%", even if not
followed by an "s".
NOTE: How submission addresses are created and maintained is
outside the scope of this specification.
The moderators list is not newsgroup-based, and an argument MUST NOT
be specified. Otherwise, a 501 response code MUST be returned.
The moderators list MAY be empty. If the server does not maintain
the information, a 503 response code MUST be returned, though these
two cases SHOULD NOT occur if the news server is an injecting agent
that carries moderated newsgroups.
Example
Example of output:
[C] CAPABILITIES
[S] 101 Capability list:
[S] VERSION 2
[S] READER
[S] POST
[S] LIST ACTIVE MODERATORS NEWSGROUPS
[S] .
[C] LIST MODERATORS
[S] 215 List of submission addresses follows
[S] foo.bar:anno...@example.com
[S] local.*:%s@localhost
[S] *:%s...@moderators.example.com
[S] .
The following table describes a few examples of associations between
a moderated newsgroup and its submission address on a news server
whose moderators list is the one of the previous example:
+-----------------------------+-------------------------------------+
| Name of the moderated | Submission address |
| newsgroup | |
+-----------------------------+-------------------------------------+
| foo.bar | anno...@example.com |
| local.test | local-test@localhost |
| alt.dev.null | alt-de...@moderators.example.com |
| alt.test-me | alt-t...@moderators.example.com |
+-----------------------------+-------------------------------------+
NOTE: When "%s" is used, periods are changed to dashes, and
dashes are left alone. It implies that two moderated newsgroups
whose names differ only by changing a period to a dash would go to
the same address. Therefore, if such moderated newsgroup pairs
exist with different submission addresses, a "%s" pattern rule
cannot be used for the moderation submission addresses for those
groups, and explicit entries without a pattern will be required.
Similarly, a "%s" pattern rule cannot be used for the moderation
submission address for two moderated newsgroups whose names differ
only by the case of their characters. See also Section 3.1.4 of
[RFC5536] for the syntax of a newsgroup name.
ABNF syntax
list-arguments =/ "MODERATORS"
list-content =/ list-moderators-content
list-moderators-content =
*(wildmat ":" moderators-address CRLF)
moderators-address = S-TEXT
--
Julien ï¿œLIE
ￜ Se taire, c'est pareil dans toutes les langues. ￜ (Philippe Geluck)
D. Stussy
news:he74pg$58g$1...@news.trigofacile.com...
Do we need this?
Blank or comment lines (starting with "#") appearing in a local
implementation's dataset will be filtered out upon transmission.
Or shouldn't we care how the data may be locally stored?
Julien ÉLIE
> Blank or comment lines (starting with "#") appearing in a local
> implementation's dataset will be filtered out upon transmission.
>
> Or shouldn't we care how the data may be locally stored?
It does not matter here how the server stores the data.
--
Julien �LIE
� L'ordinateur ob�it � vos ordres, pas � vos intentions. �