[comp.mail.misc] InterNetworking Guide

ajay@cs.Buffalo.EDU (Ajay Shekhawat) (02/14/91)

Sometime ago I posted a query asking for the "Internetworking Guide".
Someone sent me a copy, and I'm posting it here.

Methinks I'll make it a fortnightly/monthly posting, and if you
have any updates, etc., send them over to me or the author.

Enjoy..

Ajay..


Ajay Shekhawat          <Dept. of Comp. Sci., SUNY@Buffalo, Amherst, NY 14260>
ajay@cs.Buffalo.EDU || ajay@sunybcs.BITNET || ajay@sunybcs.UUCP || 716.636.3180

------------------------------c-u-t----h-e-r-e-----------------------------
Inter-Network Mail Guide - Copyright 1990 by John J. Chew
  $Header: netmail,v 1.12 90/07/06 20:38:28 john Exp $

For those of you who were wondering what happened to the June 1990 issue,
there wasn't one, because of a lack of important changes to the data,
and because I've been busy with other things.  Even worse (:-), there
will not be an August 1990 issue as I will be temporarily between net
addresses as I take a nice long holiday between jobs on different
continents.  If you have information to add or requests for subscriptions,
send them as usual to me at <poslfit@gpu.UTCS.UToronto.CA> and they should
catch up to me with some delay wherever I end up.  I'm off to enjoy
my summer now, bye!  -- John

COPYRIGHT NOTICE

This document is Copyright 1990 by John J. Chew.  All rights reserved.
Permission for non-commercial distribution is hereby granted, provided
that this file is distributed intact, including this copyright notice
and the version information above.  Permission for commercial distribution
can be obtained by contacting the author as described below.

INTRODUCTION

This file documents methods of sending mail from one network to another.
It represents the aggregate knowledge of the readers of comp.mail.misc
and many contributors elsewhere.  If you know of any corrections or
additions to this file, please read the file format documentation below
and then mail to me: John J. Chew <poslfit@gpu.utcs.utoronto.ca>.  If
you do not have access to electronic mail (which makes me wonder about
the nature of your interest in the subject, but there does seem to be
a small such population out there) you can call me during the month of
July at +1 416 979 7166 between 11:00 and 24:00 EDT (UTC-4h) and most
likely talk to my answering machine (:-).

DISTRIBUTION

(news) This list is posted monthly to Usenet newsgroups comp.mail.misc and
  news.newusers.questions.  
(mail) I maintain a growing list of subscribers who receive each monthly 
  issue by electronic mail, and recommend this to anyone planning to 
  redistribute the list on a regular basis.  
(FTP) Internet users can fetch this guide by anonymous FTP as ~ftp/pub/docs/
  internetwork-mail-guide on Ra.MsState.Edu (130.18.80.10 or 130.18.96.37)
  [Courtesy of Frank W. Peters]
(Listserv) Bitnet users can fetch this guide from the Listserv at UNMVM.
  Send mail to LISTSERV@UNMVM with blank subject and body consisting of
  the line "GET NETWORK GUIDE".  [Courtesy of Art St. George]

HOW TO USE THIS GUIDE

Each entry in this file describes how to get from one network to another.
To keep this file at a reasonable size, methods that can be generated by
transitivity (A->B and B->C gives A->B->C) are omitted.  Entries are sorted
first by source network and then by destination network.  This is what a
typical entry looks like:

  #F mynet
  #T yournet
  #R youraddress
  #C contact address if any
  #I send to "youraddress@thegateway"

For parsing purposes, entries are separated by at least one blank line,
and each line of an entry begins with a `#' followed by a letter.  Lines
beginning with `# ' are comments and need not be parsed.  Lines which do
not start with a `#' at all should be ignored as they are probably mail
or news headers.

#F (from) and #T (to) lines specify source and destination networks.
If you're sending me information about a new network, please give me
a brief description of the network so that I can add it to the list
below.  The abbreviated network names used in #F and #T lines should
consist only of the characters a-z, 0-9 and `-' unless someone can
make a very convincing case for their favourite pi character.

