Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!att!cbnews!mark
From: mark@cbnews.ATT.COM (Mark Horton)
Newsgroups: comp.mail.uucp
Subject: Re: Two fulcrums (was Re: Eeek! Pathalias error!)
Keywords: incorrect-output
Message-ID: <6980@cbnews.ATT.COM>
Date: 30 May 89 17:00:00 GMT
References: <601@acheron.UUCP> <23188@dhw68k.cts.com> <2671@splut.conmicro.com>
Reply-To: mark@cbnews.ATT.COM (Mark Horton)
Organization: AT&T Bell Laboratories
Lines: 30

In article <2671@splut.conmicro.com> Jay Maynard writes:
>OK, so things are working as designed.
>So what's the fix?
>Am I going to have to get my downstream site to change his name? Or
>register a domain? Or both?
>
>I thought that domaining was supposed to fix this kind of problem...

Domaining does fix this kind of problem, if you use it.  It seems that
it's not being used in this case, so we get the usual confusion from
UUCP name conflicts.

In this case, the remedy is clear.  The UK fulcrum owns the name,
having gotten there first and been properly registered in the map.  The
US site should change their name to something that isn't already in
use.  splut should immediately delete the claimed link to the UK
fulcrum from their map entry (which is what they are currently doing,)
unless they actually set up such a link.

The UK fulcrum's SA has generously offered to forward mail for users of
the US machine that mistakenly arrive on the UK machine.  This is far
above and beyond the call of duty, since such mail will make two
transatlantic hops at BT expense.

There have been several constructive suggestions for domainish names
that the US fulcrum could use.  Other possibilities include putting a
prefix on the UUCP name to make it unique (txfulcrum, for example) or
just choosing a new UUCP name and making sure it's not already taken.

	Mark Horton