Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84 SMI; site sun.uucp
Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!mhuxt!houxm!whuxl!whuxlm!akgua!gatech!seismo!harvard!talcott!panda!genrad!decvax!decwrl!sun!chuq
From: chuq@sun.uucp (Chuq Von Rospach)
Newsgroups: net.mail
Subject: Re: Mail problem, ihnp4 -> tektronix
Message-ID: <3080@sun.uucp>
Date: Tue, 17-Dec-85 00:14:00 EST
Article-I.D.: sun.3080
Posted: Tue Dec 17 00:14:00 1985
Date-Received: Fri, 20-Dec-85 06:17:22 EST
References: <17623@styx.UUCP>
Distribution: net
Organization: Sun Micro -- NFS Consulting Group
Lines: 27

> The appended message was sent to me by philabs, indicating a
> problem sending a message to tektronix. I can't tell from the header 
> why it was routed to philabs from ihnp4, since it doesn't appear in the path. 
> The path was the one produced by pathalias for our site.
> 
> I deal mostly with ARPA stuff and don't really understand how the UUCP
> mailer at ihnp4 does things, but I don't know how a message addressed
> to idi!nsc!ihnp4!tektronix!orca!raynor ended up going from ihnp4 to
> philabs, who dropped it on the floor. Can anyone shed light on this?

ihnp4 uses pathalias (or a variant of it) to do routing. Unfortunately, they
seem to be getting more and more confused over time, with innnacurate or
inefficient routes being generated. Every so often, ihnp4 used to believe that
the fastest route to nsc was ihnp4!cbosgd!nsc even though nsc talked directly
to them. Now, from my mail, it seems to think that ihnp4!cbosgd!sun is the
fastest route to sun, even though sun talks to ihnp4... sigh.

It looks like somehow ihnp4 has decided the fastest route to tek is through
philabs. Perhaps philabs used to talk to tek and the map ihnp4 is using is
bogus...

chuq
-- 
:From catacombs of Castle Tarot:        Chuq Von Rospach 
sun!chuq@decwrl.DEC.COM                 {hplabs,ihnp4,nsc,pyramid}!sun!chuq

Power ennobles. Absolute power ennobles absolutely.