FAQ?? (for internet/compuserve mail)

Dan Jacobson danj at welchgate.welch.jhu.edu
Mon Jan 4 15:30:03 EST 1993


Eric Mansell writes:

>I know this must be asked all the time, but is
>there a faq or other info around anywhere on how
>to get mail to/from internet to compuserve, prodigy, etc.?

Yes this type of information is available and has been posted
before.  This one is a copy of a note that Rob Harper posted.

Best of luck,

Dan Jacobson

danj at welchgate.welch.jhu.edu


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

Below are copies of two guides to Inter-Network mail.  I am not the
author.  Please send comments or corrections to the original authors
whose names are included below. This file will be placed on nic.funet.fi
for downloading via anonymous ftp from the directory /pub/sci/molbio/biodocs


********************* John J. Chew Article ************************
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 at 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 at 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 at 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 at 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 at domain
#I send to "user at domain@internet#"
#I   domain can be be of the form "site.bitnet", address must be <35 characters

#F bitnet
#T internet
#R user at 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 at domain".
#I If this doesn't work, try "user%domain at 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 at 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 at domain
#I send to ">INTERNET:user at domain"

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

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

#F easynet
#T bitnet
#R user at site
#C DECWRL::ADMIN
#I from VMS use NMAIL to send to "nm%DECWRL::\"user at site.bitnet\""
#I from Ultrix
#I   send to "user at site.bitnet" or if that fails
#I     (via IP) send to "\"user%site.bitnet\"@decwrl.dec.com"
#I     (via DECNET) send to "DECWRL::\"user at 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 at p4.f3.n2.z1.fidonet.org\""
#I from Ultrix
#I   send to "john.smith at 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 at p4.f3.n2.z1.fidonet.org\""

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

#F envoy
#T internet
#R user at 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 at domain
#I send to "uucp" at nearest gateway site
#I first line of message: "To: user at domain"

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

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

#F internet
#T bitnet
#R user at site
#I send to "user%site.bitnet at 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 at dcibix.das.net"

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

#F internet
#T compuserve
#R 71234,567
#I send to "71234.567 at 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 at dcjcon.das.net"

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

#F internet
#T easynet
#R John Smith @ABC
#C admin at decwrl.dec.com
#I send to "John.Smith at 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 at p4.f3.n2.z1.fidonet.org"

#F internet
#T geonet
#R user at host
#I send to "user:host at 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 at mcimail.com"
#I or send to "JSMITH at mcimail.com" if "JSMITH" is unique
#I or send to "John_Smith at mcimail.com" if "John Smith" is unique - note the
#I    underscore!
#I or send to "John_Smith/1234567 at mcimail.com" if "John Smith" is NOT unique

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

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

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

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

#F internet
#T span
#R user at host
#C <NETMGR at nssdca.gsfc.nasa.gov>
#I send to "user at host.span.NASA.gov"
#I   or to "user%host.span at 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/@Sp
   rint.COM"

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

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

#F nasamail
#T internet
#R user at 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 at domain"

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

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

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

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

END

-----
Date: 8 Jul 91 07:56:37 GMT
From: rsw at cs.brown.EDU (Bob Weiner)
Subject: Basic guide on how to send e-mail

[I don't profess that this will work for those who know nothing about
computers, but I do think it is a good, short example of how to explain a
problem like e-mail addressing to a novice computer user.

It does not discuss X.400 based e-mail but should at some future time.]

************************ Bob Weiner Article ***********************
                   Internet / Usenet Mail Addressing Guide
                                 Bob Weiner
                               rsw at cs.brown.edu
                                 July 8, 1991

This document discusses how to address mail to or from both Usenet (via UUCP =
UNIX to UNIX Copy Protocol) and the Internet (via SMTP = Simple Mail Transfer
Protocol).  Mail through the Internet can reach Usenet, Compuserve, MCI Mail,
and many research and corporate organizations throughout the world.

It assumes you have a mail reader and composer program with its own
documentation, on a computer which can connect to Usenet or the Internet.  The
mail address is what you will put or receive on the message line that begins
with the literal string: "To:".

************************
Sending Worldwide E-mail
************************

Here is how you mail to someone else.  (Items within <> or in all capitals are
field names for which you must give literal values.  Items in [] are optional
fields, which are only included in certain electronic mail addresses. An |
symbol means choose one from the set of alternatives separated by the symbol. A
host is a computer)




More information about the Proteins mailing list