Path: utzoo!attcan!uunet!tut.cis.ohio-state.edu!cs.utexas.edu!swrinde!ucsd!nosc!logicon.com!Makey
From: Makey@Logicon.COM (Jeff Makey)
Newsgroups: comp.mail.uucp
Subject: Re: Imminent death of UUCP Zone predicted
Message-ID: <707@logicon.com>
Date: 12 Jul 90 18:27:31 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>
Organization: Logicon, Inc., San Diego, California
Lines: 26

In article <269B82AE.415E@intercon.com> amanda@mermaid.intercon.com (Amanda Walker) writes:
>> 		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).

If "knownsite" receives such an address via SMTP, and can reasonably
be expected to gateway UUCP mail traffic to the first "site" in the
bang-path, then "knownsite" has no valid excuse for failing to deal
with this properly.  Yes, there are plenty of UUCP-only sites that
don't grok site!user@fqdn the way Internet sites are supposed to;
that's why I always use pure bang-paths when sending mail via UUCP.

>The ability to tunnel UUCP paths through the Internet is a bug.

It's a feature.  Internet sites are required to ignore the presence of
bang-paths (and any other route encoding) in the local part of an
address, except when the FQDN on the right-hand side of the address is
that of the current host.

                           :: Jeff Makey

Department of Tautological Pleonasms and Superfluous Redundancies Department
    Disclaimer: All opinions are strictly those of the author.
    Internet: Makey@Logicon.COM    UUCP: {nosc,ucsd}!logicon.com!Makey