Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!mimsy!cvl!umd5!dzoey
From: dzoey@umd5.umd.edu (Joe Herman)
Newsgroups: comp.mail.headers
Subject: Re: overuse of Received: headers
Message-ID: <1606@umd5.umd.edu>
Date: Sun, 3-May-87 14:28:19 EDT
Article-I.D.: umd5.1606
Posted: Sun May  3 14:28:19 1987
Date-Received: Sun, 3-May-87 21:58:06 EDT
References: <8UVxtLy00UkSdSw0Co@andrew.cmu.edu> <900@maynard.BSW.COM> <1761@lsuc.UUCP> <686@van-bc.UUCP>
Reply-To: dzoey@umd5.umd.edu.UUCP (Joe Herman)
Organization: University of Maryland, College Park
Lines: 24

I too find Received headers very useful, especially in trying to trace
a path to a uucp type of host.  Awhile back, I posted a request for
info on mail implementations.  I collected the responses and said that
if anyone was interested, I'd send them a copy.  I received about
fifteen replies.  Let me tell you, tracing the Received headers was the
only way I could generate replies to many of the requests.

I find it's becoming very difficult these days to tell which network a
host exists on.  There seems to be some sort of movement in the uucp
community to create addresses that look like internet addresses.
This makes looking at Received: headers a must for trying to route mail.

Since uucp hosts are starting to use domain format, does that mean that
they are registering their hosts with the NIC and future name resolution
will provide me with a path to that host?


				Oh well, I've said my share,
					joe

dzoey@terminus.umd.edu   (for people w/o domain resolvers: dzoey@umd5.umd.edu)
{seismo, inhp4!rlgvax!cvl}!terminus.umd.edu!dzoey
-- 
"Everything is wonderful until you know something about it."