Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site mit-eddie.UUCP
Path: utzoo!linus!decvax!tektronix!hplabs!qantel!ihnp4!mit-eddie!gds
From: gds@mit-eddie.UUCP (Greg Skinner)
Newsgroups: net.mail
Subject: Re: Mail addressing and routing
Message-ID: <5317@mit-eddie.UUCP>
Date: Sun, 15-Sep-85 16:38:39 EDT
Article-I.D.: mit-eddi.5317
Posted: Sun Sep 15 16:38:39 1985
Date-Received: Wed, 25-Sep-85 09:14:49 EDT
References: <644@adobe.UUCP> <734@vortex.UUCP> <1156@umcp-cs.UUCP> <263@ncr-sd.UUCP> <1468@cbosgd.UUCP>
Organization: MIT Lusers and Hosers Inc., Cambridge, Ma.
Lines: 23

There isn't any way for ihnp4 to know that ihnp4!horton is actually
ihnp4!cbosgd!mark, especially if thefre is a horton on ihnp4.  However,
if there isn't, I suppose this simple scheme can be used when you only
know the last name.

when mailing to host!user,

if "user" maps to a local name on host, deliver it to user (ie. search
/etc/passwd),
else, apply the database searcher to "user" (the only problem is that
there may be many "user"'s in the database, and I don't know if it is
politically correct to return a list of possible completions of "user"
to the sendng agent)
else, just return the mail as usual.

Gary and Mark, is this currently done from outside AT&T?  I know it's
done internally.
-- 
It's like a jungle sometimes, it makes me wonder how I keep from goin' under.

Greg Skinner (gregbo)
{decvax!genrad, allegra, ihnp4}!mit-eddie!gds
gds@mit-eddie.mit.edu


Brought to you by Super Global Mega Corp .com