Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!ames!necntc!mirror!rayssd!ukma!david From: david@ms.uky.edu (David Herron -- One of the vertebrae) Newsgroups: news.software.b Subject: Re: Visibility of dup site names Message-ID: <10162@s.ms.uky.edu> Date: 26 Aug 88 15:00:19 GMT References: <1988Aug21.045032.15240@utzoo.uucp> <817@ace.ee.lbl.gov> <1597@datapg.MN.ORG> Reply-To: david@ms.uky.edu (David Herron -- One of the vertebrae) Organization: U of Kentucky, Mathematical Sciences Lines: 34 In article <1597@datapg.MN.ORG> sewilco@datapg.MN.ORG (Scot E Wilcoxon) writes: >The discussion has wandered off to another domain vs site name battle, so >I changed the Subject line. > >My proposal was that an article from site "abc" should be forced to be sent >to site "abc" unless the article was received from site "abc". This will >stop sites with duplicate names from being invisible to each other. This won't work. The news software doesn't know what site the news arrived from. Especially here where rnews on my uucp machine is a little script along the lines of: cat >/usr/spool/inews/uunews.$$ You may be thinking of log file entries where it looks as if the software knows that the message has arrived from some particular place. All it's doing is looking at the first component of the Path: line. Assuming for the moment that all the sites with duplicate names knew of each other ... a decidedly non-trivial task since one or all of these hosts *must* be un-registered ... How are you going to handle the administrative hassle of telling the neighbors of these sites to install the header munging stuff for them? And what lever will you use on the SAs to get them to actually DO it as well. In general I can't think of a good way to accomplish what you're wanting to accomplish. That is, discovering duplicate Usenet hosts and getting them to change in some way. -- <---- David Herron -- The E-Mail guy <---- ska: David le casse\*' {rutgers,uunet}!ukma!david, david@UKMA.BITNET <---- Problem: how to get people to call ...; Solution: Completely reconfigure <---- your mail system then leave for a weeks vacation when 90% done.