Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 4.3bsd-beta 6/6/85; site noscvax.UUCP
Path: utzoo!decvax!ittatc!dcdwest!sdcsvax!noscvax!broman
From: broman@noscvax.UUCP (Vincent P. Broman)
Newsgroups: net.mail
Subject: Re: Help in using UUCP gateways
Message-ID: <453@noscvax.UUCP>
Date: Mon, 5-May-86 13:04:15 EDT
Article-I.D.: noscvax.453
Posted: Mon May  5 13:04:15 1986
Date-Received: Tue, 6-May-86 23:50:30 EDT
References: <415@marque.UUCP>
Distribution: na
Organization: Naval Ocean Systems Center, San Diego
Lines: 46
Summary: many gateways use name@host.domain

Many address paths through gateways can be specified by a mixture of
address ::= address@host.domain
address ::= uucpsite!address
productions. Mixtures of the two syntaxes must be interpreted in the correct
order by the intermediate mailers, and I don't how universally that will happen.

Examples ---

I am on a machine with both ARPA and UUCP access. Seismo is another. My mail to
ihnp4!person@seismo.arpa goes to seismo first and then to ihnp4.
Person could reply to seismo!me@nosc.arpa . Since ihnp4 is not on ARPANET,
"me@nosc.arpa" is just a complicated name for an addressee at seismo,
delivery to which is taken care of by the mailer at seismo.

I can send CSNET mail to someone%foo.csnet@csnet-relay.arpa, so that
ihnp4!person would write to seismo!someone%foo.csnet@csnet-relay.arpa .
This would take the path ihnp4 -> seismo -> csnet-relay -> foo .
The return address would look something like ihnp4!person@seismo because
csnet-relay recognizes the '@' to mean ARPANET.

BITNET mail through wiscvm.arpa should be somewhat similar.

Mailnet addresses go through mit-multics and look like:
colleague%durham.mailnet@mit-multics.arpa who replies to
me%nosc.arpa@mit-multics .
Simile brit%machine.janet@ucl-cs.arpa who can reply to me%nosc.arpa@ucl-cs .

DECNET (ENET) mail to machines is more complicated, I think, but often some
kind of externally understandable name is available like:
decperson%hismachine.dec@decwrl.arpa which gets translated along the way to
their internal system of names. Decperson would reply to
RHEA::DECWRL::"user@host.arpa" . One might hope that one could substitute
ihnp4!person for user, for instance, since decwrl does talk uucp to ihnp4. Only
the '!' might not be a legal character.

I do not know how many machines will gateway between arpanet and uucpnet,
but ucbvax, sdcsvax, seismo, and harvard do. Purdue and Ucl-cs do not,
even though they are accessible from both nets under the same name.
(i.e. ucl-cs.arpa == ucl-cs.uucp, etc)  I have a list of 30-40 other machines
that Might gateway, but I've only tested a portion of them by use.
If anyone has hard information about that, tell me!


Vincent Broman, code 632,  Naval Ocean Systems Center, San Diego, CA 92152, USA
Phone: +1 619 225 2365     Starship: 32d 42m 22s N/ 117d 14m 13s W
Arpa: broman@bugs.nosc.mil Uucp: {floyd,moss,bang,gould9,sdcsvax}!noscvax!broman