From: UUCP%"uunet!ccavax!lmrc!hassinger" 11-JUL-1989 13:19 To: Subj: Received: from crash by simpact.UUCP (DECUS UUCP w/Smail); Tue, 11 Jul 89 13:19:16 PDT Received: by crash.cts.com (5.54/UUCP-Project/rel-1.0/09-14-86) id AA00388; Tue, 11 Jul 89 10:01:38 PDT Reply-To: cacilj!uunet!ccavax!lmrc!hassinger Received: by cacilj.UUCP (smail2.5) id AA12155; 11 Jul 89 09:15:13 PDT (Tue) Received: from ccavax.UUCP by uunet.uu.net (5.61/1.14) with UUCP id AA21522; Tue, 11 Jul 89 12:15:10 -0400 Date: Tue, 11 Jul 89 12:15:10 -0400 From: uunet!ccavax!lmrc!hassinger Message-Id: <8907111615.AA21522@uunet.uu.net> Received: from lmrc by ccavax.camb.com (DECUS UUCP w/Smail); Tue, 11 Jul 89 12:03:41 EDT Revised: 18 June 1989 - DECWRL::"/gateway.doc" Apparently-To: cacilj!crash!jeh A MAIL gateway between Easynet and the UUCP network and the Internet (including ARPAnet, NSFNET, CSNET, and uucp) is provided by the Western Research Laboratory (WRL) in Palo Alto, California. At one point our ability to provide this service was severely jeopardized by the mailing of a chain letter through our gateway to the ARPAnet. Chain letters on the Internet are explicitly illegal and any site responsible for sending one is liable to be banned from the Internet. It is therefore crucial to our continued ability to provide this gateway service that such chain letters not be sent. Questions and problems relating to mail: DECWRL::POSTMASTER Questions and problems relating to the gateway: DECWRL::ADMIN Mailing from Easynet to a UUCP site: ------------------------------------------------ To mail a message from an Easynet node to a UNIX system on UUCP you say (NOTE the required double quotes, VMS users, see "Using Quoted Addresses from a VMS System:" below): To: DECWRL::"node-1!node-2!...!user" The UUCP network is addressed with an explicit routing list. You have to know how to route through to your desired destination. See the table at the end for the current list of UUCP sites that DECWRL dials. Mailing from Easynet to an Internet net site: ----------------------------------------------------- To mail a message from an Easynet node to someone at an Internet site (say MIT-MULTICS.ARPA) you say (NOTE the required double quotes, VMS users, see "Using Quoted Addresses from a VMS System:" below): To: DECWRL::"user@MIT-MULTICS.ARPA" The Internet is in the process changing to domain based names. The old .ARPA domain is being replaced by other top level and sub-domains. The major top level domains are .EDU educational institutions .COM commercial .GOV government .MIL military .ORG miscellaneous organizations that don't fit elsewhere .NET network operations .US random individuals There are also a number of top level domains for countries using the ISO two letter abbreviations. Within these domains are multiple levels of sub domains representing independent naming authorities. Digital operates the DEC.COM domain in the Internet; other large domains include MIT.EDU, CMU.EDU and BERKELEY.EDU. Do not use host names without a domain. A recent copy of the Internet host table can be found at DECWRL::"/etc/hosts.txt". The first name listed for each host is the official name and the only one you should use in mail messages. Mailing from Easynet to other networks: -------------------------------------------------- The gateway supports connection to several other networks using a pseudo-domain syntax. These addresses are translated by the gateway to the proper form to address the gateways into those networks. To address users in these networks you say (NOTE the required double quotes, VMS users, see "Using Quoted Addresses from a VMS System:" below): To: DECWRL::"user@host.domain" The following domains are currently supported: BITNET, CSNET, MAILNET, and OZ (once called SUN). Many of these networks are joining in the conversion to domain based naming. In particular, many .EDU and .COM addresses are actually reached through CSNET. The domain system makes all of this transparent to you. Mailing from EasyNet to the Fido network: -------------------------------------------------------- Each Fidonet node is a member of a "network", and may have subsidiary nodes called "point nodes". A typical Fido address is "1:987/654" or "987/654"; a typical Fido "point node" address is "1:987/654.32" or "987/654.32". This is zone 1, network 987, Fido (node) 654, "point node" 32. If the zone number is missing, assume it is zone 1. The zone number must be supplied in the outgoing message. To send a message to Bob Jones on Fidonet address 1:987/654 DECWRL::"Bob.Jones@f654.n987.z1.fidonet.org" Fred Smith at Fidonet 987/654.32 DECWRL::"Fred.Smith@p32.f654.n987.z1.fidonet.org" Sometimes the return addresses on messages from Fidonet will look different. You may or may not be able to reply to them. Mailing from a Fidonet node to an EasyNet node: -------------------------------------------------------- Mail to EasyNet from the Fido network is handled just like Internet mail. To send a message to RDVAX::USER from a Fidonet node: Send a message to "Uucp" on the local Fidonet gateway. (If you don't know your local Fidonet gateway, use 1:114/15, or contact Dave Dodell at 1:114/15 for guidance.) The subject field can be whatever you want it to be. The first line of the message must be: To: user@rdvax.enet.dec.com There should not be any leading spaces before the "To:". The rest of the message can be anything you like. The To:-line is removed by the gateway before delivery to Digital. Mailing from Easynet Usenet newsgroups: -------------------------------------------------- Usenet is a world wide collection of distributed bulletin boards (similar in some aspects to VAXNOTES). Digital employees may learn more about Usenet in the Usenet notes conference (consult your notes directory for current location). Newsgroups are organized in a heirarchy indicated by multipart names like sci.space.shuttle comp.mail.headers rec.arts.movies The mail gateway can be used to post articles to these groups by addressing mail To: DECWRL::"groupname@usenet" for example To: DECWRL::"rec.arts.movies@usenet" Please read the introductory information in the Usenet notes conference before sending Usenet articles. Mailing from a UUCP site to an Easynet Node: ---------------------------------------------------- When mailing to an Easynet node (say RDVAX), you need to specify a path to decwrl. The rest of the path to RDVAX would look like: To: node-1!node-2!...!decwrl!rdvax.enet!user Note that this represents a change from the previous notation, which used "...!decwrl!rdvax.dec.com!user"; the ".dec.com" suffix has changed to ".enet". The old notation will be supported until June of 1990, but users should switch to the new notation as soon as possible. Some UUCP sites which support so-called "smart" mailers may accept addresses of the form To: user@rdvax.enet.dec.com and automatically produce the optimal path to decwrl. Mailing from an Internet site to an Easynet Node: --------------------------------------------------------- To mail a message from an Internet site to an Easynet node (say RDVAX), you say: To: user@rdvax.enet.dec.com This will work if the mailer at the originating site uses the Internet domain servers to resolve the address. If the site has not yet converted to using the domain servers, an alternate form can be used: To: user%rdvax.enet@decwrl.dec.com or To: <@decwrl.dec.com:user@rdvax.enet> The latter is the technically correct form (called source route addressing) but may not be acceptable to all mailers. A few other forms are still accepted for backward compatibility but their use is discouraged and they will not be described here. Replying to messages: ----------------------------- The REPLY command (or equivalent) generates correctly formatted addresses in all known cases. Users replying to UUCP originated messages should check the generated address for missing nodes in the routing path by matching it against both the "From:" and the "Return-Path:" lines in the header. Using Quoted Addresses from a VMS System: ------------------------------------------------ The double quoted portion of the address field can cause some difficulties in DCL commands and in DCL procedures. VMS users should be aware of DCL's propensity to strip off such double quotes making the address totally useless. There is no problem when standard VAX-11 MAIL is invoked and the address is specified in response to the "TO: " prompt. If you use the MAIL command at the DCL level, then the address must be enclosed in quotes and the literal quotes must be "doubled up", e.g. $ mail test.msg "DECWRL::""decvax!aps""" /subj="Testing 1,2,3" Nmail (version 8.0 or later) is integrated with VMS MAIL for sending mail and therefore you can use any address format that MAIL can handle; simply precede the address by NM% to indicate use of Nmail. Older versions of Nmail, implemented as a .COM file, may or may not (depending on antiquity) require you to double up the quotes and enclose the whole address in quotes. The only reason you should be running an old version of Nmail is if you are using VMS V3.x. The mail command inside the NOTES utility appears to strip out embedded quotes. Enclosing the entire addressee in double quotes and quoting the literal quotes works fine here too. If you have trouble ----------------------------- Although the gateway is operated by volunteer administrators who have other work to do, we do try to help out with problems. Address your questions to DECWRL::POSTMASTER or postmaster@decwrl.dec.com or decwrl!postmaster depending on where you are coming from. You can also learn about problems and solutions through the Gateways notes conference. List of uucp sites dialed by decwrl: -------------------------------------------- (Those marked with "*" are major uucp routing nodes. You should prefer uucp routes that use these sites as the first hop from decwrl. Case is significant in uucp host names.) 3comvax 3Com Corporation, Santa Clara, CA abvax Allen-Bradley Company, Highland Heights, OH acad Autodesk, Inc, Sausalito, CA adobe Adobe Systems Inc., Mountain View, CA alberta University of Alberta, Edmonton, Alberta, Canada allegra AT&T Bell Laboratories, Murray Hill, NJ *amdahl Amdahl Corp., Sunnyvale, CA amdcad Advanced Micro Devices, Sunnyvale, CA ames NASA Ames Research Center, Mountain View, CA *apple Apple Computers, Cupertino, CA ardent Ardent Computer Corp., Sunnyvale, CA argosy MasPar Computer Corp., Sunnyvale, CA atha Athabasca University, Athabasca, Alberta, Canada athertn Atherton Technology, Sunnyvale, CA *att AT&T Bell Laboratories, Columbus, Ohio avsd Ampex Corporation, Redwood City, CA cae780 Tektronix Inc. (Santa Clara Field Office) Santa Clara, CA chip M/A-COM Government Systems, San Diego, CA claris Claris Corporation, Mountain View, CA daisy Dairy Systems, Mountain View, CA *decvax Digital Equipment Unix Engineering, Nashua, NH dsinc Datacomp Systems, Inc, Huntington Valley, PA dual Dual Systems Corp., Berkeley, CA eda EDA Systems Inc., Santa Clara, CA escd Evans and Sutherland Computer Division, Mountain View, CA esunix Evans and Sutherland Corp., Salt Lake City, UT fluke John Fluke Manufacturing, Everett, WA gryphon Trailing Edge Technology, Redondo Beach, CA handel Colorodo State Univ., CS Dept., Ft. Collins, CO hoptoad Nebula Consultants, San Francisco, CA *hplabs Hewlett Packard Research Labs, Palo Alto, CA ide Interactive Development Environments, San Francisco, CA idi Intelligent Decisions, Inc., San Jose, CA imagen Imagen Corp., Santa Clara, CA intelca Intel Corp., Santa Clara, CA ios Integrated Office Systems, Los Altos, CA killer The UNIX Connection BBS, Dallas TX limbo Intuitive Systems, Los Altos, CA logitech Logitech, Inc., Palo Alto, CA megatest Megatest Corp., San Jose, CA microsoft Microsoft, Bellevue, WA mips MIPS Computer Systems, Mountain View, CA mntgfx Mentor Graphics Corp., Beaverton, OR mordor Lawrence Livermore National Lab, Livermore, CA mtu Michigan Tech Univ., Houghton, MI mtxinu Mt. Xinu, Berkeley, CA nsc National Semiconductor Corp., Sunnyvale, CA oli-stl Olivetti Software Technology Laboratory, Menlo Park, CA oracle Oracle Corp., Belmont, CA *pacbell Pacific Bell, San Ramon, CA parcplace Parc Place Systems, Palo Alto, CA purdue Purdue University, West Lafayette, IN *pyramid Pyramid Technology Corporation, Mountain View, CA qubix Qubix Graphic Systems, San Jose, CA quintus Quintus Computer Systems, Mountain View, CA research AT&T Bell Laboratories, Murray Hill, NJ riacs Res.Inst. for Adv. Compu. Sci., Mountain View, CA rtech Relational Technology Inc., Alameda, CA sci Silicon Compilers, San Jose, CA sequent Sequent Computer System, Inc., Beaverton, OR sgi Silicon Graphics, Inc., Mountain View, CA simpact Simpact Assoc., San Diego, CA sjsca4 Schlumberger Technologies, San Jose, CA sun Sun Microsystems, Mountain View, CA td2cad Intel Corp., Santa Clara, CA theta Process Software Inc., Wellesley, MA turtlevax CIMLINC, Inc, Palo Alto, CA *ucbvax University of California, Berkeley, CA utcsri Univ. of Toronto, Computer Science, Toronto, CA vlsisj VLSI Technology Inc., San Jose, CA wyse Wyse Technology, San Jose, CA zehntel Zehntel, Inc., Walnut Creek, CA From ncr-sd!hp-sdd!hplabs!pyramid!decwrl!vixie Sat Oct 22 22:33:43 PDT 1988 Article 1525 of comp.mail.misc: Path: crash!ncr-sd!hp-sdd!hplabs!pyramid!decwrl!vixie >From: vixie@decwrl.dec.com (Paul Vixie) Newsgroups: comp.mail.misc Subject: Re: DEC gateway needed Message-ID: <9@gnome6.pa.dec.com> Date: 19 Oct 88 10:24:36 GMT References: <4714@thorin.cs.unc.edu> Organization: DEC Western Research Lab Lines: 46 In article <4714@thorin.cs.unc.edu> hewitt@cs.unc.edu writes: # I am looking for a gateway between the Internet and DEC's internal # mail network. Is there such a gateway? Does a user have to obtain # permission to use it? All info would be greatly appreciated. Decwrl.dec.com is the gateway between the internet and DEC's internal network. There are two kinds of host in here: DECNet/mail-11 and Internet/SMTP/RFC822. You will in most cases not need to know which kind of host you're trying to reach. Mail to decwrl!PERSON or PERSON@decwrl.dec.com will reach anyone who works in DEC's Palo Alto buildings; you don't really need to know what host they read their mail on. Mail to decwrl!HOST.dec!PERSON or decwrl!HOST.dec.com!PERSON or PERSON%HOST.dec@decwrl.dec.com or PERSON%HOST.dec.com@decwrl.dec.com will reach anyone outside of Palo Alto, but you'll need to know their host name. There are a few subdomains of .dec.com, and if you need one, you'll know which one to use :-). It doesn't really matter whether they are reachable on DECNet/Mail-11 or Internet/SMTP; the address syntax is the same for both (or so it will seem to you, at any rate). You don't need anybody's permission to use this, since you are sending mail to DEC people after all so it's okay to use DEC equipment to do it. The trick is that you'll need to know the login name and sometimes the host name, which means you need to have some kind of contact with the person you want to send the mail to before you can start sending them mail. This is probably a bug, but there it is, anyway. Note that decwrl.dec.com is the MX for *.dec.com, and that those of you with recent (MX-capable) mailers can also send mail to PERSON@HOST.dec.com and it should work. Questions or complaints regarding DEC's mailers should be sent to postmaster@decwrl.dec.com You could also send directly to me, but if I'm on vacation(1), you'll want to reach whoever has the duty while I'm away. -- Paul Vixie Work: vixie@decwrl.dec.com decwrl!vixie +1 415 853 6600 Play: paul@vixie.sf.ca.us vixie!paul +1 415 864 7013