Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/17/84; site gang.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!ihnp4!gang!hokey
From: hokey@gang.UUCP (Hokey)
Newsgroups: net.mail
Subject: Re: UUCP/Bitnet Gateway at PSUVAX1 -- how to use it.
Message-ID: <549@gang.UUCP>
Date: Mon, 7-Jan-85 14:05:29 EST
Article-I.D.: gang.549
Posted: Mon Jan  7 14:05:29 1985
Date-Received: Tue, 8-Jan-85 05:21:48 EST
References: <1599@psuvax1.UUCP>
Organization: Plus Five Computer Services, St. Louis
Lines: 30

Mark Starner tells us:
> 
> After seeing all the discussion of gateways, etc.... I thought 
> I would set the record straight on how to use the gateway onto
> BITNET at Psuvax1.
> 
> The address is as follows: site!site!site!psuvax1!user@bitnethost.bitnet
> also: site!site!site!psuvax1!user%bitnethost.bitnet
> altenatively: @psuvax1.uucp:user@bitnethost.bitnet will also work.

There is a potential problem when using a hybrid route (site!user@place).
Specifically, the route is ambiguous.  Some sites bang-parse, while others
822 parse.  If any of the sites before psuvax1 decide to 822 parse, mail
will be messed up.  If sites along the way have a decent path parser which
uses an edge database to determine parsing, there is a significantly reduced
chance of error.

psuvax1 *should* allow mail to be sent like this:

	...!psuvax1!bitnethost.bitnet!user

which avoids the ambiguity.  The second example, which uses a % instead of
a @, may also be screwed up by sites along the way who use the % as a
delimiter for Other Things.

[Please forgive the inclusion of the first few lines of the referenced
article; I know it isn't the Fun thing to do!]
-- 
Hokey           ..ihnp4!plus5!hokey
		  314-725-9492