Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.2 9/18/84; site ncr-sd.UUCP Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!mhuxt!houxm!vax135!cornell!uw-beaver!tektronix!hplabs!sdcrdcf!sdcsvax!ncr-sd!greg From: greg@ncr-sd.UUCP (Greg Noel) Newsgroups: net.mail Subject: Re: Mail addressing and routing Message-ID: <263@ncr-sd.UUCP> Date: Tue, 20-Aug-85 20:37:08 EDT Article-I.D.: ncr-sd.263 Posted: Tue Aug 20 20:37:08 1985 Date-Received: Sun, 25-Aug-85 05:00:57 EDT References: <644@adobe.UUCP> <734@vortex.UUCP> <1156@umcp-cs.UUCP> Reply-To: greg@ncr-sd.UUCP (Greg Noel) Organization: NCR Corporation, Torrey Pines Lines: 82 In article <1156@umcp-cs.UUCP> chris@umcp-cs.UUCP (Chris Torek) writes: >If I ever get shanghaid [sic] into hacking mailers, I would probably >implement the "UUCP" "domain" like this: > > [I tried to cut this down to the portion I wanted to talk about, but > it still ended up 50 lines. Instead, I recommend that you go back and > read the original article; there's much food for thought. The thing > I wanted to discuss was the section on his "mailer."] > Hmmmmmm...... This is very interesting, since it parallels what I have been thinking about. However, instead of a database that converts host.in.a.domain into partial!path!prefix to be handed to uux, I would propose that the data base convert it into a command. So, in your example, you would convert "tinyhost.smalluniv.bigcity.calif.uucp" into something like "uux -<%F seismo!rmail (vortex!%U@%H)" which would then be expanded into "uux -