Path: utzoo!attcan!uunet!intercon!news From: amanda@mermaid.intercon.com (Amanda Walker) Newsgroups: comp.mail.uucp Subject: Re: Imminent death of UUCP Zone predicted Message-ID: <269D03E5.5995@intercon.com> Date: 12 Jul 90 23:12:37 GMT References: <1990Jun28.164938.23367@DSI.COM> <3008.268b1e9a@mccall.com> <26669@ditka.UUCP> <7871@lynx.UUCP> <100@raysnec.UUCP> <269B82AE.415E@intercon.com> <_2M4591@xds13.ferranti.com> Sender: usenet@intercon.com (USENET The Magnificent) Reply-To: amanda@mermaid.intercon.com (Amanda Walker) Organization: InterCon Systems Corporation, Herndon, VA Lines: 24 In article <_2M4591@xds13.ferranti.com>, peter@ficc.ferranti.com (Peter da Silva) writes: > going by the DNS mail to ferranti.com will be sent via uunet. So I get > mail sent from Rice University, not 20 miles (and 2 hops) away, sent via > Virginia, which I guess is about 2000 miles away. So? Rice can always have mail to *@*.ferranti.com routed to you via UUCP if this sort of efficiency is an issue. I, for example, do this with the Johns Hopkins Advanced Physics Lab. However, in exchange for "efficiency" (in this case, low latency), I have to take the responsibility of keeping my manual routing information up to date. This is only worth it for a few cases. Also, I don't have any problem with mumble!foo!zot@bar as a UUCP path. I just don't accept its legality as an internet address. How it gets to the Internet is irrelevant as long is it has a valid address once it gets there. If you want to get mail back from the internet, though, get a domain. Me, a domain bigot? You betcha, even though I run a UUCP-only site. -- Amanda Walker Postmaster With An Attitude InterCon Systems Corporation