These are the currently known networks with abbreviated names:

  applelink     AppleLink (Apple Computer, Inc.'s in-house network)
  bitnet        international academic network
  bix           Byte Information eXchange: Byte magazine's commercial BBS
  bmug          Berkeley Macintosh Users Group
  compuserve    commercial time-sharing service
  connect       Connect Professional Information Network (commercial)
  easynet       Easynet (DEC's in-house mail system)
  envoy	  Envoy-100 (Canadian commercial mail service)
  fax           Facsimile document transmission
  fidonet       PC-based BBS network
  geonet        GeoNet Mailbox Systems (commercial)
  internet      the Internet
  mci           MCI's commercial electronic mail service
  mfenet        Magnetic Fusion Energy Network
  nasamail      NASA internal electronic mail
  peacenet      non-profit mail service
  sinet         Schlumberger Information NETwork
  span          Space Physics Analysis Network (includes HEPnet)
  sprintmail    Sprint's commercial mail service (formerly Telemail)
  thenet        Texas Higher Education Network

#R (recipient) gives an example of an address on the destination network, 
to make it clear in subsequent lines what text requires subsitution.

#C (contact) gives an address for inquiries concerning the gateway,
expressed as an address reachable from the source (#F) network.
Presumably, if you can't get the gateway to work at all, then knowing
an unreachable address on another network will not be of great help.

#I (instructions) lines, of which there may be several, give verbal
instructions to a user of the source network to let them send mail
to a user on the destination network.  Text that needs to be typed
will appear in double quotes, with C-style escapes if necessary.

#F applelink
#T internet
#R user@domain
#I send to "user@domain@internet#"
#I   domain can be be of the form "site.bitnet", address must be <35 characters

#F bitnet
#T internet
#R user@domain
#I Methods for sending mail from Bitnet to the Internet vary depending on
#I what mail software is running at the Bitnet site in question.  In the
#I best case, users should simply be able to send mail to "user@domain".
#I If this doesn't work, try "user%domain@gateway" where "gateway" is a 
#I regional Bitnet-Internet gateway site.  Finally, if neither of these
#I works, you may have to try hand-coding an SMTP envelope for your mail.
#I If you have questions concerning this rather terse note, please try
#I contacting your local postmaster or system administrator first before
#I you send me mail -- John Chew <poslfit@gpu.utcs.utoronto.ca>

#F compuserve
#T fax
#R +1 415 555 1212
#I send to "FAX 14155551212" (only to U.S.A.)

#F compuserve
#T internet
#R user@domain
#I send to ">INTERNET:user@domain"

#F compuserve
#T mci
#R 123-4567
#I send to ">MCIMAIL:123-4567"

#F connect
#T internet
#R user@domain
#I send to CONNECT id "DASNET"
#I first line of message: "\"user@domain\"@DASNET"

#F easynet
#T bitnet
#R user@site
#C DECWRL::ADMIN
#I from VMS use NMAIL to send to "nm%DECWRL::\"user@site.bitnet\""
#I from Ultrix
#I   send to "user@site.bitnet" or if that fails
#I     (via IP) send to "\"user%site.bitnet\"@decwrl.dec.com"
#I     (via DECNET) send to "DECWRL::\"user@site.bitnet\""

#F easynet
#T fidonet
#R john smith at 1:2/3.4
#C DECWRL::ADMIN
#I from VMS use NMAIL to send to 
#I   "nm%DECWRL::\"john.smith@p4.f3.n2.z1.fidonet.org\""
#I from Ultrix
#I   send to "john.smith@p4.f3.n2.z1.fidonet.org" or if that fails
#I     (via IP) send to "\"john.smith%p4.f3.n2.z1.fidonet.org\"@decwrl.dec.com"
#I     (via DECNET) send to "DECWRL::\"john.smith@p4.f3.n2.z1.fidonet.org\""

#F easynet
#T internet
#R user@domain
#C DECWRL::ADMIN
#I from VMS use NMAIL to send to "nm%DECWRL::\"user@domain\""
#I from Ultrix
#I   send to "user@domain" or if that fails
#I     (via IP) send to "\"user%domain\"@decwrl.dec.com"
#I     (via DECNET) send to "DECWRL::\"user@domain\""

#F envoy
#T internet
#R user@domain
#C ICS.TEST or ICS.BOARD
#I send to "[RFC-822=\"user(a)domain\"]INTERNET/TELEMAIL/US
#I for special characters, use @=(a), !=(b), _=(u), any=(three octal digits)

#F fidonet
#T internet
#R user@domain
#I send to "uucp" at nearest gateway site
#I first line of message: "To: user@domain"

#F geonet
#T internet
#R user@domain
#I send to "DASNET"
#I subject line: "user@domain!subject"

#F internet
#T applelink
#R user
#I send to "user@applelink.apple.com"

#F internet
#T bitnet
#R user@site
#I send to "user%site.bitnet@gateway" where "gateway" is a gateway host that
#I   is on both the internet and bitnet.  Some examples of gateways are:
#I   cunyvm.cuny.edu mitvma.mit.edu.  Check first to see what local policies
#I   are concerning inter-network forwarding.

#F internet
#T bix
#R user
#I send to "user@dcibix.das.net"

#F internet
#T bmug
#R John Smith
#I send to "John.Smith@bmug.fidonet.org"

#F internet
#T compuserve
#R 71234,567
#I send to "71234.567@compuserve.com"
#I   note: Compuserve account IDs are pairs of octal numbers.  Ordinary
#I     consumer CIS user IDs begin with a `7' as shown.

#F internet
#T connect
#R NAME
#I send to "NAME@dcjcon.das.net"

#F internet
#T easynet
#R HOST::USER
#C admin@decwrl.dec.com
#I send to "user@host.enet.dec.com" or "user%host.enet@decwrl.dec.com"

#F internet
#T easynet
#R John Smith @ABC
#C admin@decwrl.dec.com
#I send to "John.Smith@ABC.MTS.DEC.COM"
#I (This syntax is for All-In-1 users.)

#F internet
#T envoy
#R John Smith (ID=userid)
#C /C=CA/ADMD=TELECOM.CANADA/ID=ICS.TEST/S=TEST_GROUP/@nasamail.nasa.gov
#C   for second method only
#I send to "uunet.uu.net!att!attmail!mhs!envoy!userid"
#I   or to "/C=CA/ADMD=TELECOM.CANADA/DD.ID=userid/PN=John_Smith/@Sprint.COM"

#F internet
#T fidonet
#R john smith at 1:2/3.4
#I send to "john.smith@p4.f3.n2.z1.fidonet.org" 

#F internet
#T geonet
#R user at host
#I send to "user:host@map.das.net"
#I American host is geo4, European host is geo1.

#F internet
#T mci
#R John Smith (123-4567)
#I send to "1234567@mcimail.com"
#I or send to "JSMITH@mcimail.com" if "JSMITH" is unique
#I or send to "John_Smith@mcimail.com" if "John Smith" is unique - note the
#I    underscore!
#I or send to "John_Smith/1234567@mcimail.com" if "John Smith" is NOT unique

#F internet
#T mfenet
#R user@mfenode
#I send to "user%mfenode.mfenet@nmfecc.arpa"

#F internet
#T nasamail
#R user
#C <postmaster@ames.arc.nasa.gov>
#I send to "user@nasamail.nasa.gov"

#F internet
#T peacenet
#R user
#C <support%cdp@arisia.xerox.com>
#I send to "user%cdp@arisia.xerox.com"

#F internet
#T sinet
#R node::user or node1::node::user
#I send to "user@node.SINet.SLB.COM" or "user%node@node1.SINet.SLB.COM"

#F internet
#T span
#R user@host
#C <NETMGR@nssdca.gsfc.nasa.gov>
#I send to "user@host.span.NASA.gov"
#I   or to "user%host.span@ames.arc.nasa.gov"

#F internet
#T sprintmail
#R [userid "John Smith"/organization]system/country
#I send to "/C=country/ADMD=system/O=organization/PN=John_Smith/DD.ID=userid/@Sprint.COM"

#F internet
#T thenet
#R user@host
#I send to "user%host.decnet@utadnx.cc.utexas.edu"

#F mci
#T internet
#R John Smith <user@domain>
#I at the "To:" prompt type "John Smith (EMS)"
#I at the "EMS:" prompt type "internet"
#I at the "Mbx:" prompt type "user@domain"

#F nasamail
#T internet
#R user@domain
#I at the "To:" prompt type "POSTMAN"
#I at the "Subject:" prompt enter the subject of your message
#I at the "Text:" prompt, i.e. as the first line of your message,
#I    enter "To: user@domain"

#F sinet
#T internet
#R user@domain
#I send to "M_MAILNOW::M_INTERNET::\"user@domain\""
#I      or "M_MAILNOW::M_INTERNET::domain::user"

#F span
#T internet
#R user@domain
#C NETMGR@NSSDCA
#I send to "AMES::\"user@domain\""

#F sprintmail
#T internet
#R user@domain
#I send to "[RFC-822=user(a)domain @GATEWAY]INTERNET/TELEMAIL/US"

#F thenet
#T internet
#R user@domain
#I send to UTADNX::WINS%" user@domain "

END

raymond@math.berkeley.edu (Raymond Chen) (02/14/91)

As a supplement, here are networks known *not* to have email gateways.

Network             Comments
-------             ---------------------------------------------------
American Online     Masato Ogawa (ogawa@sm.sony.co.jp) confirms
                    that there is no gateway.

Dialog              mcmahan@netcom.UUCP (Dave Mc Mahan) reports that
                    nobody responded to his query in October 1990.

GEnie               No gateway yet, but Bill Louden, the General Manager of
                    GEnie, has stated publically that they are currently doing
                    research into the feasibility of a gateway.  Trust me,
                    if such a gateway is set up, you'll hear about it.

                    By the way, the machine genie.com is a red herring.

HandsNet            oze3@quads.uchicago.edu (J. Daniel Ozeran) reports
                    that nobody responded to his query in January 1991.

Midas Internation headquarters in Chicago
                    IO00393@MAINE.BITNET (Pete) reports that nobody
                    responded to his query in January 1991.

Nifty-Serve         a Japanese BBS
                    suzuki@sai.vtt.fi (Makoto Suzuki) contacted the
                    system operators and confirmed that there is no gateway.

Prodigy             by IBM and Sears
                    censors email
                    charges the sender of the mail message
                    Censorship details available from comp.risks issue 10.46.

Robert Halloran (rkh@mtune.ATT.COM) notes:

[GEnie, Prodigy, and American Online] have all apparently been approached more
than once about gateways, and have refused to let all that un-screened (and
FREE!) mail onto their respective networks....

Denise Caruso (SF Chronicle, 11 Nov 1990, page D-14) writes:

    It's common knowledge that almost all the online services
    censor their membership to greater or lesser degrees.
    [Prodigy is] widely acknowledged to be losing money on the [email]
    service.

ajay@CS.BUFFALO.EDU (Ajay Shekhawat) (03/23/91)

Last updated: Fri Mar 22 14:58:55 EST 1991

---------
Contents:
	I : The Internetworking Guide
	II: Networks NOT(yet) reachable from Internet.
--------

Inter-Network Mail Guide - Copyright 1990 by John J. Chew
  $Header: netmail,v 1.12 90/07/06 20:38:28 john Exp $

COPYRIGHT NOTICE

This document is Copyright 1990 by John J. Chew.  All rights reserved.
Permission for non-commercial distribution is hereby granted, provided
that this file is distributed intact, including this copyright notice
and the version information above.  Permission for commercial distribution
can be obtained by contacting the author as described below.

INTRODUCTION

This file documents methods of sending mail from one network to another.
It represents the aggregate knowledge of the readers of comp.mail.misc
and many contributors elsewhere.  If you know of any corrections or
additions to this file, please read the file format documentation below
and then mail to me: John J. Chew <poslfit@gpu.utcs.utoronto.ca>.  If
you do not have access to electronic mail (which makes me wonder about
the nature of your interest in the subject, but there does seem to be
a small such population out there) you can call me during the month of
July at +1 416 979 7166 between 11:00 and 24:00 EDT (UTC-4h) and most
likely talk to my answering machine (:-).

DISTRIBUTION

(news) This list is posted monthly to Usenet newsgroups comp.mail.misc and
  news.newusers.questions.  
(mail) I maintain a growing list of subscribers who receive each monthly 
  issue by electronic mail, and recommend this to anyone planning to 
  redistribute the list on a regular basis.  
(FTP) Internet users can fetch this guide by anonymous FTP as ~ftp/pub/docs/
  internetwork-mail-guide on Ra.MsState.Edu (130.18.80.10 or 130.18.96.37)
  [Courtesy of Frank W. Peters]
(Listserv) Bitnet users can fetch this guide from the Listserv at UNMVM.
  Send mail to LISTSERV@UNMVM with blank subject and body consisting of
  the line "GET NETWORK GUIDE".  [Courtesy of Art St. George]

HOW TO USE THIS GUIDE

Each entry in this file describes how to get from one network to another.
To keep this file at a reasonable size, methods that can be generated by
transitivity (A->B and B->C gives A->B->C) are omitted.  Entries are sorted
first by source network and then by destination network.  This is what a
typical entry looks like:

  #F mynet
  #T yournet
  #R youraddress
  #C contact address if any
  #I send to "youraddress@thegateway"

For parsing purposes, entries are separated by at least one blank line,
and each line of an entry begins with a `#' followed by a letter.  Lines
beginning with `# ' are comments and need not be parsed.  Lines which do
not start with a `#' at all should be ignored as they are probably mail
or news headers.

#F (from) and #T (to) lines specify source and destination networks.
If you're sending me information about a new network, please give me
a brief description of the network so that I can add it to the list
below.  The abbreviated network names used in #F and #T lines should
consist only of the characters a-z, 0-9 and `-' unless someone can
make a very convincing case for their favourite pi character.

These are the currently known networks with abbreviated names:

  applelink     AppleLink (Apple Computer, Inc.'s in-house network)
  attmail	AT&T Mail,AT&T's commercial e-mail service.
  bitnet        international academic network
  bix           Byte Information eXchange: Byte magazine's commercial BBS
  bmug          Berkeley Macintosh Users Group
  compuserve    commercial time-sharing service
  connect       Connect Professional Information Network (commercial)
  easynet       Easynet (DEC's in-house mail system)
  envoy	  Envoy-100 (Canadian commercial mail service)
  fax           Facsimile document transmission
  fidonet       PC-based BBS network
  geonet        GeoNet Mailbox Systems (commercial)
  internet      the Internet
  mci           MCI's commercial electronic mail service
  mfenet        Magnetic Fusion Energy Network
  nasamail      NASA internal electronic mail
  peacenet      non-profit mail service
  sinet         Schlumberger Information NETwork
  span          Space Physics Analysis Network (includes HEPnet)
  sprintmail    Sprint's commercial mail service (formerly Telemail)
  thenet        Texas Higher Education Network

/* Additions */
/*
   Given below are the additions made, along with the sender's address:
            Network				Sender
	    
	 AT & T Mail		Tony Hansen (att!pegasus!hansen)
	 UNINet			Erik   (erik@cs.kun.nl)
	 SIGNet			Erik   (erik@cs.kun.nl)
_Ajay
*/


#R (recipient) gives an example of an address on the destination network, 
to make it clear in subsequent lines what text requires subsitution.

#C (contact) gives an address for inquiries concerning the gateway,
expressed as an address reachable from the source (#F) network.
Presumably, if you can't get the gateway to work at all, then knowing
an unreachable address on another network will not be of great help.

#I (instructions) lines, of which there may be several, give verbal
instructions to a user of the source network to let them send mail
to a user on the destination network.  Text that needs to be typed
will appear in double quotes, with C-style escapes if necessary.


#F applelink
#T internet
#R user@domain
#I send to "user@domain@internet#"
#I   domain can be be of the form "site.bitnet", address must be <35 characters

#F AT&T Mail (attmail)
#T internet
#R internet!domain!user
#C AT&T Mail Customer Assisistance Center, 1-800-624-5672 (1-800-MAIL-672)
#I For an address "user@domain", send to "internet!domain!user". 

#F bitnet
#T internet
#R user@domain
#I Methods for sending mail from Bitnet to the Internet vary depending on
#I what mail software is running at the Bitnet site in question.  In the
#I best case, users should simply be able to send mail to "user@domain".
#I If this doesn't work, try "user%domain@gateway" where "gateway" is a 
#I regional Bitnet-Internet gateway site.  Finally, if neither of these
#I works, you may have to try hand-coding an SMTP envelope for your mail.
#I If you have questions concerning this rather terse note, please try
#I contacting your local postmaster or system administrator first before
#I you send me mail -- John Chew <poslfit@gpu.utcs.utoronto.ca>

#F compuserve
#T fax
#R +1 415 555 1212
#I send to "FAX 14155551212" (only to U.S.A.)

#F compuserve
#T internet
#R user@domain
#I send to ">INTERNET:user@domain"

#F compuserve
#T mci
#R 123-4567
#I send to ">MCIMAIL:123-4567"

#F connect
#T internet
#R user@domain
#I send to CONNECT id "DASNET"
#I first line of message: "\"user@domain\"@DASNET"

#F easynet
#T bitnet
#R user@site
#C DECWRL::ADMIN
#I from VMS use NMAIL to send to "nm%DECWRL::\"user@site.bitnet\""
#I from Ultrix
#I   send to "user@site.bitnet" or if that fails
#I     (via IP) send to "\"user%site.bitnet\"@decwrl.dec.com"
#I     (via DECNET) send to "DECWRL::\"user@site.bitnet\""

#F easynet
#T fidonet
#R john smith at 1:2/3.4
#C DECWRL::ADMIN
#I from VMS use NMAIL to send to 
#I   "nm%DECWRL::\"john.smith@p4.f3.n2.z1.fidonet.org\""
#I from Ultrix
#I   send to "john.smith@p4.f3.n2.z1.fidonet.org" or if that fails
#I     (via IP) send to "\"john.smith%p4.f3.n2.z1.fidonet.org\"@decwrl.dec.com"
#I     (via DECNET) send to "DECWRL::\"john.smith@p4.f3.n2.z1.fidonet.org\""

#F easynet
#T internet
#R user@domain
#C DECWRL::ADMIN
#I from VMS use NMAIL to send to "nm%DECWRL::\"user@domain\""
#I from Ultrix
#I   send to "user@domain" or if that fails
#I     (via IP) send to "\"user%domain\"@decwrl.dec.com"
#I     (via DECNET) send to "DECWRL::\"user@domain\""

#F envoy
#T internet
#R user@domain
#C ICS.TEST or ICS.BOARD
#I send to "[RFC-822=\"user(a)domain\"]INTERNET/TELEMAIL/US
#I for special characters, use @=(a), !=(b), _=(u), any=(three octal digits)

#F fidonet
#T internet
#R user@domain
#I send to "uucp" at nearest gateway site
#I first line of message: "To: user@domain"

#F geonet
#T internet
#R user@domain
#I send to "DASNET"
#I subject line: "user@domain!subject"

#F internet
#T applelink
#R user
#I send to "user@applelink.apple.com"

#F internet
#T attmail
#R user@attmail.com
#C AT&T Mail Customer Assisistance Center, 1-800-624-5672 (1-800-MAIL-672)
#I For an address "attmail!user", send to "user@attmail.com"

#F internet
#T bitnet
#R user@site
#I send to "user%site.bitnet@gateway" where "gateway" is a gateway host that
#I   is on both the internet and bitnet.  Some examples of gateways are:
#I   cunyvm.cuny.edu mitvma.mit.edu.  Check first to see what local policies
#I   are concerning inter-network forwarding.

#F internet
#T bix
#R user
#I send to "user@dcibix.das.net"

#F internet
#T bmug
#R John Smith
#I send to "John.Smith@bmug.fidonet.org"

#F internet
#T compuserve
#R 71234,567
#I send to "71234.567@compuserve.com"
#I   note: Compuserve account IDs are pairs of octal numbers.  Ordinary
#I     consumer CIS user IDs begin with a `7' as shown.

#F internet
#T connect
#R NAME
#I send to "NAME@dcjcon.das.net"

#F internet
#T easynet
#R HOST::USER
#C admin@decwrl.dec.com
#I send to "user@host.enet.dec.com" or "user%host.enet@decwrl.dec.com"

#F internet
#T easynet
#R John Smith @ABC
#C admin@decwrl.dec.com
#I send to "John.Smith@ABC.MTS.DEC.COM"
#I (This syntax is for All-In-1 users.)

#F internet
#T envoy
#R John Smith (ID=userid)
#C /C=CA/ADMD=TELECOM.CANADA/ID=ICS.TEST/S=TEST_GROUP/@nasamail.nasa.gov
#C   for second method only
#I send to "uunet.uu.net!att!attmail!mhs!envoy!userid"
#I   or to "/C=CA/ADMD=TELECOM.CANADA/DD.ID=userid/PN=John_Smith/@Sprint.COM"

#F internet
#T fidonet
#R john smith at 1:2/3.4
#I send to "john.smith@p4.f3.n2.z1.fidonet.org" 

#F internet
#T geonet
#R user at host
#I send to "user:host@map.das.net"
#I American host is geo4, European host is geo1.

#F internet
#T mci
#R John Smith (123-4567)
#I send to "1234567@mcimail.com"
#I or send to "JSMITH@mcimail.com" if "JSMITH" is unique
#I or send to "John_Smith@mcimail.com" if "John Smith" is unique - note the
#I    underscore!
#I or send to "John_Smith/1234567@mcimail.com" if "John Smith" is NOT unique

#F internet
#T mfenet
#R user@mfenode
#I send to "user%mfenode.mfenet@nmfecc.arpa"

#F internet
#T nasamail
#R user
#C <postmaster@ames.arc.nasa.gov>
#I send to "user@nasamail.nasa.gov"

#F internet
#T peacenet
#R user
#C <support%cdp@arisia.xerox.com>
#I send to "user%cdp@arisia.xerox.com"

#F internet
#T signet (through FidoNet)
#R John Smith at 27:2/3.4
#I Send the message to John.Smith@f527.n2.z2.fidonet.org (that is the
#I FidoNet to SigNet gateway).
#I The first line of the message should be:
#I    @DOMAIN SIGNet 27:2/3.4 FidoNet 2:2/527
#I For other persons at the signet, replace John.Smith and 27:2/3.4 by
#I the proper person/node adrress.
#I The sysop of the gateway can be reached at: 
#I    andreas.levenitschnig@f527.n2.z2.fidonet.org

#F internet
#T sinet
#R node::user or node1::node::user
#I send to "user@node.SINet.SLB.COM" or "user%node@node1.SINet.SLB.COM"

#F internet
#T span
#R user@host
#C <NETMGR@nssdca.gsfc.nasa.gov>
#I send to "user@host.span.NASA.gov"
#I   or to "user%host.span@ames.arc.nasa.gov"

#F internet
#T sprintmail
#R [userid "John Smith"/organization]system/country
#I send to "/C=country/ADMD=system/O=organization/PN=John_Smith/DD.ID=userid/@Sprint.COM"

#F internet
#T thenet
#R user@host
#I send to "user%host.decnet@utadnx.cc.utexas.edu"

#F internet
#T uninet (South Africa) (Through FidoNet)
#R user.node
#I Send the message to user.node@f4.n494.z5.fidonet.org
#I A list of nodes in the uninet can be obtained by sending a message
#I with SEND UNINODE

#F mci
#T internet
#R John Smith <user@domain>
#I at the "To:" prompt type "John Smith (EMS)"
#I at the "EMS:" prompt type "internet"
#I at the "Mbx:" prompt type "user@domain"

#F nasamail
#T internet
#R user@domain
#I at the "To:" prompt type "POSTMAN"
#I at the "Subject:" prompt enter the subject of your message
#I at the "Text:" prompt, i.e. as the first line of your message,
#I    enter "To: user@domain"

#F sinet
#T internet
#R user@domain
#I send to "M_MAILNOW::M_INTERNET::\"user@domain\""
#I      or "M_MAILNOW::M_INTERNET::domain::user"

#F span
#T internet
#R user@domain
#C NETMGR@NSSDCA
#I send to "AMES::\"user@domain\""

#F sprintmail
#T internet
#R user@domain
#I send to "[RFC-822=user(a)domain @GATEWAY]INTERNET/TELEMAIL/US"

#F thenet
#T internet
#R user@domain
#I send to UTADNX::WINS%" user@domain "

END

------------------------------------------------------------------------------


As a supplement, here are networks known *not* to have email gateways.

Network             Comments
-------             ---------------------------------------------------
American Online     Masato Ogawa (ogawa@sm.sony.co.jp) confirms
                    that there is no gateway.

Dialog              mcmahan@netcom.UUCP (Dave Mc Mahan) reports that
                    nobody responded to his query in October 1990.

GEnie               No gateway yet, but Bill Louden, the General Manager of
                    GEnie, has stated publically that they are currently doing
                    research into the feasibility of a gateway.  Trust me,
                    if such a gateway is set up, you'll hear about it.

                    By the way, the machine genie.com is a red herring.

HandsNet            oze3@quads.uchicago.edu (J. Daniel Ozeran) reports
                    that nobody responded to his query in January 1991.

Midas Internation headquarters in Chicago
                    IO00393@MAINE.BITNET (Pete) reports that nobody
                    responded to his query in January 1991.

Nifty-Serve         a Japanese BBS
                    suzuki@sai.vtt.fi (Makoto Suzuki) contacted the
                    system operators and confirmed that there is no gateway.

Prodigy             by IBM and Sears
                    censors email
                    charges the sender of the mail message
                    Censorship details available from comp.risks issue 10.46.

Robert Halloran (rkh@mtune.ATT.COM) notes:

[GEnie, Prodigy, and American Online] have all apparently been approached more
than once about gateways, and have refused to let all that un-screened (and
FREE!) mail onto their respective networks....

--

Ajay Shekhawat           <Dept. of Comp. Sci., SUNY@Buffalo, Amherst, NY 14260>
ajay@cs.Buffalo.EDU || ajay@sunybcs.BITNET || ajay@sunybcs.UUCP || 716.636.3027

raymond@math.berkeley.edu (Raymond Chen) (03/23/91)

It would be nice if Mr. Shekhawat could keep my name attached to Part II
of the referenced article.  I've spent over a year collecting that
information; all I ask is a little recognition (sob).

(That `Part II' is Chapter Two of the file
math.princeton.edu:pub/rjc/misc/gateway.Z.)

Here's the most recent version of same:

Network             Comments (and userids of people who asked about it
                              and didn't post summaries)
-------             ---------------------------------------------------
American Online     Masato Ogawa (ogawa@sm.sony.co.jp) confirms
                    that there is no gateway.

British Telecom     rbatt@adam.adelaide.edu.au (R Batt) reports that
Gold                BT is a member of DialCom (qv).

DialCom             The gateway was shut down in March 1990 for financial
                    reasons.  Individual customers may have established
                    private relays through the Commercial Mail Relay (CMR).
                    Information available on the CMR is available from
                        Intermail-Request@Intermail.ISI.EDU

Dialog              mcmahan@netcom.UUCP (Dave Mc Mahan) reports that
                    nobody responded to his query in October 1990.

Easylink            a Western Union service
                    bruceh@CV.HP.COM (Bruce Hauge) reports that as of March
                    1991 there is no gateway yet, but they're working on it.

ECONET              rchen@draco.rutgers.edu reports that you send mail to
                    cdp!user@labrea.stanford.edu

Eurokom             christ@issun3.stc.nl (Brian Christiansen) reports that
                    nobody responded to his query in February 1991.

Fidelity Investments ea47916@uxa.cso.uiuc.edu (Eric Adams) reports that
(Dallas)            nobody responded to his query in February 1991.

GEnie               No gateway yet, but Bill Louden, the General Manager of
                    GEnie, has stated publically that they are currently doing
                    research into the feasibility of a gateway.  Trust me,
                    if such a gateway is set up, you'll hear about it.

                    By the way, the machine genie.com is a red herring.

GoldNet             chaim@eniac.seas.upenn.edu (Chaim Dworkin) reports that
                    GoldNet is part of DialCom (qv).

HandsNet            oze3@quads.uchicago.edu (J. Daniel Ozeran) reports
                    that nobody responded to his query in January 1991.

Midas Internation headquarters in Chicago
                    IO00393@MAINE.BITNET (Pete) reports that nobody
                    responded to his querh in January 1991.

Nifty-Serve         a Japanese BBS
                    suzuki@sai.vtt.fi (Makoto Suzuki) contacted the
                    system operators and confirmed that there is no gateway.

OMNET               Craig E. Ward (cew@isi.edu) explains:

Go either through Sprint Internet relay, Sprint.COM, or through the Commercial
Mail Relay (CMR) at Intermail.ISI.EDU.

Through the CMR, you can send mail to OMNET users with this format:

           "[omnet.user/OMNET]MAIL/USA%TELEMAIL"@Intermail.ISI.EDU

Users on OMNET will need to use an embedded header, i.e. in the body of the
message text (almost as ugly as X.400, but not quite) in a message to
"[INTERMAIL/USCISI]SM66/USA" to get mail back to you:

        Forward: Internet
        To: Gumley_LE@cc.curtin.edu.au
        <Blank-Line>

You can get more information about the Commercial Mail Relay from:

                     Intermail-Request@Intermail.ISI.EDU

Paranet             vac163w@monu6.cc.monash.edu.au (vacation) 4 Dec 90
                    No summary has yet been posted, and personal email
                    to this person is not answered.

PC-Relay            davidl@cix.compulink.co.uk (Dave Lambert) 21 Feb 91
                    No summary has yet been posted, and personal email
                    to Mr Lambert is not answered.

Prodigy             by IBM and Sears
                    censors email
                    charges the sender of the mail message
                    Censorship details available from comp.risks issue 10.46.

PROFS (general)     PROFS is not a network.  It is an electronic office system
                    that has electronic mail as one of its components.  Many
                    companies purchase it from IBM and install it locally.

PROFS (IBM)         gt5116b@prism.gatech.EDU (Gaby Turek)
                    reports that you send to username@vmmachine.iinus1.ibm.com,
                    but the recipient must first have registered for internet
                    access.

QUICK-COMM          GE Information Services E-Mail
                    pegah@pleiades.cps.msu.edu (Mahmoud Pegah) reports
                    that as of February 1991 there is no gateway, though
                    one is under development.

SABRE               American Airlines' in-house reservation network.
                    savel@hoss.unl.edu (Bharat P. Savel) reports that
                    it has no gateway to any other network, and they
                    intend to keep it that way.

SAPONET             the South African Post Office's X.25 network (#6550)
                    s873561@minyos.xx.rmit.oz.au (Michael Barnett) reports
                    that the alleged gateway via
                        user%sapo.net.com@ames.arc.nasa.gov
                    simply bounces.  There seems to be some way to sneak
                    in via FidoNet; send mail to
                        MAILSRV.RURES@f4.n494.z5.fidonet.org
                    containing the message `SEND UNINODE' for details.
                    The postmaster for Saponet appears to be
                        Barrett.UNDEE@f4.n494.z5.fidonet.org

Telemail            stevenst@infonode.ingr.com (Todd Stevens) 20 Feb 91
Use the gateway at sprint.com   This requires knowledge of the recipient's
X.400 address on Telenet (now Sprintnet).  Your SMTP address will look like
this:

  smtp%"/dd.un=username/admd=telemail/o=gte/c=us/@sprint.com"

the username will be the recipient's username on the system and o will be
the organization.

VNET (IBM)          kkrueger@zeus.unomaha.edu (Kurt Krueger) 16 Feb 91

Whole Earth 'Lectronic Link (WELL)
                    basiji@milton.u.washington.edu (David Basiji) reports that
                    you send mail to username@well.sf.ca.usa

ajay@cs.Buffalo.EDU ( Ajay Shekhawat ) (03/23/91)

 /*** In article #5314, Raymond Chen writes... ***/
...It would be nice if Mr. Shekhawat could keep my name attached to Part II
...of the referenced article.  I've spent over a year collecting that
...information; all I ask is a little recognition (sob).

Whoops, I'm sorry:  It was sent to me by a bunch of people, and I
(mistakenly, as can be seen) assumed it was one of those things
that float around the net, with no definite origin. 

Sorry about that: of course, now that you've sent a (more) complete
list, I'll attach it with due credits. 

Ajay..

paul@frcs.UUCP (Paul Nash) (03/26/91)

Thus spake raymond@math.berkeley.edu (Raymond Chen):
>
> SAPONET             the South African Post Office's X.25 network (#6550)
>                     s873561@minyos.xx.rmit.oz.au (Michael Barnett) reports
>                     that the alleged gateway via
>                         user%sapo.net.com@ames.arc.nasa.gov
>                     simply bounces.  There seems to be some way to sneak
>                     in via FidoNet; send mail to
>                         MAILSRV.RURES@f4.n494.z5.fidonet.org
>                     containing the message `SEND UNINODE' for details.
>                     The postmaster for Saponet appears to be
>                         Barrett.UNDEE@f4.n494.z5.fidonet.org

The first line is correct, thereafter, I fear, the figment of Mr Chen's
imagination.  Yes, SAPONET is the SA Post Office's X.25 network.  It
is, however, merely a physical network, on which subscribers can rent
X.25 ports, PVCs, SVCs, attatch PADs, etc.  There is _NO_ mail facility
or any other type of Value Added Service.

I have been able to connect from Saponet to Tymnet, so I assume that
a reverse connection is possible, but I do not know what the NUA would
be to connect in this way.

South Africa _does_ have at least two networks, apart from the Fidonet
network here.  One is Uninet-ZA, which links the universities.  The
Uninet office also administer the .ZA domain.  You might wish to contact
VICSHAW@FRD.AC.ZA, or barrett@daisy.ee.und.ac.za or ccfj@quagga.ru.ac.za
for more information.  Uninet-ZA runs (mostly) on TCP/IP over leased
lines, with a few IBM hosts running RSCS, and Vaxen running Decnet.

There is also a UUCP-based network called Sanet, which includes a 
portion of Uninet-ZA.  As with the UUCP network in the states,
there is no postmaster for the net as a whole.  To get mail to
someone on a non-academic machine in SA, try using a bang-path of
``...!ddsw1!olsa99!machine!user'', or ``user%machine%olsa99@ddsw1.mcs.com''


 ---=---=---=---=---=---=---=---=---=---=---=---=---=---=---=---=---=---
Paul Nash				   Free Range Computer Systems cc
paul@frcs.UUCP				      ...!uunet!m2xenix!frcs!paul

barrett@Daisy.EE.UND.AC.ZA (Alan P. Barrett) (03/27/91)

In article <427@frcs.UUCP>, paul@frcs.UUCP (Paul Nash) writes:
> Thus spake raymond@math.berkeley.edu (Raymond Chen):
> >
> > SAPONET             the South African Post Office's X.25 network (#6550)
> >                     s873561@minyos.xx.rmit.oz.au (Michael Barnett) reports
> >                     that the alleged gateway via
> >                         user%sapo.net.com@ames.arc.nasa.gov
> >                     simply bounces.  There seems to be some way to sneak
> >                     in via FidoNet; send mail to
> >                         MAILSRV.RURES@f4.n494.z5.fidonet.org
> >                     containing the message `SEND UNINODE' for details.
> >                     The postmaster for Saponet appears to be
> >                         Barrett.UNDEE@f4.n494.z5.fidonet.org

Thanks for bringing this misinformation to my attention, Paul.

Yes, Saponet is net number 6550 in the international X.25 world.

As Paul says, there is no mail service on Saponet, and no reason why
there should be a gateway at Ames.  Saponet is just an X.25 network,
linked to other X.25 networks around the world.  Of course, people are
free to use Saponet as a transport for electronic mail, with their own
protocols above the X.25 layer, and many people do so.

Sites belonging to UNINET-ZA (the South African academic and research
network) were reachable through a Fidonet gateway for some time before
the ZA top level domain was registered in November 1990, but the Fidonet
route to is deprecated now, and will go away some time.  UNINET-ZA has
absolutely nothing to do with SAPONET.  Further information about sites
belonging to UNINET-ZA is available from UNINET@FRD.AC.ZA.

I am certainly not the postmaster for SAPONET.  There is no postmaster
for SAPONET.

> I have been able to connect from Saponet to Tymnet, so I assume that
> a reverse connection is possible, but I do not know what the NUA would
> be to connect in this way.

It would be xxx6550yyyyyyyyzz, where xxx is whatever is needed on the
originating network to tell it you want to make a call to an address
that is on a different network (two likely values for xxx are either the
null string or the digit zero, but I think that other values are also
permitted by CCITT rules, and the choice will vary from one net to
another); yyyyyyyy is the SAPONET address; and zz is the subaddress (if
any).

--apb
Alan Barrett, Dept. of Electronic Eng., Univ. of Natal, Durban, South Africa
Internet: barrett@ee.und.ac.za           UUCP: m2xenix!quagga!undeed!barrett

ajay@CS.BUFFALO.EDU (Ajay Shekhawat) (04/05/91)

This list is current as of 04 April 1991, I think (but then,
one never knows: things change so rapidly).

Would someone like to "officially" maintain this list?  
I'll strapped for time in the coming months...

Ajay.

==============================================================================

---------
Contents:
	I : The Internetworking Guide
	II: Networks NOT(yet) reachable from Internet.
--------

Inter-Network Mail Guide - Copyright 1990 by John J. Chew
  $Header: netmail,v 1.12 90/07/06 20:38:28 john Exp $

COPYRIGHT NOTICE

This document is Copyright 1990 by John J. Chew.  All rights reserved.
Permission for non-commercial distribution is hereby granted, provided
that this file is distributed intact, including this copyright notice
and the version information above.  Permission for commercial distribution
can be obtained by contacting the author as described below.

INTRODUCTION

This file documents methods of sending mail from one network to another.
It represents the aggregate knowledge of the readers of comp.mail.misc
and many contributors elsewhere.  If you know of any corrections or
additions to this file, please read the file format documentation below
and then mail to me: John J. Chew <poslfit@gpu.utcs.utoronto.ca>.  If
you do not have access to electronic mail (which makes me wonder about
the nature of your interest in the subject, but there does seem to be
a small such population out there) you can call me during the month of
July at +1 416 979 7166 between 11:00 and 24:00 EDT (UTC-4h) and most
likely talk to my answering machine (:-).

DISTRIBUTION

(news) This list is posted monthly to Usenet newsgroups comp.mail.misc and
  news.newusers.questions.  
(mail) I maintain a growing list of subscribers who receive each monthly 
  issue by electronic mail, and recommend this to anyone planning to 
  redistribute the list on a regular basis.  
(FTP) Internet users can fetch this guide by anonymous FTP as ~ftp/pub/docs/
  internetwork-mail-guide on Ra.MsState.Edu (130.18.80.10 or 130.18.96.37)
  [Courtesy of Frank W. Peters]
(Listserv) Bitnet users can fetch this guide from the Listserv at UNMVM.
  Send mail to LISTSERV@UNMVM with blank subject and body consisting of
  the line "GET NETWORK GUIDE".  [Courtesy of Art St. George]

HOW TO USE THIS GUIDE

Each entry in this file describes how to get from one network to another.
To keep this file at a reasonable size, methods that can be generated by
transitivity (A->B and B->C gives A->B->C) are omitted.  Entries are sorted
first by source network and then by destination network.  This is what a
typical entry looks like:

  #F mynet
  #T yournet
  #R youraddress
  #C contact address if any
  #I send to "youraddress@thegateway"

For parsing purposes, entries are separated by at least one blank line,
and each line of an entry begins with a `#' followed by a letter.  Lines
beginning with `# ' are comments and need not be parsed.  Lines which do
not start with a `#' at all should be ignored as they are probably mail
or news headers.

#F (from) and #T (to) lines specify source and destination networks.
If you're sending me information about a new network, please give me
a brief description of the network so that I can add it to the list
below.  The abbreviated network names used in #F and #T lines should
consist only of the characters a-z, 0-9 and `-' unless someone can
make a very convincing case for their favourite pi character.

These are the currently known networks with abbreviated names:

  applelink     AppleLink (Apple Computer, Inc.'s in-house network)
  attmail	AT&T Mail,AT&T's commercial e-mail service.
  bitnet        international academic network
  bix           Byte Information eXchange: Byte magazine's commercial BBS
  bmug          Berkeley Macintosh Users Group
  compuserve    commercial time-sharing service
  connect       Connect Professional Information Network (commercial)
  easynet       Easynet (DEC's in-house mail system)
  envoy	  	Envoy-100 (Canadian commercial mail service)
  fax           Facsimile document transmission
  fidonet       PC-based BBS network
  geonet        GeoNet Mailbox Systems (commercial)
  internet      the Internet
  mci           MCI's commercial electronic mail service
  mfenet        Magnetic Fusion Energy Network
  nasamail      NASA internal electronic mail
  peacenet      non-profit mail service
  sinet         Schlumberger Information NETwork
  span          Space Physics Analysis Network (includes HEPnet)
  sprintmail    Sprint's commercial mail service (formerly Telemail)
  thenet        Texas Higher Education Network

#R (recipient) gives an example of an address on the destination network, 
to make it clear in subsequent lines what text requires subsitution.

#C (contact) gives an address for inquiries concerning the gateway,
expressed as an address reachable from the source (#F) network.
Presumably, if you can't get the gateway to work at all, then knowing
an unreachable address on another network will not be of great help.

#I (instructions) lines, of which there may be several, give verbal
instructions to a user of the source network to let them send mail
to a user on the destination network.  Text that needs to be typed
will appear in double quotes, with C-style escapes if necessary.

/* Additions */
/*
   Given below are the additions made, along with the sender's address:

 Network	Description 					Sender
	    
 UNINet		Network in Rep. of SA		Erik Proper  (erik@cs.kun.nl)
 SIGNet		Network in Rep. of SA		Erik Proper  (erik@cs.kun.nl)
 EcoNet		Similar to PeaceNet 		Brian Coan   (brian@igc.org)
 gsfcmail 	NASA Goddard Space Flight Center mail system
					DWEISSMAN@amarna.gsfc.nasa.gov

_Ajay
*/

#F applelink
#T internet
#R user@domain
#I send to "user@domain@internet#"
#I   domain can be be of the form "site.bitnet", address must be <35 characters

#F AT&T Mail (attmail)
#T internet
#R internet!domain!user
#C AT&T Mail Customer Assisistance Center, 1-800-624-5672 (1-800-MAIL-672)
#I For an address "user@domain", send to "internet!domain!user". 

#F bitnet
#T internet
#R user@domain
#I Methods for sending mail from Bitnet to the Internet vary depending on
#I what mail software is running at the Bitnet site in question.  In the
#I best case, users should simply be able to send mail to "user@domain".
#I If this doesn't work, try "user%domain@gateway" where "gateway" is a 
#I regional Bitnet-Internet gateway site.  Finally, if neither of these
#I works, you may have to try hand-coding an SMTP envelope for your mail.
#I If you have questions concerning this rather terse note, please try
#I contacting your local postmaster or system administrator first before
#I you send me mail -- John Chew <poslfit@gpu.utcs.utoronto.ca>

#F compuserve
#T fax
#R +1 415 555 1212
#I send to "FAX 14155551212" (only to U.S.A.)

#F compuserve
#T internet
#R user@domain
#I send to ">INTERNET:user@domain"

#F compuserve
#T mci
#R 123-4567
#I send to ">MCIMAIL:123-4567"

#F connect
#T internet
#R user@domain
#I send to CONNECT id "DASNET"
#I first line of message: "\"user@domain\"@DASNET"

#F easynet
#T bitnet
#R user@site
#C DECWRL::ADMIN
#I from VMS use NMAIL to send to "nm%DECWRL::\"user@site.bitnet\""
#I from Ultrix
#I   send to "user@site.bitnet" or if that fails
#I     (via IP) send to "\"user%site.bitnet\"@decwrl.dec.com"
#I     (via DECNET) send to "DECWRL::\"user@site.bitnet\""

#F easynet
#T fidonet
#R john smith at 1:2/3.4
#C DECWRL::ADMIN
#I from VMS use NMAIL to send to 
#I   "nm%DECWRL::\"john.smith@p4.f3.n2.z1.fidonet.org\""
#I from Ultrix
#I   send to "john.smith@p4.f3.n2.z1.fidonet.org" or if that fails
#I     (via IP) send to "\"john.smith%p4.f3.n2.z1.fidonet.org\"@decwrl.dec.com"
#I     (via DECNET) send to "DECWRL::\"john.smith@p4.f3.n2.z1.fidonet.org\""

#F easynet
#T internet
#R user@domain
#C DECWRL::ADMIN
#I from VMS use NMAIL to send to "nm%DECWRL::\"user@domain\""
#I from Ultrix
#I   send to "user@domain" or if that fails
#I     (via IP) send to "\"user%domain\"@decwrl.dec.com"
#I     (via DECNET) send to "DECWRL::\"user@domain\""

#F envoy
#T internet
#R user@domain
#C ICS.TEST or ICS.BOARD
#I send to "[RFC-822=\"user(a)domain\"]INTERNET/TELEMAIL/US
#I for special characters, use @=(a), !=(b), _=(u), any=(three octal digits)

#F fidonet
#T internet
#R user@domain
#I send to "uucp" at nearest gateway site
#I first line of message: "To: user@domain"

#F geonet
#T internet
#R user@domain
#I send to "DASNET"
#I subject line: "user@domain!subject"

#F GSFCMail
#T internet
#R user@domain
#C cust.svc
#I at the "To:" prompt type "POSTMAN"
#I at the "Subject:" prompt enter the subject of your message
#I at the "Text:" prompt, i.e. as the first line of your message,
#I    enter "To: user@domain"
#I or use same directions as sprintmail to internet

#F GSFCMail
#T NASAMAIL
#R userid
#C cust.svc
#I send to "(C:USA,ADMD:TELEMAIL,P:NASAMAIL,O:NASA,UN:userid)"

#F GSFCMail
#T span (now nsi-decnet)
#R host::user
#C cust.svc
#I at the "To:" prompt enter "POSTMAN"
#I at the "Subject:" prompt enter the subject of your message
#I at the "Text:" prompt, i.e. as the first line of your message,
#I    enter "To: user@host.SPAN.NASA.GOV"
#I or use GSFCCNE gateway and send to
#I    (C:USA,ADMD:TELEMAIL,P:GSFCCNE,O:SPAN,OU:host,SN:user)

#F GSFCMail
#T sprintmail
#R (C:USA,ADMD:TELEMAIL,O:organization,UN:userid)
#C cust.svc
#I for public networks send to 
#I     "(C:USA,ADMD:TELEMAIL,O:organization,UN:userid)"
#I for private networks send to
#I     "(C:USA,ADMD:TELEMAIL,PRMD:private_net,O:organization,UN:userid)"
#F internet
#T applelink
#R user
#I send to "user@applelink.apple.com"

#F internet
#T attmail
#R user@attmail.com
#C AT&T Mail Customer Assisistance Center, 1-800-624-5672 (1-800-MAIL-672)
#I For an address "attmail!user", send to "user@attmail.com"

#F internet
#T bitnet
#R user@site
#I send to "user%site.bitnet@gateway" where "gateway" is a gateway host that
#I   is on both the internet and bitnet.  Some examples of gateways are:
#I   cunyvm.cuny.edu mitvma.mit.edu.  Check first to see what local policies
#I   are concerning inter-network forwarding.

#F internet
#T bix
#R user
#I send to "user@dcibix.das.net"

#F internet
#T bmug
#R John Smith
#I send to "John.Smith@bmug.fidonet.org"

#F internet
#T compuserve
#R 71234,567
#I send to "71234.567@compuserve.com"
#I   note: Compuserve account IDs are pairs of octal numbers.  Ordinary
#I     consumer CIS user IDs begin with a `7' as shown.

#F internet
#T connect
#R NAME
#I send to "NAME@dcjcon.das.net"

#F internet
#T easynet
#R HOST::USER
#C admin@decwrl.dec.com
#I send to "user@host.enet.dec.com" or "user%host.enet@decwrl.dec.com"

#F internet
#T easynet
#R John Smith @ABC
#C admin@decwrl.dec.com
#I send to "John.Smith@ABC.MTS.DEC.COM"
#I (This syntax is for All-In-1 users.)

#F internet
#T econet
#R user
#C <support@igc.org>
#I send to "user@igc.org"


#F internet
#T envoy
#R userid
#C POSTMASTER@SPRINT.COM for second method only
#I send to "att!attmail!mhs!envoy!userid@UUNET.UU.NET"
#I or through US Sprint's X.400 gateway to
#I    "/C=CA/ADMD=TELECOM.CANADA/O=ENVOY/DD.ID=userid/@SPRINT.COM"

#F internet
#T fidonet
#R john smith at 1:2/3.4
#I send to "john.smith@p4.f3.n2.z1.fidonet.org" 

#F internet
#T geonet
#R user at host
#I send to "user:host@map.das.net"
#I American host is geo4, European host is geo1.

#F internet
#T GSFCMail
#R userid
#C postmaster@ames.arc.nasa.gov
#I send to "user@GSFCMAIL.NASA.GOV"

#F internet
#T mci
#R John Smith (123-4567)
#I send to "1234567@mcimail.com"
#I or send to "JSMITH@mcimail.com" if "JSMITH" is unique
#I or send to "John_Smith@mcimail.com" if "John Smith" is unique - note the
#I    underscore!
#I or send to "John_Smith/1234567@mcimail.com" if "John Smith" is NOT unique

#F internet
#T mfenet
#R user@mfenode
#I send to "user%mfenode.mfenet@nmfecc.arpa"

#F internet
#T nasamail
#R user
#C <postmaster@ames.arc.nasa.gov>
#I send to "user@nasamail.nasa.gov"

#F internet
#T peacenet
#R user
#C <support@igc.org>
#I send to "user@igc.org"

#F internet
#T signet (through FidoNet)
#R John Smith at 27:2/3.4
#I Send the message to John.Smith@f527.n2.z2.fidonet.org (that is the
#I FidoNet to SigNet gateway).
#I The first line of the message should be:
#I    @DOMAIN SIGNet 27:2/3.4 FidoNet 2:2/527
#I For other persons at the signet, replace John.Smith and 27:2/3.4 by
#I the proper person/node adrress.
#I The sysop of the gateway can be reached at: 
#I    andreas.levenitschnig@f527.n2.z2.fidonet.org

#F internet
#T sinet
#R node::user or node1::node::user
#I send to "user@node.SINet.SLB.COM" or "user%node@node1.SINet.SLB.COM"


#F internet
#T span (now nsi-decnet)
#R host::user
#C netmgr@nssdca.gsfc.nasa.gov
#I send to "user@host.SPAN.NASA.GOV"

#F internet
#T sprintmail
#R (C:USA,ADMD:TELEMAIL,O:organization,UN:userid)
#C postmaster@sprint.com
#I for public networks send to
#I     "/C=US/ADMD=TELEMAIL/O=organization/DD.UN=userid/@SPRINT.COM"
#I or if you know the recipients registered full name
#I     "/C=US/ADMD=TELEMAIL/O=organization/PN=firstname.lastname/@SPRINT.COM"
#I for private networks send to
#I     "/C=USA/ADMD=TELEMAIL/PRMD=private_net/O=organization/DD.UN=userid/@SPRINT.COM"

#F internet
#T thenet
#R user@host
#I send to "user%host.decnet@utadnx.cc.utexas.edu"

#F internet
#T uninet (South Africa) (Through FidoNet)
#R user.node
#I Send the message to user.node@f4.n494.z5.fidonet.org
#I A list of nodes in the uninet can be obtained by sending a message
#I with SEND UNINODE

#F mci
#T internet
#R John Smith <user@domain>
#I at the "To:" prompt type "John Smith (EMS)"
#I at the "EMS:" prompt type "internet"
#I at the "Mbx:" prompt type "user@domain"

#F nasamail
#T internet
#R user@domain
#I at the "To:" prompt type "POSTMAN"
#I at the "Subject:" prompt enter the subject of your message
#I at the "Text:" prompt, i.e. as the first line of your message,
#I    enter "To: user@domain"

#F sinet
#T internet
#R user@domain
#I send to "M_MAILNOW::M_INTERNET::\"user@domain\""
#I      or "M_MAILNOW::M_INTERNET::domain::user"

#F span (now nsi-decnet)
#T GSFCMail
#R userid
#C mssdca::netmgr
#I send to "AMES::\"user@GSFCMAIL.NASA.GOV"\"

#F span
#T internet
#R user@domain
#C nssdca::netmgr
#I send to "AMES::\"user@domain\""
#F sprintmail
#T internet
#R user@domain
#C (c:usa,admd:telemail,o:telenet.tele,fn:technical,sn:support,i:t)
#I send to "(C:USA,ADMD:TELEMAIL,PRMD:INTERNET,ID:<user(a)domain>)"

#F thenet
#T internet
#R user@domain
#I send to UTADNX::WINS%" user@domain "

END

------------------------------------------------------------------------------
PART - II

NETWORKS KNOWN *NOT* TO HAVE ACCESS FROM INTERNET

Compiled by Raymond Chen <raymond@math.berkeley.edu> . 

Network             Comments (and userids of people who asked about it
                              and didn't post summaries)
-------             ---------------------------------------------------
American Online     Masato Ogawa (ogawa@sm.sony.co.jp) confirms
                    that there is no gateway.

British Telecom     rbatt@adam.adelaide.edu.au (R Batt) reports that
Gold                BT is a member of DialCom (qv).

DialCom             The gateway was shut down in March 1990 for financial
                    reasons.  Individual customers may have established
                    private relays through the Commercial Mail Relay (CMR).
                    Information available on the CMR is available from
                        Intermail-Request@Intermail.ISI.EDU

Dialog              mcmahan@netcom.UUCP (Dave Mc Mahan) reports that
                    nobody responded to his query in October 1990.

Easylink            a Western Union service
                    bruceh@CV.HP.COM (Bruce Hauge) reports that as of March
                    1991 there is no gateway yet, but they're working on it.

Eurokom             christ@issun3.stc.nl (Brian Christiansen) reports that
                    nobody responded to his query in February 1991.

Fidelity Investments ea47916@uxa.cso.uiuc.edu (Eric Adams) reports that
(Dallas)            nobody responded to his query in February 1991.

GEnie               No gateway yet, but Bill Louden, the General Manager of
                    GEnie, has stated publically that they are currently doing
                    research into the feasibility of a gateway.  Trust me,
                    if such a gateway is set up, you'll hear about it.

                    By the way, the machine genie.com is a red herring.

GoldNet             chaim@eniac.seas.upenn.edu (Chaim Dworkin) reports that
                    GoldNet is part of DialCom (qv).

HandsNet            oze3@quads.uchicago.edu (J. Daniel Ozeran) reports
                    that nobody responded to his query in January 1991.

Midas Internation headquarters in Chicago
                    IO00393@MAINE.BITNET (Pete) reports that nobody
                    responded to his querh in January 1991.

Nifty-Serve         a Japanese BBS
                    suzuki@sai.vtt.fi (Makoto Suzuki) contacted the
                    system operators and confirmed that there is no gateway.

OMNET               Craig E. Ward (cew@isi.edu) explains:

Go either through Sprint Internet relay, Sprint.COM, or through the Commercial
Mail Relay (CMR) at Intermail.ISI.EDU.

Through the CMR, you can send mail to OMNET users with this format:

           "[omnet.user/OMNET]MAIL/USA%TELEMAIL"@Intermail.ISI.EDU

Users on OMNET will need to use an embedded header, i.e. in the body of the
message text (almost as ugly as X.400, but not quite) in a message to
"[INTERMAIL/USCISI]SM66/USA" to get mail back to you:

        Forward: Internet
        To: Gumley_LE@cc.curtin.edu.au
        <Blank-Line>

You can get more information about the Commercial Mail Relay from:

                     Intermail-Request@Intermail.ISI.EDU

Paranet             vac163w@monu6.cc.monash.edu.au (vacation) 4 Dec 90
                    No summary has yet been posted, and personal email
                    to this person is not answered.

PC-Relay            davidl@cix.compulink.co.uk (Dave Lambert) 21 Feb 91
                    No summary has yet been posted, and personal email
                    to Mr Lambert is not answered.

Prodigy             by IBM and Sears
                    censors email
                    charges the sender of the mail message
                    Censorship details available from comp.risks issue 10.46.

PROFS (general)     PROFS is not a network.  It is an electronic office system
                    that has electronic mail as one of its components.  Many
                    companies purchase it from IBM and install it locally.

PROFS (IBM)         gt5116b@prism.gatech.EDU (Gaby Turek)
                    reports that you send to username@vmmachine.iinus1.ibm.com,
                    but the recipient must first have registered for internet
                    access.

QUICK-COMM          GE Information Services E-Mail
                    pegah@pleiades.cps.msu.edu (Mahmoud Pegah) reports
                    that as of February 1991 there is no gateway, though
                    one is under development.

SABRE               American Airlines' in-house reservation network.
                    savel@hoss.unl.edu (Bharat P. Savel) reports that
                    it has no gateway to any other network, and they
                    intend to keep it that way.

Telemail            stevenst@infonode.ingr.com (Todd Stevens) 20 Feb 91
Use the gateway at sprint.com   This requires knowledge of the recipient's
X.400 address on Telenet (now Sprintnet).  Your SMTP address will look like
this:

  smtp%"/dd.un=username/admd=telemail/o=gte/c=us/@sprint.com"

the username will be the recipient's username on the system and o will be
the organization.

VNET (IBM)          kkrueger@zeus.unomaha.edu (Kurt Krueger) 16 Feb 91

Whole Earth 'Lectronic Link (WELL)
                    basiji@milton.u.washington.edu (David Basiji) reports that
                    you send mail to username@well.sf.ca.usa

------------------------------------------------------------------------------
Ajay Shekhawat           <Dept. of Comp. Sci., SUNY@Buffalo, Amherst, NY 14260>
ajay@cs.Buffalo.EDU || ajay@sunybcs.BITNET || ajay@sunybcs.UUCP || 716.636.3180