telecom@eecs.nwu.edu (TELECOM Moderator) (10/21/90)
TELECOM Digest Sat, 20 Oct 90 20:53:00 CDT Special: Network Guide
Inside This Issue: Moderator: Patrick A. Townson
Introduction [TELECOM Moderator]
Network Guide [John J. Chew, via Syd Weinstein]
Email Addresses: Public? Private? Somewhere in Between? [M. Schoffstall]
----------------------------------------------------------------------
From: TELECOM Moderator <telecom@eecs.nwu.edu>
Subject: Introduction to Network Guide
Date: 20 Oct 1990
This issue of the Digest is devoted to a theme near and dear to my
heart: universal, and easy to use email. For a long time now, I have
campaigned for an expansion of the email universe. Furthermore, I
believe email should be, and will eventually be as easy to use and
commonplace as a telephone call.
Internetwork email is becoming easier and easier to use, but there are
still those systems which seem to relish making it as hard as possible
to connect with another network. And there are those networks, that
for whatever reason seem to feel a policy of exclusion is in their
best interest -- a policy which prevents their subscribers from
writing to other networks, and keeps other networks from reaching
them. Thank goodness both MCI Mail and AT&T Mail wised up early on to
the fallacy behind this kind of exclusivity: there is no advantage in
limiting the number of people who can reach you or be reached by
yourself.
I'll repeat what I have asked for many times in the past:
Interconnectivity between networks and sites where the routing is
totally transparent to users. I'd like to see the time when something
like the Network Guide -- valuable as it is -- is no longer required.
A user would enter an address and be done with it, and the standards
would be the same from one network to another; from one site to
another.
Likewise, the "White Pages" mentioned in the second message of this
special issue is an idea whose time is overdue. As David Tamkin points
out in a message which will appear in a future issue of the Digest,
unlike a telephone call, where a call (wanted or unwanted) ties up the
use of the service for the subscriber, email does not deprive the
subscriber of the right to receive and send other email. Email can be
a very powerful force in our society. 'The Power of the Pen' should
not be overlooked in this medium as a way to raise issues, ask
questions, advise others and educate ourselves. If you decide to try
using the White Pages, you might be surprised at the number of people
you can reach through email.
Enjoy this issue of the Digest!
Patrick Townson
--------------------------------------
From: Syd Weinstein <syd@dsi.com>
Subject: Network Guide
Reply-To: syd@dsi.com
Organization: Datacomp Systems, Inc. Huntingdon Valley, PA
Date: Fri, 19 Oct 90 14:54:30 GMT
claris!netcom!mcmahan@ames.arc.nasa.gov (Dave Mc Mahan) writes:
>I was asked an interesting question the other day. Someone I work
>with wanted to e-mail another party, but that party only had BIX and
>CompuServe.
>If you know of another network that can send e-mail, please let me
>know.
There is a generic file posted every so often by John J. Chew
<poslfit@gpu.UTCS.UToronto.CA> in comp.mail.misc and
news.newusers.questions called the Inter-Network Mail Guide.
Here is a recent issue for your information:
Inter-Network Mail Guide - Copyright 1990 by John J. Chew
$Header: netmail, v1.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
Sydney S. Weinstein, CDP, CCP Elm Coordinator
Datacomp Systems, Inc. Voice: (215) 947-9900
syd@DSI.COM or dsinc!syd FAX: (215) 938-0235
------------------------------
From: Martin Schoffstall <schoff@uu.psi.com>
Subject: Re: Email Addresses: Public? Private? Somewhere in Between?
Reply-To: Martin Schoffstall <schoff@uu.psi.com>
Organization: Performance Systems International, Inc.
Date: Thu, 18 Oct 90 05:51:21 GMT
If you telnet into wp.psi.com and login as "fred" you will find some
number of organizations in the US Internet who believe that some
amount of information even beyond the email address is public. The
organizations range from Kodak to DOE, to Columbia to Cray.
This service is an Internet wide WhitePages service of which either
Marshall Rose or I could try to retell some of the stories of this two
year old project containg 100,000's of thousands of entries, most kept
up to date on a weekly or monthly basis. But only if there is
interest.
Marty
[Moderator's Note: Marty, thanks for passing along this valuable
address for the readers of the Digest. I hope at least a few folks
will make use of it. And yes please, share your stories. Better still,
how about a short tutorial with examples of how to use the White
Pages. PAT]
------------------------------
End of TELECOM Digest Special: Network Guide
******************************peter@ficc.ferranti.com (peter da silva) (10/22/90)
It wouldn't take much change to allow anonymous UUCP to provide email at least as convenient as FAX. You would send mail to <name@9999999.phone>, and it queues up a uux rmail to that number. You'd just need a routing script that adds the appropriate line to the Systems file before queueing the UUCP. The biggest problem is standardising chat scripts. Peter da Silva. +1 713 274 5180. peter@ferranti.com