Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!cs.utexas.edu!uunet!mcvax!ukc!axion!fulcrum!igb
From: igb@Fulcrum.BT.CO.UK (Ian G Batten)
Newsgroups: comp.mail.uucp
Subject: Re: Eeek! Pathalias error!
Keywords: incorrect-output
Message-ID: <176@cat.Fulcrum.BT.CO.UK>
Date: 25 May 89 08:14:38 GMT
References: <601@acheron.UUCP> <2659@splut.conmicro.com> <239@jetson.UPMA.MD.US>
Reply-To: igb@fulcrum.bt.co.uk (Ian G Batten)
Organization: BT Fulcrum, Birmingham, England
Lines: 23

In article <239@jetson.UPMA.MD.US> john@jetson.UPMA.MD.US (John Owens) writes:
>Now, since they don't seem to actually have any UUCP connections, you
>might be able to convince them to give up their UUCP name (keeping

We do have uucp connections.  It's just that they don't link directly
to the states and probably don't figure in your maps.  (We talk via one
hop to ukc, who talk to mcvax, who talk to uunet).  Giving up our uucp
domain and using just a domain name would be a little tricky as there
are still deranged people who use 'Path:' to reply to news.  This plus
active re-routers means that uucp names still matter to us.

What is the approved procedure for resolving these problems?  I suspect
that one possibility is to merge the ``other'' fulcrum's password file
into my aliases and forward mail to user@fulcrum where user is one of
the other machine's users to user@fulcrum2.  I have the resources to do
this.

ian



-- 
Ian G Batten, BT Fulcrum - igb@fulcrum.bt.co.uk - ...!uunet!ukc!fulcrum!igb