Path: utzoo!attcan!uunet!lll-winken!lll-lcc!ames!pasteur!ucbvax!decwrl!reid
From: reid@decwrl.dec.com (Brian Reid)
Newsgroups: comp.mail.uucp
Subject: Re: Routing mail through Digital's sites
Message-ID: <616@bacchus.DEC.COM>
Date: 19 Jul 88 15:51:10 GMT
References: <651@scovert.sco.COM> <30.UUL1.3#935@aocgl.UUCP> <2761@ttrdc.UUCP> <271@mjbtn.UUCP> <84@holin.ATT.COM> <119@carpet.WLK.COM> <599@bacchus.DEC.COM> <121@carpet.WLK.COM> <606@bacchus.DEC.COM> <122@carpet.WLK.COM> <3501@palo-alto.DEC.COM>
Reply-To: reid@decwrl.UUCP (Brian Reid)
Distribution: na
Organization: DEC Western Research
Lines: 12

In article <3501@palo-alto.DEC.COM> vixie@palo-alto.DEC.COM (Paul Vixie) writes:
>Yup.  No UUCP routing.  If you send mail to decwrl!xyzzy!person, then xyzzy
>had better be one of...
>
>	a dotted internet domain, MX or A record known to the root named's
>	an internal (decnet or SMTP) host
>	a UUCP neighbor of decwrl
>
>...the one thing we don't do (yet) is find a path to "xyzzy" if they aren't
>found in the above search path but are in the UUCP map.

And with a little luck, we never will. This kind of pseudo-AI belongs in user
agents, not transport.