[leafnode-list] Follow-up posts are lost?

[Matthias Andree]

"Mike Vanecek" <leaf_list at mm-vanecek.cc> writes:

>         Followup-To isn't the culprit.  That works fine (for proof, see
> the headers of this post).  The problem arose because the article you
> referenced was posted with the following header:
>
> Newsgroups: alt.atheism,alt.agnosticism,talk.origins
>
>         The group talk.origins is moderated.  So the post was received
> successfully on our server--as you noted--and then our server dutifully
> emailed it to the talk.origins moderator for approval.  It's not showing
> up in the groups because it hasn't been processed by a moderator.
>
>         Articles posted to multiple groups when one of the groups is
> moderated are still subject to the moderation process before the article
> will appear in any of the named groups.  There's really no other graceful
> way to deal with that situation because of Message-ID collisions and other
> such minutiae.  The best solution is to leave moderated groups off the
> crosspost list and/or send the post separately to the moderated group.

> Does this explanation sound correct to you?

Makes perfect sense.

The next NNTP and/or Usenet (USEFOR) standard (not sure which) has a
section on handling of moderated groups, and their server is apparently
working properly, holding back the post, forwarding it to the moderator
(the upcoming standard does nothing more than casting existing common
practice into a standard text).

Unfortunately, leafnode-1 does not know which upstream groups are
moderated, so it cannot log pertinent info.

leafnode-2 was recently upgraded to not only check the status byte
(y/m/n) but also the description for the " (Moderated)" tag.

>> The angle brackets are mandatory for these commands.
>> Try: HEAD <lk6q42-vb5.ln1 at news.invalid.99computer>
>
> Roger, I will remember that if I ever need to check on things in the future. 
> Did not see that when I did a help while connected to the upstream
> server.

Currently, RFC-977 is still in effect. :)

>> If you're posting an article and editing the text takes longer than 
>> 900 s, this is "normal".
>
> If I am editing in vim called from slrn, how will leafnode even be aware of 
> the fact that I am posting or replying to a post?

Newsreaders will usually call the editor first, and only if the result
passes sanity checks, issue the POST command. (You cannot back out of a
POST command if the server accepted it, you must send data - or drop the
connection and re-connect, which is considered unfriendly.)

> Based on the reply from newscene, it would appear the puzzle is
> resolved? 

Yes, I consider it solved.

> Still, how does a poster entering a reply know that one of the groups listed 
> is a moderated list? Had I known about talk.origins, I would have definitely 
> removed it from the post.

leafnode-1 relies on the upstream servers passing the (Moderated) tag,
but it does not store the status byte unfortunately - no other way is
supported as of 1.10.6.

leafnode-2 additionally reports back the standard status byte in list or
list active replies.

-- 
Matthias Andree