ESC1332@ESOC.BITNET.UUCP (09/02/87)
I am trying to communicate with a VAX site in Australia but haven't got any idea how to route the messages. Maybe this isn't the correct forum to aim my query, but does ANYONE out there have any notion of how to communicate with Australian nodes? Any help would be greatly appreciated. Please answer directly to me. Thanks, Karl
KHF@JHUIGF.BITNET.UUCP (09/07/87)
Re: Karl Keyte's request for Australian node addresses
------------------------------------------------------------------------------
If you have access to gMAIL.COM (older version is SENDGATE.COM), the following
should be sufficient:
user@domain.OZ
Possible alternatives to try are:
1) user%domain.OZ@RELAY.CS.NET
2) "MUNNARI!domain.OZ!user@SEISMO.ARPA"
3) "MUNNARI!domain.OZ!user@SEISMO.CSS.GOV"
(where, in each case, "user" is the account you're trying to reach and
"domain" is the local node name)
We've only sent mail there via gMAIL, so I can't speak to the appropriateness
of the alternative addresses.
-------------------------------------------------------------------------------
Ken Fasman
U.S. Mail: Bard Laboratories of Neurophysiology
Johns Hopkins School of Medicine
725 N. Wolfe St.
Baltimore MD 21205
Telephone: (301) 955-8330
BITNET: KHF@JHUIGF
"My opinions, especially the wrong ones, are strictly my own."
-------------------------------------------------------------------------------carl@CITHEX.CALTECH.EDU (Carl J Lydick) (09/08/87)
> Re: Karl Keyte's request for Australian node addresses > ------------------------------------------------------------------------------ > If you have access to gMAIL.COM (older version is SENDGATE.COM), the following > should be sufficient: > > user@domain.OZ > > Possible alternatives to try are: > > 1) user%domain.OZ@RELAY.CS.NET > 2) "MUNNARI!domain.OZ!user@SEISMO.ARPA" > 3) "MUNNARI!domain.OZ!user@SEISMO.CSS.GOV" > > (where, in each case, "user" is the account you're trying to reach and > "domain" is the local node name) > We've only sent mail there via gMAIL, so I can't speak to the appropriateness > of the alternative addresses. > ------------------------------------------------------------------------------- > . > . > . > "My opinions, especially the wrong ones, are strictly my own." (Flame on) This opinion must have been one of his own, since, to the extent that he is right, GMAIL is wrong. In a suitably configured version of GMAIL, what he suggests will work. However, GMAIL SHOULD NOT come configured with a gateway to down under wired in. One version of it was being distributed a while back with CITHEX as the default BITNET to HEPnet/SPAN gateway (and this when my poor 780 had only 4Mb of memory and maybe 2% null time BEFORE we started getting all this internetwork traffic!). I THINK (i.e., please, Mr. SYSTEM MANAGER at MUNNARI and similarly at SEISMO, don't yell at me too much if I'm wrong; and anybody else, please check with the system managers at MUNNARI AND SEISMO BEFORE using their machines as gateways) that alternative 3) is correct. (Flame off) You may now remove the asbestos pads from your terminals. A note here on internetwork etiquette: There are many machines out there that connect to two or more networks. A sizeable number of these machines have mailers that will act as gateways between the networks to which they are configured (CITHEX is among these. Due to the unfortunate GMAIL incident, it's mailer has been hacked to prevent its use as a gateway between various networks unless the mail originates or is destined for a machine at Caltech; it used to be available as a gateway of last resort, but this is no longer the case). In general, these machines ARE NOT to be used as gateways except by a few other machines. The reason for this is simple and BERKELEY provides the classic example of why: they've now got (last I heard) two VAXen doing nothing but being internetwork gateways! Gatewaying takes (non-chargeable) resources. When you send mail through a gateway, unless that machine has an agreement with the networks in question, they can't recover the costs of processing your mail. You should, therefore, ALWAYS consult with the system manager of any machines you intend to use as default gateways BEFORE doing so. If nothing else, this will save said managers the trouble of figuring out where their CPU time is suddenly being eaten.