Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!rutgers!uwvax!rhesus!uwmacc!hobbes!root
From: root@hobbes.UUCP
Newsgroups: news.admin,news.software.b
Subject: Re: Using "local" as a newsgroup name considered harmful
Message-ID: <181@hobbes.UUCP>
Date: Mon, 17-Aug-87 16:49:09 EDT
Article-I.D.: hobbes.181
Posted: Mon Aug 17 16:49:09 1987
Date-Received: Wed, 19-Aug-87 07:08:38 EDT
References: <434@acornrc.UUCP> <587@its63b.ed.ac.uk> <14347@watmath.waterloo.edu>
Reply-To: root@hobbes.UUCP (John Plocher)
Followup-To: news.admin
Organization: U of Wisconsin - Madison  Spanish Department
Lines: 24
Xref: utgpu news.admin:771 news.software.b:723

+---- Jeff Voskamp writes in article <14347@watmath.waterloo.edu> ----
| One solution would be to have some option for news that will remove a
| selected list of news groups, not all unknown ones (a file like
| /usr/lib/news/localgroups or the like).  In this way you could remove
| all the groups which are local to your site and still pass along news
| that is cross-posted to several groups, only some of which you
| offically receive. You might have to define which groups get cut out on 
| a machine by machine basis, but once it was set up you could forget
| about it.
+----

Wouldn't there be enough info in the sys file + active file to determine
this?  ie:
	local = in(active) and not in("L" flagged sys file entries)

If I have a local group, (by definition) it is not sent to other machines.
If the message was for internal consumption at a company, the gateway machine
which fed the rest of the net would not have the local groups sent out.

Too farfetched?  Did I forget some simple fact?  flame me by email,
only post constructive, mature replies.

-- 
John Plocher uwvax!geowhiz!uwspan!plocher  plocher%uwspan.UUCP@uwvax.CS.WISC.EDU