Path: utzoo!utgpu!watmath!xenitec!edhew
From: edhew@xenitec.uucp (Ed Hew)
Newsgroups: news.newusers.questions
Subject: Re: How do I get from here to there? (E-mail to various nets)
Message-ID: <1989Aug13.080454.6719@xenitec.uucp>
Date: 13 Aug 89 08:04:54 GMT
References: <1676@sactoh0> <2573@dell.dell.com> <391@wet.UUCP> <2617@dell.dell.com>
Reply-To: edhew@xenitec.UUCP (Ed Hew)
Followup-To: news.newusers.questions
Distribution: na
Organization: Xenitec Consulting Services, Kitchener, ON
Lines: 62

In article <2617@dell.dell.com> mikeh@dell.UUCP (Mike Hammel, ) writes:
>In article <391@wet.UUCP> epsilon@wet.UUCP (Eric P. Scott) writes:
>>In article <2573@dell.dell.com> mikeh@dell.UUCP (Mike Hammel, ) writes:
>>>From UUCP to Bitnet:
>>>	node.BITNET!userid	where node is the Bitnet node and userid is
>>>				the userid on that Bitnet node
>>
>>Funny, I'm not aware of any UNIX system "out of the box" that
>>will accept this.  Even systems shipped with sendmail--the
>>supplied configuration files had no BITNET hacks.  If this
>>works on your system it's because someone specifically provided
>>to intercept it--both uucp and DNS will reject node.BITNET.
>
>You're right.  I tried it again and it didn't work.  That response was taken
>from a response I got from a list on Bitnet (can't remember which one).

I might suspect that the answer would be that:

		BITNET.node!uid@BITNET_gateway
		^^^^^^^^^^^ ^^^ ^^^^^^^^^^^^^^
		where_to    who   who's.forwarding

*might* work, provided your site is talking directly to a BITNET gateway
host, which may or may not be the case.  If the site downstream isn't
a gateway, or the host your site talks to isn't running a good smartmailer,
this probably *won't* work.

>I take it that UUCPnode!node.BITNET!userid would work if the UUCP node knows
>what to do witht the rest of the address (such as psuvax1, I was told, would).

The key words here are "...if the UUCP node knows what to do with the rest
of the address..."
More appropriate on a complete bang path-syntax would be:

	UUCP-BITNET_gateway!node.BITNET!uid

where your site connects *directly* with a BITNET gateway.

I suppose the point is that it is most relevant that your site must either
have a useful smart mail installed, or at very least talk *directly* to one
that has, or is a gateway.

You can always experiment.  Try out some of the examples we've been
discussing.  One of two things will happen:

	a/	your mail will likely be bounced from the immediate
		host site, if not internally (no harm done), but with
		some useful diagnostic messages.
	b/	it will work.

If all else fails, contact your sysadmin.  (on most systems you can
reach that party simply by mailing "root" or "postmaster").  He/she
should know the specifics for your site connectivity.

>Michael J. Hammel   | UUCP(preferred): ...!cs.utexas.edu!dell!Kepler!mjhammel
>Dell Computer Corp. | Also: ...!dell!dell!mikeh  or 73377.3467@compuserve.com

  Ed. A. Hew       Authorized Technical Trainer        Xeni/Con Corporation
  work:  edhew@xenicon.uucp	 -or-	 ..!{uunet!}utai!lsuc!xenicon!edhew
->home:	 edhew@egvideo.uucp	 -or-	   ..!{uunet!}watmath!egvideo!edhew
->home:	 changing to:  edhew@xenitec.uucp     [but be patient for new maps]
  # I haven't lost my mind, it's backed up on floppy around here somewhere!