Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!nbires!isis!udenva!wedgingt
From: wedgingt@udenva.UUCP (Will Edgington)
Newsgroups: news.admin,news.software.b
Subject: Re: Using "local" as a newsgroup name considered harmful
Message-ID: <4148@udenva.UUCP>
Date: Sat, 29-Aug-87 14:48:49 EDT
Article-I.D.: udenva.4148
Posted: Sat Aug 29 14:48:49 1987
Date-Received: Sun, 30-Aug-87 10:05:49 EDT
References: <434@acornrc.UUCP> <8481@utzoo.UUCP> <2007@lsuc.UUCP>
Reply-To: wedgingt@udenva.UUCP (Will Edgington)
Organization: U of Denver
Lines: 52
Xref: mnetor news.admin:946 news.software.b:791

In article <2007@lsuc.UUCP> dave@lsuc.UUCP (David Sherman) writes:
>Yeah. What about looking at the domain of the poster in the From:
>line when you receive the article, and making a decision based
>on that as to whether to post to the local group a cross-posted article
>which includes a locallish-distribution group? [...]
>
>[...] For example, U of Toronto sites would have, in the "zap this"
>file,
>ut	.texas.edu
>meaning, "if something comes in cross-posted to ut.anything,
>and it was posted from anyone@anything.texas.edu, then don't post
>it to ut.anything because they meant a different ut." [...]

How about reversing the meaning of the domain ?  I.e., a line like :

ut	.texas.edu

means *keep* 'ut.' newsgroups if the poster's domain ends with '.texas.edu' ?

>The file would be updated by the sysadmins every time
>a new duplication problem surfaced.

My variation obviates the need for this, and, furthermore, you don't need
to know of a problem to have the file ready to squash it.  You only need
to change it when you add a new distribution.  Better yet, you can now
expand the file to handle cases like :

co	.du.edu,.ucar.edu,.isc.com,.nbi.com,.alphacdc.com

where the 'co.' distribution is the same one for all of the given (mail)
domains (yes, .du.edu and .ucar.edu *aren't* in the UUCP maps, and these
*are* most of the domains I know of in Colorado).

>The only problem I see is that if joe@texas.edu posts to
>ut.general,comp.misc, and fred@toronto.edu reads the article
>in comp.misc, the header will still mention ut.general (thus
>preserving the article in case it goes back into the Texas
>distribution, in theory), but fred will not be able to find
>it there if he goes looking. Not a serious problem, in my view.

Nor in many others, including mine, from what I've heard ...
Part of the "Frequently Asked Questions" document could even
say a bit about this kind of thing.

Is this too late for C News ?  If so, is it small enough changes
to be sent out as an "enhancement patch" later on ?
-----
Will Edgington, Computing and Information Resources, University of Denver
System Administrator for udenva (== dueos), dutyche, duorion, dunike, ...
{{hplabs,seismo}!hao,ucbvax!nbires,boulder,cires,ssds}!udenva!wedgingt,
WEDGINGT@DUCAIR (BITNET), wedgingt@ccndu (CSN/CCN), ...
COMING SOON: wedgingt@du.edu (all nets)|"No two addresses are the same  (Ail