Path: utzoo!utstat!helios.physics.utoronto.ca!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!rpi!crdgw1!crdos1!davidsen
From: davidsen@crdos1.crd.ge.COM (Wm E Davidsen Jr)
Newsgroups: news.software.b
Subject: Re: Modifications to B news
Keywords: news software, B news
Message-ID: <1881@crdos1.crd.ge.COM>
Date: 6 Dec 89 21:47:27 GMT
References: <315@ntpdvp1.UUCP>
Distribution: usa
Organization: GE Corp R&D Center, Schenectady NY
Lines: 21
Reply-exos:@crdgw1:To: davidsen@crdos1.crd.ge.com (bill davidsen)

In article <315@ntpdvp1.UUCP> davel@ntpdvp1.UUCP (Dave Livingston) writes:
| 	How do I protect the local groups from the expire date, but still 
| 	allow myself the ability to edit messages?

  If I understand the question, just change the call to expire in your
cron so it doesn't do the local group, the do it with its own expire.

| 	If I would want my customers to have access to a news group, would
| 	using the fascist option keep them from being able to reply via my
| 	system, or does anyone else have an idea?

  That sounds like the easiest way. I would like to restrict some users
but not others, and I don't see a great way other than designing
something from scratch. I want a per-user control of allowed groups for
posting. My first thought is a per user mandatory distribution, so I can
use "none" for no post, or "local" to allow some stuff.
-- 
bill davidsen	(davidsen@crdos1.crd.GE.COM -or- uunet!crdgw1!crdos1!davidsen)
"The world is filled with fools. They blindly follow their so-called
'reason' in the face of the church and common sense. Any fool can see
that the world is flat!" - anon