ietf-nntp LIST ACTIVE issues

[Russ Allbery]

Charles Lindsey <chl at clw.cs.man.ac.uk> writes:
> Russ Allbery <rra at stanford.edu> writes:

>> A mode of n means that messages from peers are accepted as normal, but
>> messages posted by local readers are rejected.

> Yes, but what is the definition of "peers" and "local"?

The conventional and normal NNTP interpretations of those terms.  I don't
understand what you're asking.

> ITYM that, under 'n', articles arriving via IHAVE are accepted, but
> articles arriving via POST are not (alternatively, articles are not
> accepted under mode READER).

Yes, except that articles arriving via the nnrpd version of IHAVE are
rejected.  A better way to put this in INN terms is that articles arriving
via innd are accepted and articles arriving via nnrpd are not.

>> A mode of m means that messages from peers are accepted iff they
>> contain an Approved header, and local messages are forwarded to the
>> moderator.

> No, I don't think that is right.  Why do "peers" and "local" come into
> it?  Surely if Approved is present it is accepted regardless, whether
> from IHAVE or POST.

Right.  Sorry, that was sloppy wording on my part.

> But if Approved is absent, then articles from IHAVE are silently
> dropped, and those from POST are sent to the moderator. At least, that
> is what Usefor says.

Correct.

> But that doesn't sound right to me. If an article is crossposted to
> comp.a and comp.b, and comp.a is 'y' and comp.b is 'x', then I would
> expect it to be stored under comp.a, but not under comp.b. At least, I
> think that is what CNews does.

Huh.  You're right.  That isn't how I thought it worked, but looking at it
in more detail, you appear to be correct about what's going on.

-- 
Russ Allbery (rra at stanford.edu)             <http://www.eyrie.org/~eagle/>