Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!wuarchive!kuhub.cc.ukans.edu!sloane
From: sloane@kuhub.cc.ukans.edu
Newsgroups: news.software.anu-news
Subject: Re: My moderated newsgroups reject new newsitems
Message-ID: <21820.25bb37b3@kuhub.cc.ukans.edu>
Date: 22 Jan 90 22:41:22 GMT
References: <9001151008.AA03870@uunet.uu.net> <653.25b2e629@mdcbbs.com> <33667.25b3b7da@kontu.utu.fi> <21560.25b48821@kuhub.cc.ukans.edu> <664.25b89cd2@mdcbbs.com>
Organization: University of Kansas Academic Computing Services
Lines: 26

In article <664.25b89cd2@mdcbbs.com>, spain@mdcbbs.com writes:
> This is good advice!  I sent mail to Gene (net.god) Spafford :-) asking for the
> "official" list.  Gene gave me the list and pointed me to NEWS.GROUPS which has
> this information posted periodically.  I gave up on NEWS.GROUPS a while back
> due to the noise but apparently some of that "noise" is *very* important!

Try reading news.admin instead.  I think the "monthly" checkgroups are
cross posted there, too.

> I made sure to SET NEWSGROUP * /NOMODER and then CAREFULLY set each moderated
> newsgroup properly.  Things are starting to settle down.  If I get a reject to
> any of my moderated newsgroup (I check the RNEWS log files regularly now), I
> will trace back the newsitem to the orginator.

Actually, news should be able to process the checkgroups message
automatically.  Just delete everything before and after the
===cut_here=== lines and do an ADD FILE command on the result. MAKE
SURE YOU KEEP THE DISTRIBUTION LOCAL, or you will probably be flamed
to death. :-)  NEWS should make a command procedure containing the
appropiate NEWS commands to update your local NEWS database to match
whatever the checkgroups says is current.  You should probably check
the command procedure by hand, but that should still be faster than
doing the moderation by hand.
-- 
USmail: Bob Sloane, University of Kansas Computer Center, Lawrence, KS, 66045
E-mail: sloane@kuhub.cc.ukans.edu, sloane@ukanvax.bitnet, AT&T: (913)864-0444