Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!sdd.hp.com!ucsd!helios.ee.lbl.gov!nosc!logicon.com!Makey
From: Makey@Logicon.COM (Jeff Makey)
Newsgroups: comp.mail.uucp
Subject: Re: Imminent death of UUCP Zone predicted
Message-ID: <701@logicon.com>
Date: 6 Jul 90 20:50:49 GMT
References: <3008.268b1e9a@mccall.com> <KARL.90Jun29151044@giza.cis.ohio-state.edu> <2723@litchi.bbn.com> <ANSELMO-ED.90Jul6120157@bigbird.cs.yale.edu>
Organization: Logicon, Inc., San Diego, California
Lines: 19
X-Local-Date: 6 Jul 90 13:50:49 PDT

In article <ANSELMO-ED.90Jul6120157@bigbird.cs.yale.edu> Anselmo-Ed@cs.yale.edu (Ed Anselmo) writes:
>If you flatten the UUCP envelope from foo.dom.ain to foo (or whatever
>their UUCP name is), then unless an intermediate site tries to be cute
>about things (i.e. expanding UUCP names into domains), there shouldn't
>be much trouble (famous last words...).

I don't consider it "cute," but my site (which gateways only a couple
of dozen messages per day between Internet and UUCP) has been
carefully tailored to do *both* of these things.  During address
canonicalization a selected set of .UUCP names are rewritten as their
corresponding fully qualified domain names.  Only when delivery is
actually to be made via UUCP is the FQDN replaced with the
corresponding .UUCP name.

                           :: 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