Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uwm.edu!rpi!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!aplcen!wb3ffv!ka3ovk!raysnec!shwake
From: shwake@raysnec.UUCP (Ray Shwake)
Newsgroups: comp.mail.uucp
Subject: Re: Imminent death of UUCP Zone predicted
Summary: Just a little followup to someone who doesn't quite "get" it
Message-ID: <104@raysnec.UUCP>
Date: 12 Jul 90 22:44:19 GMT
References: <1990Jun28.164938.23367@DSI.COM> <KARL.90Jun28154651@giza.cis.ohio-state.edu> <3008.268b1e9a@mccall.com> <26669@ditka.UUCP> <7871@lynx.UUCP> <100@raysnec.UUCP> <269B82AE.415E@intercon.com>
Reply-To: shwake@raysnec.UUCP (Ray Shwake)
Distribution: na
Organization: IRS - ACI Project Office
Lines: 27

In article <269B82AE.415E@intercon.com> amanda@mermaid.intercon.com (Amanda Walker) writes:

>> 		user@sitename	(specified user AT specified sitename)
>> 		site!...!site!user	(reach user by following this path)
>
>Fine so far.  However, the second is not an address.  It is a route.  There
>are many mailers that blur the distinction, but it is there nonetheless.

	Of COURSE it's a route. But it's also an address. Just like the
	scribble on the front of the USnail envelope you received yesterday
	is both address and route.

>> 		site!...!site!user@knownsite (reach user by following this
>> 			path once you reach a known site)
>
>This is broken.  This is not guaranteed to work, and is guaranteed not to
>work for many values of "knownsite" (any site I run, for example).
>The ability to tunnel UUCP paths through the Internet is a bug.

	As we used to say, "Where you stand [on an issue] depends on where
	you sit".  My own submission should properly be seen as a set of
	"postulates", a way of returning to first principles, if you will.
	The fact that your own mailers and routers couldn't handle such
	an environment might suggest that YOUR system is broken, n'est pas?

	That fact that sites ON the Internet can handle UUCP traffic is,
	in my book, hardly a bug. If it couldn't, it would be worthless to me.