Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!gem.mps.ohio-state.edu!apple!epimass!jbuck
From: jbuck@epimass.EPI.COM (Joe Buck)
Newsgroups: news.config
Subject: Re: duplicate sites?
Message-ID: <3690@epimass.EPI.COM>
Date: 30 Oct 89 23:40:56 GMT
References: <6541.625602943@paris.ics.uci.edu> <1526@crdos1.crd.ge.COM>
Reply-To: jbuck@epimass.EPI.COM (Joe Buck)
Organization: Entropic Processing, Inc., Cupertino, CA
Lines: 30

In article <6541.625602943@paris.ics.uci.edu>, nagel@PARIS.ICS.UCI.EDU (Mark Nagel) writes:
>|  Apparently there are two alice.uucp's out there.  One is the home of
>|  Dennis Ritchie at AT&T and a new one that is equivalent to
>|  alice.sp.unisys.com.  Somebody should probably do something about
>|  this.

In article <1526@crdos1.crd.ge.COM> davidsen@crdos1.UUCP (bill davidsen) writes:
>  I thought this was the type of thing the mapping project was going to
>prevent? Or is the new one mapped?

It's perfectly legitimate to have alice.sp.unisys.com.  The problem is
almost certainly that the new guys have their news installed incorrectly.
For example, rn, as shipped, wires in a

    Reply-To: user@hostname.UUCP

This code is in a shell script and is easy to fix.  FIX IT, FOLKS!  I see
a lot of articles with bogus Reply-To headers for this reason.  Another
possible fix (actually simpler) is not to generate a Reply-To at all, or
provide one with an empty body (like the Followup-To header).

The UUCP mapping project has no enforcement power, but the rabid
rerouters of the net will send all mail for the new site to Dennis
Ritchie's home base.


-- 
-- Joe Buck, just visiting/consulting at Entropic
-- write me at: jbuck@janus.berkeley.edu 
		...!{uunet,ucbvax}!janus.berkeley.edu!jbuck