🚀 go-pugleaf

ajay@sybil.cs.Buffalo.EDU (Ajay Shekhawat) writes:

> Due to some requests for an updated version, I managed to update the
> Internet Mailing Guide (it's upto v1.1 now, up from v1.0 last year :-)
> 
> Here's the updated version.  If you have any changes, please reply to
> this message (hit "r" in [tx]rn) asap, and I'll incorporate the
> changes.  Thanks!
> 
> Ajay S.
> 
The appended was posted to bit.listserv.infonets recently so it looks
like Mr. Chew is going to start maintaining the list again.

--
Internet: rick@ricksys.lonestar.org,      bo836@cleveland.freenet.edu
UUCP: ...!rwsys!ricksys!rick,   {backbones}!ricksys.lonestar.org!rick
BITNET: bo836%cleveland.freenet.edu@cunyvm  Fidonet: Richard McCombs @ 1:385/6
-- Vote YES for comp.bbs.waffle


Article 1629 of bit.listserv.infonets:
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Path: usenet.ins.cwru.edu!ukma!nntp.msstate.edu!paladin.american.edu!auvm!AIS.BERGER-LEVRAULT.FR!JJCH
Return-Path: <owner-info-nets@Think.COM>
Errors-To: owner-info-nets@Think.COM
X-Administrator: Robert L. Krawitz <info-nets-request@think.com>
Precedence: bulk
Approved: info-nets@think.com
Message-ID: <9204031250.AA28795@AIS.Berger-Levrault.FR>
Newsgroups: bit.listserv.infonets
Date:         Fri, 3 Apr 1992 14:50:25 +0200
Reply-To:     Info-Nets@Think.Com
Sender:       owner-info-nets@think.com
Comments:     Warning -- original Sender: tag was owner-info-nets@THINK.COM
From:         John Chew <jjch@AIS.BERGER-LEVRAULT.FR>
Subject:      Re: Inter-Network Mail Guide
Comments: To: info-nets@Think.COM

In response to Jeff Block <22648MGR@msu.edu>'s recent posting of version 1.10
of my Inter-Network Mail Guide:

The last version of the INMG was dated 90/05/31, since which date I have not
had enough time to keep the document up-to-date, owing to a change of job
and country of residence.  I would like to announce now that I will begin
editing the guide again, because I am concerned at the number of people who
may be using out-of-date information, and because almost two years later I
still receive several pieces of mail a day concerning it.  (The mail is
curiously like an extra subscription to info-nets, a mixture of useful
information with very naive queries - the only thing i don't get many of
are unsubscription request :-).)

I will start by appending to this message version 1.11 of the guide, with
the warning that I am doing so solely to solicit corrections and additions
and not to suggest that its information is current or accurate.  I would
appreciate it if info-nets readers would send corrections, preferably in
patch(1) format, addressed to <poslfit@utcs.utoronto.ca> (whence it will
be forwarded here to France), mentioning the guide either by its full name
or just as "INMG" somewhere to alert my Perl mail receiver.

If all goes well, I will start monthly updates again and post them to this
list as a sort of secondary FAQ document.

John
--
John J. Chew, III       * AIS/Berger-Levrault * jjchew@AIS.Berger-Levrault.FR
phone +33 1 46 40 10 60 * 34, avenue du Roule * poslfit@UTCS.UToronto.CA
fax   +33 1 46 40 18 44 * Neuilly-sur-Seine   * poslfit@utorgpu.bitnet
telex BL NANCY 960 212  * 92200 France        * Berger.Lev.@AppleLink.Apple.COM
"Les arbres sont souvent en cause dans les accidents de la circulation."
-----
# Inter-Network Mail Guide - Copyright 1990 by John J. Chew
#   $Header: netmail,v 1.11 90/05/31 19:45:04 john Exp $
#
# WHAT'S NEW
#
# + FTP instructions to Ra.MsState.edu
# + easynet (DEC's internal network)
# + sprintmail (formerly telemail)
# - telemail (now sprintmail)
# - arisia.xerox.com's connection to PeaceNet/EcoNet (dead)
#
# 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 between 14:00 and
# 18:00 Eastern Time (UTC-4h or UTC-5h depending on the time of year) at
# +1 416 425 3818.
#
# 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)
#   att           AT&T Mail (commercial)
#   bitnet        international academic network
#   bix           Byte Information eXchange: Byte magazine's commercial BBS
#   bmug          Berkeley Macintosh Users Group
#   cgnet         Agricultural research network
#   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)
#   ibm           IBM's internal network
#   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          NASA Science Internet
#                 formerly Space Physics Analysis Network/HEPnet/StarLink
#   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 att
#T internet
#R user@domain
#I send to "internet!domain!user"
#I   domain can be of the form "site.bitnet"

#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 cgnet
#T internet
#R user@domain
#I send to "INTERMAIL"
#I message body must contain an appropriately (?) formatted header

#F compuserve
#T fax
#R +1 415 555 1212
#I send to ">FAX 14155551212"
#I not transitive - message must originate from a CompuServe user
#I for calls outside the NANP, use "011" as the international prefix

#F compuserve
#T internet
#R user@domain
#I send to ">INTERNET:user@domain" (only from CompuServe users)

#F compuserve
#T mci
#R 123-4567
#I send to ">MCIMAIL:123-4567" (only from CompuServe users)

#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 att
#R user
#I 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 cgnet
#R user
#C intermail-request@intermail.isi.edu
#I send to "user%CGNET@intermail.isi.edu"

#F internet
#T compuserve
#R 71234,567
#I send to "71234.567@compuserve.com"
#I   Ordinary Compuserve account IDs are pairs of octal numbers

#F internet
#T compuserve
#R organization:department:user
#I send to "user@department.organization.compuserve.com"
#I   This syntax is for use with members of organizations which have a
#I   private CompuServe mail area.  "department" may not always be present.

#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 ibm
#R user@vmnode.tertiary_domain (syntax?)
#C nic@vnet.ibm.com
#I send to "user@vmnode.tertiary_domain.ibm.com"
#I nic handles automatic name lookups in response to "WHOIS name" in msg body.

#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>
#C 267-1163 (MCI Help)
#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

--
Internet: rick@ricksys.lonestar.org, bo836@cleveland.freenet.edu
UUCP: ...!rwsys!ricksys!rick,  {backbones}!ricksys.lonestar.org!rick
BITNET: bo836%cleveland.freenet.edu@cunyvm Fidonet: Richard McCombs @ 1:385/6