(:source 
  :version  3 
  :ip-address "152.2.22.81"
  :ip-name "sunsite.unc.edu"
  :tcp-port 210
  :database-name "internet-mail"
  :cost 0.00 
  :cost-unit :free 
  :maintainer "jem@sunsite.unc.edu"
  :description "
Archive-name: inter-network mail guide
#VERSION: $Revision: 2.1 $
#VERSION: $Date: 7/2/93 $
#           * INTER-NETWORK MAIL GUIDE:    Last Update: 7/2/93 *
#
# Inter-Network Mail Guide - Original Copyright (C) 1992 by John J. Chew
# Further modifications and (C) 1993 by Scott Yanoff (yanoff@csd4.csd.uwm.edu)
#
# 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 follow the instructions in the section
# entitled 'HOW TO FORMAT INFORMATION FOR SUBMISSION' and then mail the
# information to me: Scott A. Yanoff <yanoff@csd4.csd.uwm.edu>. 
#
# HOW TO USE THIS GUIDE
#
# If you just want to browse the guide manually for information, this is what
# you need to know.  The guide is organized as a list of entries.  Each entry
# tells you how to get from one network to another.  Here is what a typical
# entry might look like:
#
#   #FROM: mynet
#   #TO: yournet
#   #RECIPIENT: youraddress
#   #CONTACT: contactaddress
#   #INSTR: send to 'youraddress@thegateway'
#
# This means that to send mail FROM a network called 'mynet' TO a
# RECIPIENT address 'youraddress' on a network called 'yournet', you
# should follow the INSTRUCTIONS shown and address your mail to
# 'youraddress@thegateway'.
#
# Names and descriptions of the possible FROM and TO fields:
#
#N: aol           ; America Online; America Online, Inc.; commercial;
#N: applelink     ; AppleLink; Apple Computer, Inc.; in-house;
#N: arcom         ; X.400; ?; ?;
#N: att           ; AT&T Mail; AT&T; commercial;
#N: bitnet        ; BITNET; none; academic;
#N: bix           ; Byte Information eXchange; Byte magazine; commercial;
#N: bmug          ; ? ; Berkeley Macintosh Users Group; in-house;
#N: compuserve    ; CompuServe; CompuServe Inc.; commercial;
#N: connect       ; Connect Professional Information Network; ?; commercial;
#N: easylink      ; Easylink; AT&T; commercial;
#N: easynet       ; Easynet; DEC; in-house;
#N: envoy         ; Envoy-100; Telecom Canada; commercial; X.400
#N: fax           ; Facsimile document transmission; none; none;
#N: fidonet       ; FidoNet; none; bbs;
#N: genie         ; Genie; commercial; ?;
#N: geonet        ; GeoNet Mailbox Systems; 
#- Geonet Mailbox Services GmbH/Systems Inc.; commercial;
#N: gold-400      ; GNS Gold 400; British Telecom; commercial; X.400
#N: goldgate      ; GoldGate Telcom Gold; Net-Tel Computer Systems; ?;
#N: greennet      ; GreenNet; Soft Solutions Ltd; commercial;
#N: gsfcmail      ; GSFCmail; NASA/Goddard Space Flight Center; in-house;
#N: ibm           ; VNET; IBM; in-house;
#N: internet      ; Internet; none; academic;
#N: keylink       ; KeyLink; Telecom Australia; commercial; X.400
#N: mailnet       ; X.400; ?; ?;
#N: mausnet       ; Mausnet; Mausnet; non-profit;
#N: mci           ; MCIMail; MCI; commercial;
#N: mfenet        ; Magnetic Fusion Energy Network;
#- Lawrence Livermore National Laboratory; academic;
#N: nasamail      ; NASAMail; NASA; in-house;
#N: nsi           ; NASA Science Internet; NASA; government;
#-  Dual-protocol: instructions given here pertain only to NSI-DECnet addresses
#-  (NSI-TCP/IP addresses should be treated as shown for 'internet')
#N: omnet         ; OMNET; OMNET; commercial;
#N: peacenet      ; PeaceNet; Institute for Global Communications;
#- non-profit;
#N: sinet         ; Schlumberger Information NETwork; ?; ?;
#N: sprintmail    ; SprintMail; Sprint; commercial; formerly Telemail
#N: thenet        ; Texas Higher Education Network; University of Texas;
#- academic ;
#N: wwivnet       ; WWIVnet; WWIVnet; non-profit;
# The 'RECIPIENT' record gives an example of an address on the
# destination network, to make it clear in subsequent lines what text
# requires subsitution.
#
# The 'CONTACT' record gives an address for inquiries concerning the
# gateway, expressed as an address reachable from the source (#FROM:) 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.
#
# The 'INSTR' records, 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.  If
# the instructions consist simply of mailing to a certain address, this
# will be indicated by the words 'send to' followed by a quoted address.
# If there are alternative addresses, they will be marked 'or to' instead.
#
# HOW TO FORMAT INFORMATION FOR SUBMISSION
#
# Here is what I really want in the way of information.  If you are adding
# a new network to the list, tell me what its official name is (pay attention
# to capitalization), what the name of its responsible organization is, and
# what kind of a network it is (academic, commercial, government, in-house
# or non-profit).  If this isn't clear, look at the examples above.
# For each connection, give me an entry that looks something like:
#
# #FROM: foonet
# #TO: barnet
# #RECIPIENT: baraddress
# #CONTACT: contactaddress
# #INSTR: send to 'baraddress@thegateway'
#
# Note that 'contactaddress' must be an address expressed in foonet's native
# format, and not that of barnet, since if a user is having trouble accessing
# barnet, giving him/her an address on that net to contact for help is not
# productive.  If there is no contact/postmaster address, please tell me.
# If there are more complicated instructions, use additional #INSTR: lines.
#
# Once you've got all the information together, send it to me in an e-mail
# message with the words 'INMG update' in the Subject: line.  You can in
# general expect an answer back from me within a week.
"
  )
