(Message nnsc-pol-proc:4)
Received: from Osprey.Telcom.Arizona.EDU by NNSC.NSF.NET id aa03708;
          14 Oct 92 15:30 EDT
Received: from Arizona.edu by Arizona.edu (PMDF #2381 ) id
 <01GPXT683R9I96VKBH@Arizona.edu>; Wed, 14 Oct 1992 12:29:44 MST
Date: 14 Oct 1992 12:29:44 -0700 (MST)
From: Aaron Leonard <LEONARD@arizona.edu>
Subject: [mail]mail.gateway from Arizona.EDU
To: pol-proc-doc@NNSC.NSF.NET
Message-id: <01GPXT683R9K96VKBH@Arizona.edu>
X-VMS-To: IN%"pol-proc-doc@NNSC.NSF.NET"
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT


                      THE TELECOMMUNICATIONS MAIL GATEWAY
                            A. Leonard/25-Mar-1990

0. The Telecommunications Mail Gateway - Introduction.

The Telecommunications VAXcluster services the electronic mail gateway needs
of the University of Arizona campus.  It does NOT provide users with login
accounts with which to access electronic mail - that is the responsibility of
the users' departments - but it does provide a store-and-forward mail gateway
service, to allow users to send mail between DECnet, TCP/IP (the Internet),
and RSCS (BITNET).  It does this at the transport level by being directly
connected to DECnet, the Internet and BITNET, and at the application level by
running the PMDF mail gateway software.


1. The TELCOM Mail Gateway - Goals.

Following are some of the goals of the TELCOM mail gateway:

* Compliance with current Internet standards, for example, with section 5
  ("Electronic Mail -- SMTP and RFC-822") of RFC1123 ("Requirements for
  Internet Hosts -- Application and Support")

* A maximum of 5 minutes turnaround time (i.e. between the time that 
  Telcom.Arizona.EDU picks up the mail and when it sends it out another 
  interface.)

* Correct domain nameservice lookup and MX understanding across the Internet

* Store and forward capability, with frequent, long-lived retrying

* Offering MX service for any SMTP, Mail-11 (DECnet), or RSCS capable client 
  on campus.


2. What the Telcom Gateway Intends To Support.

We will claim to understand the following domains -

* Any Internet domain, namely those that are listed in NETINFO:DOMAINS.TXT 
  on NIC.DDN.MIL (in the UA netinfo tree as [.HOSTS.SRI]DOMAINS.TXT).  
  This includes as of this writing the following domains: .AR, .ARPA, .AT,
  .AU, .BE, .BR, .CA, .CH, .CL, .COM, .DE, .DK, .EDU, .ES, .FI, .FR, .GOV,
  .GR, .IE, .IL, .IN, .INT, .IS, .IT, .JP, .KR, .MIL, .MX, .MY, .NET, .NI,
  .NL, .NO, .NZ, .ORG, .PR, .PT, .SE, .SG, .TH, .TW, .UK, .US, and .YU.

* BITNET (.BITNET); SPAN (.SPAN); Hepnet (.HEPNET); uucp (.UUCP - well, we 
  don't claim to actually *understand* uucp, but we will try to punt such 
  addresses as best we can.)

We support the following maximum sizes per message:

* For mail outbound to BITNET, 300,000 bytes (586 VAX blocks) - this is per
  the BITNET Usage Guideline.

* For mail outbound to DECnet or the Internet, 1MB (2048 VAX blocks).

Please note that these maxima may be temporarily reduced in instances of
extreme congestion.


3. Using the Telcom Gateway - Examples.

Here's examples of how to use the Telcom gateway:

a. Mail from Arizonet DECnet to remote network:

If you are on an Arizonet DECnet machine, then do it thus:

  To: TELCOM::IN%"<user@host.domain>"

For example, to send to user `jrandom' on node foovax.throckmorton.edu, 
send to: TELCOM::IN%"<jrandom@foovax.throckmorton.edu>"

b. Mail from Internet (TCP/IP) to non-Internet network:

If you are on an Internet machine with SMTP (for example, a Sun) and
you want to send mail to a non-Internet network, then do it thus:

  To: user%host.domain@Arizona.EDU

For example, to send mail to user `BIGBLUE' on BITNET node MITEYMVS, 
send to: BIGBLUE%MITEYMVS.BITNET@Arizona.EDU

c. Mail from Internet to Arizonet DECnet 

If you are on an Arizonet DECnet machine, then YOUR network mail address
with respect to users on the Internet will be:

  you%yournode.DECnet@Arizona.EDU

For example, if you are GURU on DECnet node BIGVAX, then Internet users
would be able to reach you via SMTP as:

  GURU%BIGVAX.DECNET@Arizona.EDU.

Alternatively, you could register BIGVAX in your administrative domain
to receive MX service from telcom.  In that case, assuming that
BIGVAX is in the subdomain Housekeeping, then your Internet mail address
would be:

  GURU@BIGVAX.Housekeeping.Arizona.EDU


4. Setting up your system as a mail client of the Telcom gateway.

If you are system manager of a mail-capable system, you may want to set
your system up so as best to take advantage of the Telcom mail gateway 
services. 

If you are running MultiNet version 2.1 or greater, then we recommend that
you set up Arizona.EDU as your "SMTP forwarder".  To do this, 
$ MULTINET CONFIG
config> set smtp-forwarder Arizona.EDU
config> exit
On your next reboot, your system will send mail to all non-Internet domains
via Arizona.EDU.  For example, your users will be able to send mail to
SMTP%"user@somewhere.BITNET", and Arizona.EDU will handle the mail for you.

If you are running a VAX/VMS system on the Arizonet DECnet, then you can
set up a system-wide logical name thus:
$ DEFINE/SYSTEM IN "TELCOM::IN%"
such that your users will be able to send all non-DECnet mail via the TELCOM
gateway thus:
To: IN::"user@somewhere.BITNET"

If you are running Sendmail on a Unix system, then we recommend that you
set up your sendmail.cf file to take advantage of TELCOM's capabilities.
For a (bad) example of such a sendmail.cf file, see the file
[mail]sendmail.cf-template on Arizona.EDU; for more details, consult your
local guru. 

-----

Please give our gateway service a good workout.  Joseph Zaepfel of 
Telecom Network Operations is our Postmaster; please direct suggestions, 
etc. to him (DECnet: TELCOM::POSTMASTER; Internet: Postmaster@Arizona.EDU).