Xref: utzoo news.admin:10971 news.software.b:6098
Path: utzoo!utstat!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!aplcen!haven!ni.umd.edu!sayshell.umd.edu!louie
From: louie@sayshell.umd.edu (Louis A. Mamakos)
Newsgroups: news.admin,news.software.b
Subject: Re: C News drops unapproved postings(was: comp.newprod - moderated/unmoderated??)
Message-ID: <1990Oct31.221626.529@ni.umd.edu>
Date: 31 Oct 90 22:16:26 GMT
References: <454@tygra.ddmi.com> <A1439044953@thelake.mn.org> <89668@aerospace.AERO.ORG> <1990Oct26.165109.29072@zoo.toronto.edu> <1990Oct28.002345.11093@vicom.com> <1990Oct31.205604.23731@grian.cps.altadena.ca.us>
Sender: usenet@ni.umd.edu (USENET News System)
Organization: The University of Maryland, College Park
Lines: 14
Nntp-Posting-Host: sayshell.umd.edu

I must applaud C news for doing what I think is the correct thing with
unapproved new articles in moderated newsgroups.  If you're ever in
the position of maintaining a mailing list which is gatewayed to a
USENET newsgroup, this is the friendly thing to do.

When the comp.protocols.time.ntp newsgroup was created, it was
un-moderated.  Unfortunately, an incorrect checkgroups message
followed a few days later with the group marked as moderated, and with
the mailing list address listed as the moderator's address.  Chaos
ensued, with articles looping and appearing on the mailing list over
and over again.  If B news had the same behavior, then the brokeness
caused by the incorrect checkgroups would not have been so.. painful.

louie