dennett@kodak.UUCP (Charlie Dennett) (06/17/88)
Below is a bounced mail message that tried to go through a machine (cygnus)
that I administer here at Eastman Kodak. I'm not 100% sure how to read all
the path and addressing information, but it seems to me that some machine
along the way thinks there is another machine called cygnus. Is there a way
to tell which machine has the wrong information? Since the map for my cygnus
has shown up in the map file u.usa.ny.1, I assume that at the time I sent my
map to the people at rutgers there was no other cygnus. Perhaps someone
could shed some light on this for me. I did check the map files for Colorado
and found no mention of a machine called cygnus.
Thanks for any help. Of course, if this is the wrong newsgroup for something
like this, I would appreciate it if someone would tell me which is the
correct group.
------------------------------------------------------------------------------
From MAILER-DAEMON Thu Jun 16 11:32:04 1988
Return-Path: <MAILER-DAEMON>
Received: by cygnus.EP02.KODAK.uucp (3.2/SMI-3.2)
id AA12038; Thu, 16 Jun 88 11:32:00 EDT
Date: Thu, 16 Jun 88 11:32:00 EDT
From: MAILER-DAEMON (Mail Delivery Subsystem)
Subject: Returned mail: Host unknown
Message-Id: <8806161532.AA12038@cygnus.EP02.KODAK.uucp>
To: Postmaster
Status: R
----- Transcript of session follows -----
bad system name: boulder
uux failed. code 68
550 boulder!colo!mcdonald... Host unknown
----- Message header follows -----
Return-Path: <kodak!rochester!ames!cgdra.UCAR.EDU!dave>
Received: by cygnus.EP02.KODAK.uucp (3.2/SMI-3.2)
id AA12036; Thu, 16 Jun 88 11:32:00 EDT
Received: by kodak.com (3.2/SMI-3.2)
id AA09103; Wed, 15 Jun 88 18:47:12 EDT
Received: from ames.arc.nasa.gov by sol.cs.rochester.edu (3.2/h) id AA14293; Wed, 15 Jun 88 18:36:00 EDT
Received: Wed, 15 Jun 88 15:31:25 PDT from HANDIES.UCAR.EDU by ames.arc.nasa.gov (5.59/1.2)
Received: by ncar.UCAR.EDU (5.58/1.00.UUCP-MOD.8-11-85)
id AA08753; Wed, 15 Jun 88 16:33:56 MDT
Received: by ncar.UCAR.EDU (5.58/1.00.UUCP-MOD.8-11-85)
id AA08731; Wed, 15 Jun 88 16:33:50 MDT
Received: from CGDRA.UCAR.EDU by ncar.UCAR.EDU (5.58/1.00.UUCP-MOD.8-11-85)
id AA08713; Wed, 15 Jun 88 16:33:44 MDT
Date: Wed, 15 Jun 88 16:31:52 MDT
From: kodak!rochester!ames!cgdra.UCAR.EDU!dave (Dave Darr)
Message-Id: <8806152231.AA05114@cgdra.UCAR.EDU>
Received: by cgdra.UCAR.EDU (3.2/1.00.UUCP-MOD.8-11-85)
id AA05114; Wed, 15 Jun 88 16:31:52 MDT
To: mcdonald@cygnus%colo
Subject: hey ho
--
Charlie Dennett - Eastman Kodak Company
UUCP: ...rutgers!rochester!kodak!dennett
...rutgers!rochester!kodak!cygnus!dennettbill@sigma.UUCP (Bill Swan) (06/18/88)
In article <1293@kodak.UUCP> dennett@kodak.UUCP (Charlie Dennett) writes: >Below is a bounced mail message that tried to go through a machine (cygnus) >that I administer here at Eastman Kodak. I'm not 100% sure how to read all >the path and addressing information, but it seems to me that some machine >along the way thinks there is another machine called cygnus. [...] It is possible for a machine to not have a map entry and still show up in routing info. I ran into this when I was going to name my home system "cygnus" (a natural for someone named "Swan"), but discovered that there was another machine by that name already connected. All that is necessary is for somebody to show a link to that machine in their map file. In this case "uuhosts" showed no entry for a machine named "cygnus", but "uupath" gave a path to it! Although registering and entry in the maps should show conflicts, if a new machine comes on the net and fails to register, it's left to their neighbours to find out if there's a conflict. I've run into this recently with "telesis", a neighbour here, but also the name of a machine elsewhere. Apparently some uucp-files have been misrouted to our site awaiting delivery to the nearby telesis (which is now dead). (I have updated our map entry, and if the neighbouring telesis ever comes up again I will inform him of the name conflict.) --Bill Swan -- .signature