Message Exchange Installation Guide April, 1990 This manual provides installation and setup instructions for Message Exchange, electronic mail software for VMS systems. Revision/Update Information: This manual supersedes Message Exchange Installation Guide V1.1. Operating System and Version: VMS V5.0 or later Software Version: Message Exchange V1.2 Engineering Computing Services Rensselaer Polytechnic Institute Troy, New York ________________________ 09 April 1990 Permission is granted to copy and redistribute this document for no commercial gain. The information in this document is subject to change without notice and should not be construed as a commitment by Rensselaer Polytechnic Institute. Rensselaer assumes no responsibility for any errors that may appear in this document. DISCLAIMER: The software described in this document is provided "as is". No guarantee is made by the author or the author's employer as to the suitability, reliability, security, usefulness, or performance of this software. The following are trademarks of Digital Equipment Corporation: DEC ULTRIX VAX VAXcluster VMS Jnet is a trademark of Joiner Associates, Inc. __________ Copyright ©1990 Rensselaer Polytechnic Institute All Rights Reserved. Printed in U.S.A. This document was prepared using VAX DOCUMENT, Version 1.2 _______________________________________________________ Contents _________________________________________________ PREFACE vii _______________________________________________________ CHAPTER 1 PRODUCT DESCRIPTION 1-1 _________________________________________________ 1.1 MESSAGE ROUTING SERVICE 1-1 _________________________________________________ 1.2 LOCAL DELIVERY SUPPORT 1-1 _________________________________________________ 1.3 SMTP DELIVERY SUPPORT 1-2 _________________________________________________ 1.4 JNET DELIVERY SUPPORT 1-2 _________________________________________________ 1.5 UUCP SUPPORT 1-2 _______________________________________________________ CHAPTER 2 PREPARING TO INSTALL MX 2-1 _________________________________________________ 2.1 PREREQUISITE SOFTWARE 2-1 _________________________________________________ 2.2 VAXCLUSTER SUPPORT 2-1 _________________________________________________ 2.3 DETERMINING YOUR NODE NAME 2-1 iii Contents _________________________________________________ 2.4 ACCESSING THE ONLINE RELEASE NOTES 2-2 _________________________________________________ 2.5 MAILER ACCOUNT 2-3 _________________________________________________ 2.6 INSTALLATION PROCEDURE REQUIREMENTS 2-3 _________________________________________________ 2.7 SAVING CURRENT CONFIGURATION 2-5 _______________________________________________________ CHAPTER 3 INSTALLING MESSAGE EXCHANGE 3-1 _________________________________________________ 3.1 SHUTTING DOWN MX 3-1 _________________________________________________ 3.2 INVOKING VMSINSTAL 3-1 _________________________________________________ 3.3 INSTALLATION OPTIONS 3-2 _________________________________________________ 3.4 PLACING THE MX DIRECTORIES 3-3 _________________________________________________ 3.5 ENTERING HOST NAMES 3-3 _________________________________________________ 3.6 ENTERING MAILER ACCOUNT NAME 3-4 _________________________________________________ 3.7 COMPONENT-SPECIFIC QUESTIONS 3-4 _________________________________________________ 3.8 THE INSTALLATION COMPLETES 3-6 iv Contents _______________________________________________________ CHAPTER 4 POST-INSTALLATION INFORMATION 4-1 _________________________________________________ 4.1 CONFIGURING MX 4-1 _________________________________________________ 4.2 ESTABLISHING YOUR TIME ZONE 4-2 _________________________________________________ 4.3 DEFINING A DEFAULT SMTP ROUTER 4-3 _________________________________________________ 4.4 INTERFACING MX WITH UUCP 4-3 _________________________________________________ 4.5 ADDING MX STARTUP TO SYSTEM STARTUP 4-4 4.5.1 MX Jnet Startup _______________ 4-4 _________________________________________________ 4.6 STARTING MX 4-5 _______________________________________________________ APPENDIX A SAMPLE MX INSTALLATION A-1 _______________________________________________________ APPENDIX B FILES CREATED DURING INSTALLATION B-1 _______________________________________________________ FIGURES 2-1 Mailer Account attributes _____ 2-4 v _______________________________________________________ Preface This guide describes how to install Message Exchange (MX). __________________________________________________________________ Intended Audience This manual is intended for use by the system manager or any individual responsible for installing and maintaining MX. __________________________________________________________________ Document Structure This guide consists of four chapters and two appendices. Chapter 1 Contains general information about Message Exchange. Chapter 2 Contains pre-installation information. Chapter 3 Describes the MX installation procedure. Chapter 4 Contains post-installation information. Appendix A Contains a listing of a sample installation. Appendix B Contains a list of the files created by an installation. vii Preface __________________________________________________________________ Related Documents You can find additional information in the following documents: o Message Exchange Management Guide describes the management of the MX software. o Message Exchange User's Guide describes MX features available to general users. o Message Exchange Release Notes contain information and updates not included in this manual. The release notes are part of the software distribution kit. viii _______________________________________________________ 1 Product Description Message Exchange (MX) is software that provides the routing and delivery of electronic mail messages. It is divided into four major components: message routing service, local delivery support, SMTP delivery support, and Jnet delivery support. __________________________________________________________________ 1.1 Message Routing Service MX provides a router that takes messages from the local system, SMTP input, or Jnet input channels and, based on the envelope information provided, identifies the proper delivery channel to be used for the message. The system manager may define rewrite rules to modify envelope addresses as they are processed, paths to map addresses into delivery channels, and aliases to provide automatic, transparent forwarding of messages from the local system to another address. __________________________________________________________________ 1.2 Local Delivery Support MX provides a foreign mail protocol interface for use with VMS MAIL. Users can use VMS MAIL to send and receive messages processed by MX. The MX local delivery agent distributes mail to local users and to users over DECnet (with retries). VMS MAIL forwarding is handled automatically by MX, as is forwarding-loop detection. The local delivery agent also provides mailing list service. The mailing list processor can handle subscription and signoff requests automatically, if desired, and can automatically archive messages sent to the list. Mailing lists can be restricted to allow 1-1 Product Description posting only by subscribers or only by the mailing list owners. The local delivery agent can also be set up to offer a mail-based file delivery service. __________________________________________________________________ 1.3 SMTP Delivery Support The SMTP delivery agent and server agent interface with the CMU-Tektronix TCP/IP software or DEC's VMS/ULTRIX Connection to provide RFC 821-compliant message transfers over a TCP/IP network. When used with the CMU-Tek software, the delivery agent uses mail forwarding information from the Internet domain name service (DNS) for automatic delivery of messages to hosts on other networks through mail-forwarding gateways. __________________________________________________________________ 1.4 Jnet Delivery Support The Jnet delivery agent and mail/file dispatcher interface with Joiner Associates' Jnet software for transfer of messages over an RSCS network such as BITNET. The Jnet delivery agent includes support for BSMTP and will communicate with other mailers on the BITNET network. It also provides a BITNET/Internet gateway if SMTP support is installed. __________________________________________________________________ 1.5 UUCP Support MX can be used with the DECUS UUCP package to gateway mail between UUCP and other MX-supported delivery paths. UUCP support has not been rigorously tested, but should work. 1-2 _______________________________________________________ 2 Preparing to Install MX __________________________________________________________________ 2.1 Prerequisite Software All MX components require VMS version V5.0 or later to run. The SMTP support option requires CMU-Tek TCP/IP V6.4 or V6.5, or VMS/ULTRIX Connection V1.2. The Jnet support option requires Jnet V3.4. The UUCP support option requires DECUS UUCP V1.1. __________________________________________________________________ 2.2 VAXcluster Support MX fully supports VAXcluster systems in both homogeneous and heterogeneous configurations. Loosely speaking, a VAXcluster system is homogeneous when all the nodes in the cluster share the same User Authorization File (UAF), whereas a heterogeneous VAXcluster consists of nodes that that have different UAFs. Some of the nodes in a heterogeneous VAXcluster may share a UAF with one or more other nodes; this is called a homogeneous subset of VAXcluster nodes. __________________________________________________________________ 2.3 Determining Your Node Name MX actually requires three node names for its operation. The first, the MX cluster name, is used by the MX file queueing software to determine lock names for coordination of access to the message queue. o For a stand-alone (non-clustered) system, the MX cluster name usually corresponds to your DECnet node name. If you are not running DECnet, you can use any 1-to-6 character name. 2-1 Preparing to Install MX o For a homogeneous VAXcluster system, the MX cluster name should correspond to your DECnet cluster alias node name. If do not have a cluster alias, you can use any 1-to-6 character name. o For a heterogeneous VAXcluster system, the MX cluster name should be unique to each node or homogeneous subset of nodes. The second type of node name is the MX network node name. This is the name that is used by the MX software to identify mail originating locally. You should decide on a node name for your system before installing the MX software. If you are running TCP/IP software, you should use your system's Internet node name. If using Jnet but not TCP/IP, you can use your RSCS node name. The third type of node name is the reply-to node name. This node name is used to generate "Reply-to" tags on mail originating locally. This allows you to force replies to locally-generated mail to come back through a different system, such as a company mail gateway. __________________________________________________________________ 2.4 Accessing the Online Release Notes MX provides online release notes, which you can display or print by using VMSINSTAL with the OPTIONS N parameter. After the installation, you can read the release notes by printing the file SYS$HELP:MX01n.RELEASE_NOTES, where "n" identifies the minor version number of the software. For example, for version V1.0 of MX, the file name would be MX010. 2-2 Preparing to Install MX __________________________________________________________________ 2.5 Mailer Account If you would like to use an account other than SYSTEM for running the MX detached processes, you should create the account before installing MX. The mailer account should have the following attributes: o a username of eight characters or less. o full batch access, no interactive or network access. o the INTERNET_ACCESS identifier, if needed for CMU- Tek TCP/IP access. o the ARPANET_ACCESS identifier, if needed for CMU- Tek TCP/IP access. o the following authorized and default privileges: CMKRNL, DETACH, WORLD, PHY_IO, SYSPRV, SYSLCK, EXQUOTA, TMPMBX, and NETMBX. o a subprocess limit (PRCLM) of at least 1. o no detached process limit (MAXDETACH of 0). Figure 2-1 shows the UAF entry for a typical Mailer account. __________________________________________________________________ 2.6 Installation Procedure Requirements Before installing MX, ensure that the following privileges, resources, and requirements are met: o Operating System Version MX V1.2 runs under VMS V5.0 through V5.3. o Layered Product Versions 2-3 Preparing to Install MX Figure 2-1 Mailer Account attributes _______________________________________________________ Username: MAILER Owner: MX Mailer account Account: 1 UIC: [1,76] ([MAILER]) CLI: DCL Tables: DCLTABLES Default: SYS$SYSROOT:[SYSMGR] LGICMD: NL: Login Flags: Disctly Defcli Primary days: Mon Tue Wed Thu Fri Secondary days: Sat Sun Primary 000000000011111111112222 Secondary 000000000011111111112222 Day Hours 012345678901234567890123 Day Hours 012345678901234567890123 Network: ----- No access ------ ----- No access ------ Batch: ##### Full access ###### ##### Full access ###### Local: ----- No access ------ ----- No access ------ Dialup: ----- No access ------ ----- No access ------ Remote: ----- No access ------ ----- No access ------ Expiration: (none) Pwdminimum: 3 Login Fails: 0 Pwdlifetime: (none) Pwdchange: (none) Last Login: (none) (interactive), 19-JAN-1990 14:38 (non-interactive) Maxjobs: 0 Fillm: 60 Bytlm: 36000 Maxacctjobs: 0 Shrfillm: 0 Pbytlm: 0 Maxdetach: 0 BIOlm: 20 JTquota: 1024 Prclm: 4 DIOlm: 18 WSdef: 512 Prio: 4 ASTlm: 325 WSquo: 512 Queprio: 100 TQElm: 10 WSextent: 2048 CPU: (none) Enqlm: 600 Pgflquo: 25600 Authorized Privileges: CMKRNL DETACH TMPMBX WORLD EXQUOTA NETMBX PHY_IO SYSPRV SYSLCK Default Privileges: CMKRNL DETACH TMPMBX WORLD EXQUOTA NETMBX PHY_IO SYSPRV SYSLCK Identifier Value Attributes __INTERNET_ACCESS__________________%X80010043______NORESOURCE NODYNAMIC For TCP/IP support, MX V1.2 requires CMU-Tek TCP/IP V6.4 or V6.5, or VMS/ULTRIX Conection V1.2. For Jnet support, MX V1.2 requires Jnet V3.4. For UUCP support, MX V1.2 requires DECUS UUCP V1.1. 2-4 Preparing to Install MX o all the normal privileges and quotas of the default SYSTEM account. o approximately 10 minutes to 1 hour, depending on your system configuration, distribution medium, and options selected. o 4 free global sections and 25 free global pages. o approximately 2,500 free blocks on a disk for use during the installation procedure; this can be the system disk or a disk specified with the VMSINSTAL AWD option. o approximately 30 free blocks on the system disk for permanent files. o approximately 750 free blocks on any disk for MX base software, 100 additional blocks for SMTP support, and 100 additional blocks for Jnet support. The Jnet interface also requires an XMAILER.NAMES file, which (for BITNET) requires approximately 400 free blocks. o a minimum of 2,000 free blocks on any disk for message queue space. __________________________________________________________________ 2.7 Saving Current Configuration If MX is already installed on your system, you should create an MCP command file from your current MX configuration database prior to installing a new version of MX. To do this, use the following commands: $MCP :== $MX_EXE:MCP $MCP/FILE=MX_DIR:MX_CONFIG SHOW ALL/OUTPUT=MX_DIR:OLD_CONFIG.MCP/COMMAND You can then use this MX command file to re-create your MX configuration database once the new version of MX is installed. 2-5 _______________________________________________________ 3 Installing Message Exchange MX uses VMSINSTAL for installation. If you do not know how to use VMSINSTAL, refer to the VMS Installation and Operations guide for your CPU. For the installation, you should be logged into the SYSTEM account, or another suitably privileged account. __________________________________________________________________ 3.1 Shutting down MX If any MX processes are currently running, you should stop them before installing a new version of MX. Incoming mail via SMTP, Jnet, or from local users via VMS MAIL should remain queued until you start the new MX processes. __________________________________________________________________ 3.2 Invoking VMSINSTAL Invoke VMSINSTAL to install MX. $@SYS$UPDATE:VMSINSTAL MX01n ddcu: Substitute the appropriate values for n and ddcu. VAX/VMS Software Product Installation Procedure V5.3 It is dd-Mmm-yyyy at hh:mm. Enter a question mark (?) at any time for help. If there are any users logged into the system, you will see the message %VMSINSTAL-W-ACTIVE, The following processes are still active: ...process names... 3-1 Installing Message Exchange You can install MX while users are logged in, though it is safer to perform the installation while no one is logged in and while TCP/IP and Jnet (if you have them) are shut down. * Do you want to continue anyway [NO]? If you wish to continue, answer YES. * Are you satisfied with the backup of your system disk [YES]? If you feel comfortable with your system disk backup, answer YES. Otherwise, answer NO, perform the backup, then restart the installation procedure. __________________________________________________________________ 3.3 Installation Options Some introductory information is displayed, and you are asked: * Do you want to purge files replaced by this installation [YES]? If this is the first time you have installed MX, answer NO to this question can save some time when the MX files are moved into their directories. A description of the various MX software components is displayed and you are asked: * Do you want to install SMTP support [NO]? Answer YES if you have the CMU-Tek TCP/IP software installed on your system and you want to send and receive messages using SMTP over TCP/IP. * Do you want to install JNET support [NO]? Answer YES if you have Jnet installed on your system and you want to interface MX with Jnet. * Do you want to install UUCP support [NO]? Answer YES if you have DECUS UUCP installed on your system and you want to interface MX with UUCP. 3-2 Installing Message Exchange __________________________________________________________________ 3.4 Placing the MX Directories A brief description of the directory structure used by MX is displayed, and you are asked: * Where should the MX top directory be located [SYS$SYSDEVICE:[MX]]: You may place the MX directories on any disk you like. If MX is already installed on the system and its logical names are defined, the default answer will be the definition of your existing MX root directory. The file queueing used by MX is described next, and you are asked: * Where would you like the MX file queue [SYS$SYSDEVICE:[MX.QUEUE]]: You can keep the queue with the MX directories, or you can place it on another device, depending on how busy your disks are. If MX is already installed on the system, and you keep the same queue directory, any files already in the queue will be retained. __________________________________________________________________ 3.5 Entering Host Names The host names MX uses are described as they are in Section 2.3. You should have selected the host names you want to use prior to installation, so just enter the names you selected. * Enter the local FLQ node name [MYNODE]: * Enter the MX local node name:my.mycompany.ORG * Enter the REPLY-TO node name [@mynode.mycompany.ORG]: The names are redisplayed and you are asked to confirm their correctness. 3-3 Installing Message Exchange __________________________________________________________________ 3.6 Entering Mailer Account Name Selecting a Mailer account for use by MX was described in Section 2.5. A brief description of the use of this account is displayed during the installation, and you are asked: * What username should be used for MX processes: Enter SYSTEM or the username you selected for use by MX prior to installation. Remember that the username must already exist on the system prior to installing MX. __________________________________________________________________ 3.7 Component-Specific Questions All MX components run as detached processes. However, these detached processes are started via a batch job. A separate batch job is started for each MX component, and each job may execute on a specific batch queue to have its corresponding MX detached process run on a specific node. MX Base Components You are first asked: * Which batch queue should the Router be started on: * Which batch queue should the Local agent be started on [router-queue]: The default answer for the second question is the queue name you provided for the first question. If you don't care which node executes which MX process, or you are running a stand-alone system, the default batch queue, SYS$BATCH, should be used. 3-4 Installing Message Exchange SMTP Support If you asked for SMTP support, you are asked to select which version of TCP/IP you are running on your system: CMU-Tek V6.4 or V6.5, or VMS/ULTRIX Connection. The installation procedure will attempt to detect which package is installed to provide a default answer: * Which TCP/IP will you run with MX [CMU064]: Answer CMU064 for CMU-Tek V6.4, CMU065 for CMU-Tek V6.5, or UCX for VMS/ULTRIX Connection. You are then asked: * Which batch queue should the SMTP delivery agent be started on: Only one SMTP delivery agent is required per cluster (or homogenous cluster subset). You can run several SMTP servers, however, if more than one node in your cluster is running TCP/IP. When asked: * Which batch queue(s) should the SMTP server be started on: You can specify a list of batch queues by separating the queue names with commas. Jnet Support If you asked for Jnet support, you are given some vital information about modifying the JANSITE procedures to allow mail coming in via Jnet to enter MX, and you are asked: * Which batch queue should the Jnet interface agent be started on: The Jnet interface agent must run on a node that is also running Jnet. 3-5 Installing Message Exchange UUCP Support If you asked for UUCP support, you are asked: * Which batch queue should the UUCP interface agent be started on: The UUCP interface agent must run on a node that is running DECUS UUCP. __________________________________________________________________ 3.8 The Installation Completes At this point you have answered all of the installation questions. The installation should continue on its own for about 5 to 30 minutes, depending on your CPU, distribution media, etc. Be sure to read the informational messages that are displayed while MX is being installed. Once the installation completes, be sure to complete the post-installation steps described in Chapter 4. 3-6 _______________________________________________________ 4 Post-Installation Information __________________________________________________________________ 4.1 Configuring MX Once the MX files have been installed, you should next create an MX configuration database. If you were already running MX before the installation and saved your configuration commands as described in Section 2.7, you can re-create your old configuration with the commands: $MCP :== $MX_EXE:MCP $MCP MCP>@MX_DIR:OLD_CONFIG MCP>SAVE MX_DIR:MX_CONFIG.MXCFG MCP>EXIT If this was a first-time installation, or if you want to create a new MX configuration from scratch, you should use the MXCONFIG command procedure to create an MX configuration database: $@SYS$STARTUP:MX_STARTUP LOGICALS $@MX_DIR:MXCONFIG MXCONFIG prompts you for some basic information and creates an MCP command file to create an MX configuration based. You can use MXCONFIG to define all the routing information, local aliases, and mailing lists you want to have on your system. Once the basic configuration is created with MXCONFIG, you can tailor it as you wish using the MCP commands described in Message Exchange Management Guide. 4-1 Post-Installation Information __________________________________________________________________ 4.2 Establishing Your Time Zone If you are not in the US Eastern time zone, or you are not following US standard daylight savings time, or you don't like "EST" and "EDT" as time zone names, you must add one of the following logical name definitions to your SYSTARTUP_V5.COM: If you are in the United States and you are following standard US daylight savings time, define the following logical name: $DEFINE/SYS/EXEC MDM_TZ_PREFIX x where x is the letter E, C, M, or P, depending on whether you are in the Eastern, Central, Mountain, or Pacific time zone. If you are not in the United States, or you do not wish to use the xST/xDT time zone designation, you should define the following logical: $DEFINE/SYS/EXEC MDM_TIMEZONE "tzstr" where tzstr is a valid (RFC822-compliant) time zone designation. No validity checking is performed on this string. Note that the string you specify with MDM_TIMEZONE is used verbatim. If you use MDM_TIMEZONE and you observe daylight savings time in your area, it is your responsibility for modifying the definition of MDM_TIMEZONE as needed. You do not need to shut down MX to do this. If you do not define MDM_TZ_PREFIX or MDM_TIMEZONE, the default (EST/EDT) time zone will be used. 4-2 Post-Installation Information __________________________________________________________________ 4.3 Defining a Default SMTP Router If you installed SMTP support, you can provide the name of a system, called a default router, that the SMTP delivery agent will forward messages to when it fails to find a host name in its local host tables (when running VMS/ULTRIX Connection) or through the domain name system (when running CMU-Tek TCP/IP). To define a default SMTP router, include the following logical name in your system startup sequence: $DEFINE/SYSTEM/EXEC MX_SMTP_DEFAULT_ROUTER "hostname" Before assigning a default router, you should obtain permission from the manager of the system you intend to forward messages to. __________________________________________________________________ 4.4 Interfacing MX with UUCP If you have installed the support for DECUS UUCP, you must modify the UUCP command procedure UUCP_BIN:UUXQT_DCL.COM to accomodate the hook into MX. The section of the command file after the label DO_RMAIL should be modified as follows: The line that reads $ SET PROCESS/PRIVILEGE=(SYSPRV, DETACH, BYPASS) should be modified to include the privilege SYSLCK: $ SET PROCESS/PRIVILEGE=(SYSPRV, DETACH, BYPASS, SYSLCK) The corresponding line that turns off these privileges a few lines below should be similarly modified. The line that runs the mail message through the UUCP mailer: $ MAIL/PROTOCOL=UUCP_MAILSHR 'infile' "''addr'" 4-3 Post-Installation Information should be replaced by the following two lines: $ RMAIL := $MX_EXE:MX_RMAIL $ RMAIL 'infile' "''addr'" You may want to move the definition of the RMAIL symbol to the top of the command procedure. __________________________________________________________________ 4.5 Adding MX Startup to System Startup You should add the following command to your system startup command procedure, SYS$MANAGER:SYSTARTUP_V5.COM: $@SYS$STARTUP:MX_STARTUP Remember that if you are running the MX SMTP support software, you should start MX after you start your TCP/IP software, and if you are running the MX Jnet support software, you should start MX before you start Jnet. ___________________________ 4.5.1 MX Jnet Startup If you elected to install MX Jnet support, you should edit the JAN_SYS:JANSITE.COM or JAN_SYS:JANSITECOMMON.COM command procedure for your system to include the following commands: $DEFINE/SYSTEM/EXEC JAN_MFSDISP MX_EXE:MX_MFSDISP $@SYS$STARTUP:MX_STARTUP JNET If you have a mail/file dispatcher you were using with Jnet prior to MX installation that you would like to continue to use, add the following line before the invocation of MX_STARTUP in JANSITECOMMON: $DEFINE/SYSTEM/EXEC MX_LOCAL_MFSDISP file-spec 4-4 Post-Installation Information MX_MFSDISP will automatically invoke your local mail/file dispatcher for all incoming Jnet files that it does not transfer into MX. __________________________________________________________________ 4.6 Starting MX Once you have created an MX configuration database and added the appropriate startup commands to your system startup, you are ready to start up the MX software. From the SYSTEM account, or other suitably privilged account, enter the command: $@SYS$STARTUP:MX_STARTUP If you are running MX Jnet support, you should also start (or stop and start) Jnet. 4-5 _______________________________________________________ A Sample MX Installation The following is a sample installation of MX. $@SYS$UPDATE:VMSINSTAL MX012 DISK:[MXKITS] VAX/VMS Software Product Installation Procedure V5.2 It is dd-mmm-yyyy at hh:mm. Enter a question mark (?) at any time for help. * Are you satisfied with the backup of your system disk [YES]? The following products will be processed: MX V1.2 Beginning installation of MX V1.2 at xx:xx %VMSINSTAL-I-RESTORE, Restoring product saveset A ... %VMSINSTAL-I-RELMOVED , The product's release notes have been successfully moved to SYS$HELP. Message Exchange Installation Procedure All MX components are copyright © 1990 Rensselaer Polytechnic Institute. Redistribution for no commercial gain is permitted. Jnet is a registered trademark of Joiner Associates. * Do you want to purge files replaced by this installation [YES]? M X C O M P O N E N T S E L E C T I O N The MX BASE software includes file queueing, the MX Control Program, the MX Router module, the VMS Mail interface, local distribution, mailing lists, and file server. You MUST install this component. SMTP SUPPORT provides an interface between MX and either CMU-Tek TCP/IP (V6.4 or V6.5) or DEC VMS/ULTRIX Connection for sending and receiving mail via the SMTP protocol. A-1 Sample MX Installation JNET SUPPORT provides an interface between MX and Joiner Associates' Jnet software for sending and receiving mail over Bitnet. UUCP SUPPORT provides an interface between MX and the DECUS UUCP package. * Do you want to install SMTP support [NO]? YES * Do you want to install JNET support [NO]? YES * Do you want to install UUCP support [NO]? YES MX places most of its files in a private directory structure. This directory structure can be located on any disk, but the disk must either have disk quotas disabled or sufficient diskquota to hold all of the MX images, temporary files, and log files. * Where should the MX top directory be located [SYS$SYSDEVICE:[MX]]: %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$SYSDEVICE:[MX]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$SYSDEVICE:[MX.LOCAL]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$SYSDEVICE:[MX.LOCAL.MLIST]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$SYSDEVICE:[MX.JNET]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$SYSDEVICE:[MX.SMTP]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$SYSDEVICE:[MX.EXE]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$SYSDEVICE:[MX.FILESERV]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$SYSDEVICE:[MX.ROUTER]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$SYSDEVICE:[MX.UUCP]. MX uses a file queue directory for storing mail messages. This queue directory may be placed with the other MX directories, or may be placed on a different disk. The disk on which the queue directory resides must also have quotas disabled or must have sufficient system quota to provide for a backlog of undelivered messages. * Where would you like the MX file queue [SYS$SYSDEVICE:[MX.QUEUE]]: %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$SYSDEVICE:[MX.QUEUE]. H O S T N A M E S E L E C T I O N There are three host names you must designate for the "local" host or cluster. o The FLQ node name is a 1-to-6 character name used by the file queueing software. This name usually corresponds to the DECnet cluster alias or local node name. A-2 Sample MX Installation o The MX node name is a 1-to-255 character name that identifies the "official" node name for E-mail purposes. This name usually corresponds to the Internet or BITNET node name. o The "Reply-To" node name is used by the MX/VMS MAIL interface software to create return addresses. Usually this is the same as the MX node name, preceded by an at-sign ("@"). For systems that use another host as a gateway, this can be a percent-hacked gateway address ("%localhost@gateway"). If you are running a heterogeneous VAXcluster environment, refer to the Installation Guide for details on coordinating host names and creating MX sub-clusters. * Enter the local FLQ node name [MYNODE]: * Enter the MX local node name: mynode.mycompany.ORG * Enter the REPLY-TO node name [@mynode.mycompany.ORG]: FLQ node name: MYNODE MX node name: mynode.mycompany.ORG "Reply-To" node name: @mynode.mycompany.ORG * Is this correct [YES]? You can elect to have all MX-related process execute under the SYSTEM account or some other suitably-privileged account. Note that if you have decided to install Jnet support, or you plan to do so in the future, you MUST create a separate account for handling MX mail, which must be registered as your designated mailer username for use by other BITNET hosts. NOTE: This procedure does NOT create the Mailer account for you. Refer to the pre-installation procedures in the Installation Guide for information on quotas, privileges, etc. needed for a Mailer account. * What username should be used for MX processes: MAILER If this system is part of a VAXcluster, you may elect to distribute the MX processes across several nodes in the cluster. The systems must share the same User Authorization File and must all have the same FLQ and MX node names. In addition, there must be at least one batch queue on each node to allow for startup of the processing agent. A-3 Sample MX Installation * Which batch queue should the Router be started on: SYS$BATCH * Which batch queue should the Local agent be started on [SYS$BATCH]: You must now specify which TCP/IP you wish to use with MX. Your choices are: CMU064 - CMU-Tek TCP/IP V6.4 CMU065 - CMU-Tek TCP/IP V6.5 UCX - DEC VMS/ULTRIX Connection * Which TCP/IP will you run with MX [CMU064]: The SMTP server and delivery agent must run on a node that is running the CMU-Tek software. If running on a VAXcluster, you can run the SMTP server on as many nodes in the cluster as you like, as long as all of the selected nodes run CMU-Tek. Only one SMTP delivery agent is required per cluster. Remember that the startup for CMU-Tek must come BEFORE the startup for MX in the system startup sequence. * Which batch queue should the SMTP delivery agent be started on: ACC_BATCH To specify more than one batch queue name for the next question, separate the queue names with commas. * Which batch queue(s) should the SMTP server be started on [ACC_BATCH]: The MX/Jnet Interface agent may only execute on a node that runs Jnet. Jnet must be started AFTER MX is started. To start the MX/Jnet Interface, include the following commands in the JANSITE or JANSITECOMMON procedures for your node: $ DEFINE/SYS/EXEC JAN_MFSDISP MX_EXE:MX_MFSDISP $ @SYS$STARTUP:MX_STARTUP JNET * Which batch queue should the Jnet interface agent be started on: SYS$BATCH The MX/UUCP interface should only execute on a node that is running DECUS UUCP. UUCP should be started (or at least the logicals defined) before MX is started. * Which batch queue should the UUCP interface agent be started on: SYS$BATCH All installation questions have been asked. The installation will continue for another 5 to 30 minutes, depending on your CPU type, distribution media, etc. A-4 Sample MX Installation %VMSINSTAL-I-RESTORE, Restoring product saveset B ... Now providing MX Base Support files and images. %MX-I-LINKING, Linking image FLQ_SHR... %MX-I-LINKING, Linking image MX_MAILSHR... %MX-I-LINKING, Linking image MCP... %MX-I-LINKING, Linking image MX_ROUTER... %MX-I-LINKING, Linking image MX_LOCAL... %MX-I-LINKING, Linking image MAILQUEUE... %MX-I-LINKING, Linking image FLQU... Now providing the SMTP support files and images. %VMSINSTAL-I-RESTORE, Restoring product saveset C ... %MX-I-LINKING, Linking image MX_SMTP... %MX-I-LINKING, Linking image SMTP_SERVER... Now providing the Jnet support files and images. %VMSINSTAL-I-RESTORE, Restoring product saveset D ... %MX-I-LINKING, Linking image MX_JNET... %MX-I-LINKING, Linking image MX_MFSDISP... Now providing the UUCP support files and images. %VMSINSTAL-I-RESTORE, Restoring product saveset E ... %MX-I-LINKING, Linking image MX_UUCP... %MX-I-LINKING, Linking image MX_RMAIL... Don't forget to modify the file UUCP_BIN:UUXQT_DCL.COM as described in the installation guide, to supply the hook needed to transfer mail from UUCP to MX. S Y S T E M M A N A G E R : Be sure to edit the system startup command file as described in the Installation Guide. This will minimally include adding the following command to SYSTARTUP_V5.COM: $ @SYS$STARTUP:MX_STARTUP When the installation has completed, you must create an MX configuration file with the MX Control Program (MCP). A command procedure has been provided that will prompt for basic information and create a configuration file from that information. To use this procedure, enter the commands: A-5 Sample MX Installation $ @SYS$STARTUP:MX_STARTUP LOGICALS $ @MX_DIR:MXCONFIG %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... Installation of MX V1.2 completed at xx:xx VMSINSTAL procedure done at xx:xx A-6 _______________________________________________________ B Files Created During Installation The following files are created during the installation of the MX software. Most files are placed in directories under the MX root directory you specify at installation time. The system queue file is placed in the queue directory you specify at installation time. _______________________________________________________ File_name_____________Description______________________ ___________________Files_in_FLQ_DIR:___________________ SYSTEM_QUEUE.FDL FDL file for creating queue ISAM file SYSTEM_QUEUE.FLQ_CTL System queue ISAM file _______________________________________________________ _______________Files_in_MX_ROOT:[000000]_______________ MXCONFIG.COM MX configuration creation procedure B-1 Files Created During Installation _______________________________________________________ _______________________________________________________ _________________Files_in_MX_ROOT:[EXE]________________ FLQU.EXE File queue management utility FLQ_SHR.EXE shareable image implementing file queues MAILQUEUE.EXE Program for listing delayed messages in queue MCP.EXE MX Control Program MX_JNET.COM Command procedure used by MX Jnet interface[1] MX_JNET.EXE MX Jnet interface module[1] MX_LOCAL.COM Command procedure used by MX Local delivery process MX_LOCAL.EXE MX Local delivery module MX_MAILSHR.EXE VMS MAIL foreign protocol interface MX_MFSDISP.EXE Jnet Mail/File Dispatcher for MX[1] MX_ROUTER.EXE MX Router module MX_SMTP.EXE SMTP outbound delivery module[2] _______________________________________________________ [1]Only if Jnet support is selected during installation. [2]Only if SMTP support is selected during installation. B-2 Files Created During Installation _______________________________________________________ File_name_____________Description______________________ _________________Files_in_MX_ROOT:[EXE]________________ MX_START.COM Command procedure for starting MX components MX_RMAIL.EXE UUCP mail entry interface[3] MX_UUCP.COM Used by UUCP delivery agent[3] MX_UUCP.EXE UUCP delivery agent[3] SMTP_SERVER.EXE SMTP inbound receiver module[2] _______________________________________________________ ______________Files_in_MX_ROOT:[FILESERV]______________ FILESERV_HELP.TXT Help text for use with file server _______________________________________________________ ______________Files_in_SYS$COMMON:[SYSHLP]_____________ MCP_HELPLIB.HLB Help library for MCP _______________________________________________________ ___________Files_in_SYS$COMMON:[SYS$STARTUP]___________ MX_STARTUP.COM Startup procedure for MX _______________________________________________________ [2]Only if SMTP support is selected during installation. [3]Only if UUCP support is selected during installation.__________________________________________ B-3