[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Re[2]: [leafnode-list] 1.9.19 status

On 03-May-2001 Cornelius Krasel wrote:
> Volker Apelt wrote:
>> How is leafnode supposed to know which groups are moderated 
>> and which are not?
> Leafnode could evaluate the lines returned to the LIST command. Each line
> contains a status field indicating if posting to the newsgroup is allowed
> or whether it is moderated. At the moment, Leafnode does not evaluate
> this field. Unfortunately, it is not really documented what belongs in
> this field. RFC977 gives only "y" and "n"; many moderated groups have
> "m" in there.

FWIW, Noffle stores the group status character. It also stores the current
'preferred server' of a particular group; in practice, this is either the only
server supplying the group, or the first server on the list of servers that
supplies the group. Group content is only requested from the preferred server,
but can arrive in the form of cross-posts from other servers.

Whether it might or might not be a good idea to obtain posts for a particular
group explicitly from multiple servers, I'm not sure; I think you need to
distinguish between specialised servers with only some local groups where it
would be pointless asking for netwide group content, and multiple 'full feed'
servers. Am I right in thinking that leafnode attempts to get all groups from
all servers?

Posts to local groups with status character 'm' are only allowed in containing
an Approved: header. Noffle only permits 'y', 'n' or 'm' statuses for local

Posts to external groups with status 'n' are rejected.

Posts to external groups with status 'y' are send to the preferred server for
that group.

Posts to external groups with any other status are send to the preferred server
for that group, on the basis that if the server gave the group a particular
status it should know how to handle it.

Articles cross-posted to groups with different preferred servers will be sent
to each preferred server. This will produce multiple arrivals at a moderatorial
mailbox for articles cross-posted to groups with different preferred servers
where each server does actually handle the group, but I see no alternative.

In current CVS, there is an option to post articles to the local newsbase
immediately on posting, rather than getting them back from the upstream server.
That should only post locally for local groups and external groups with status
'y', I see now. Must fix.

>> Make a new file called moderated.groups in $SPOOL/leaf.node with one line
>> for each moderated group, containing the groupname and  email address to
>> which submissions should be sent.
> This has been discussed before. The question is who is going to maintain
> this file. I have proposed a list of automated email addresses but there
> is no guarantee that this list will be up-to-date and therefore postings
> to moderated groups may simply vanish. We therefore decided to leave the
> posting to moderated groups to the upstream server; it is, however,
> necessary that a posting to a moderated group goes to one upstream server
> only to avoid hassling of the moderator. This has not yet been implemented.

I think you're quite right in not attempting to keep a moderatorial mail list.
Definitely one to lob upstream, given leafnode's target audience. But I think a
side-effect of this is that you can't absolutely definitely never duplicate
messages to the moderator where cross-posting happens.

Jim Hague - jim.hague@xxxxxxxxxxxx (Work), jim@xxxxxxxxxxxxxxxx (Play)
Never trust a computer you can't lift.

leafnode-list@xxxxxxxxxxxxxxxxxxxxxxxxxxxx -- mailing list for leafnode
To unsubscribe, send mail with "unsubscribe" in the subject to the list