                                       -           Message Exchange Installation Guide                  October, 1998       5           This manual provides installation and setup <           instructions for Message Exchange, electronic mail#           software for VMS systems.         A           Revision/Update Information:  This is a revised manual.   =           Operating System and Version: VAX/VMS V5.2 or later   =                                         OpenVMS Alpha V1.5 or -                                         later   =           Software Version:             Message Exchange V5.1   )           Matt Madison and Hunter Goatley            MadGoat Software         "           17_October_1998_________  ?           The information in this document is subject to change 9           without notice and should not be construed as a :           commitment by MadGoat Software. MadGoat Software;           assumes no responsibility for any errors that may "           appear in this document.  8           No part of this publication may be reproduced,9           transmitted, transcribed, stored in a retrieval =           system, or translated into any language or computer ;           language, in any form or by any means electronic, ?           mechanical, magnetic, optical, chemical, or otherwise 9           without the prior written permission of MadGoat            Software.   ;           Use of this software and documentation is subject >           to the terms and conditions set forth in the License           Agreement.  =           The Licensed Materials are provided with RESTRICTED 8           RIGHTS. Use, duplication, or disclosure by the<           Government is subject to restrictions as set forth?           in subparagraph (c)(1)(ii) of the Rights in Technical >           Data and Computer Software clause at DFARS 252.227-@           7013 or subparagraphs (c)(1) and (2) of the Commercial@           Computer Software-Restricted Rights at 48 CFR 52.227-           19, as applicable.  =           MadGoat, Message Exchange, and MX are trademarks of            MadGoat Software.   ;           The following are trademarks of Digital Equipment            Corporation:  7           DEC                DECnet              P.S.I. ;           ULTRIX             VAX                 VAXcluster ;           VMS                AXP                 VMScluster   @           Jnet is a registered trademark of Wingra Technologies,           Inc.  ;           MultiNet and TCPware are registered trademarks of '           Process Software Corporation.   6           LISTSERV is a registered trademark of L-Soft           International.  :           WIN/TCP and Pathway are registered trademarks of           Attachmate, Inc.             __________@           Copyright 1998 MadGoat Software. ALL RIGHTS RESERVED.                       A           _______________________________________________________              Contents  A                 _________________________________________________ A                 PREFACE                                       vii   A           _______________________________________________________ 1           CHAPTER 1  PREPARING TO INSTALL MESSAGE A                      EXCHANGE                                 1-1   A                 _________________________________________________ A                 1.1   SOFTWARE LICENSE KEY                    1-1   A                 _________________________________________________ A                 1.2   PREREQUISITE SOFTWARE                   1-1   A                 _________________________________________________ 9                 1.3   UPGRADING FROM PREVIOUS VERSIONS OF A                       MX                                      1-1   A                 _________________________________________________ A                 1.4   VMSCLUSTER SUPPORT AND MX CLUSTERS      1-2   6                 1.4.1     Answering VMScluster-relatedA                           Installation Questions  ________    1-2   4                 1.4.2     Mixed VMSclusters (VAX andA                           Alpha systems)  ________________    1-3   A                 _________________________________________________ A                 1.5   DETERMINING YOUR NODE NAME              1-4   A                 _________________________________________________ A                 1.6   ACCESSING THE ONLINE RELEASE NOTES      1-5   A                 _________________________________________________ A                 1.7   MAILER ACCOUNTS                         1-5   9                 1.7.1     SMTP-over-DECnet/X.25 Dedicated A                           Account  _______________________    1-6   A                                                               iii                     Contents          A                 _________________________________________________ A                 1.8   INSTALLATION PROCEDURE REQUIREMENTS     1-7   A                 _________________________________________________ A                 1.9   SAVING CURRENT CONFIGURATION           1-10     A           _______________________________________________________ A           CHAPTER 2  INSTALLING MESSAGE EXCHANGE              2-1   A                 _________________________________________________ A                 2.1   SHUTTING DOWN MX                        2-1   A                 _________________________________________________ A                 2.2   INVOKING VMSINSTAL                      2-2   A                 _________________________________________________ 4                 2.3   MIXED VAX AND ALPHA VMSCLUSTERA                       SUPPORT                                 2-2   A                 _________________________________________________ A                 2.4   INSTALLATION OPTIONS                    2-3   A                 _________________________________________________ A                 2.5   COMPONENT SELECTION                     2-4   A                 _________________________________________________ A                 2.6   BASE SOFTWARE CONFIGURATION             2-5   A                 2.6.1     Placing the MX Directories  ____    2-6   6                 2.6.2     Selecting the Size of the MXA                           Message Queue  _________________    2-7   A                 _________________________________________________ A                 2.7   NETLIB COMPONENT INSTALLATION           2-7   A                 _________________________________________________ A                 2.8   THE INSTALLATION COMPLETES              2-9              iv         A                                                          Contents           A           _______________________________________________________ A           CHAPTER 3  POST-INSTALLATION INFORMATION            3-1   A                 _________________________________________________ A                 3.1   LICENSE KEY REGISTRATION                3-1   A                 _________________________________________________ A                 3.2   CONFIGURING MX                          3-1   A                 _________________________________________________ A                 3.3   ESTABLISHING A POSTMASTER               3-2   A                 _________________________________________________ A                 3.4   ADDING MX STARTUP TO SYSTEM STARTUP     3-2   A                 3.4.1     MX Jnet Startup  _______________    3-4   A                 3.4.2     Example  _______________________    3-5   A                 _________________________________________________ 2                 3.5   ADDING MX SHUTDOWN TO SYSTEMA                       SHUTDOWN                                3-6   A                 _________________________________________________ A                 3.6   ESTABLISHING YOUR TIME ZONE             3-6   8                 3.6.1     The Product-Specific Time ZoneA                           Logicals  ______________________    3-6   A                 3.6.2     The MX Timezone Logicals  ______    3-7   A                 _________________________________________________ A                 3.7   INTERFACING WITH TCP/IP                 3-8   A                 3.7.1     Disabling Vendor SMTP Support  _    3-8 5                 3.7.1.1     Disabling CMUIP SMTP, 3-8 8                 3.7.1.2     Disabling MultiNet SMTP, 3-87                 3.7.1.3     Disabling TCPware SMTP, 3-9 3                 3.7.1.4     Disabling UCX SMTP, 3-9 8                 3.7.1.5     Disabling Wollongong PathWay&                             SMTP, 3-10  A                                                                 v                     Contents          A                 3.7.2     Ensuring SMTP Server Restarts  _   3-11   A                 3.7.3     Enabling SMTP Kanji Support  ___   3-11   A                 _________________________________________________ A                 3.8   INTERFACING WITH UUCP                  3-11   A                 _________________________________________________ A                 3.9   SMTP SUPPORT FOR DECNET AND X.25       3-12   6                 3.9.1     Creating a DECnet Object forA                           DECnet-SMTP  ___________________   3-13   6                 3.9.2     Creating a DECnet Object forA                           X.25-SMTP  _____________________   3-15   A                 _________________________________________________ 7                 3.10  CUSTOMIZING MAILING LIST AND FILE A                       SERVER FILES                           3-16   A                 _________________________________________________ A                 3.11  SETTING UP MXALIAS                     3-16   A                 _________________________________________________ A                 3.12  STARTING MX                            3-18   A           _______________________________________________________ A           APPENDIX A  SAMPLE MX INSTALLATION                  A-1   A           _______________________________________________________ A           APPENDIX B  CONTENTS OF DISTRIBUTION KIT            B-1   A           _______________________________________________________ A           APPENDIX C  FILES CREATED DURING INSTALLATION       C-1                        vi         A                                                          Contents           A           _______________________________________________________            FIGURES   A                 1-1       Mailer Account attributes  _____    1-7   9                 1-2       SMTP-over-DECnet server account A                           attributes  ____________________    1-8   A           _______________________________________________________            TABLES  A                 B-1       MX installation kit save sets  _    B-1   8                 C-1       Message Exchange files createdA                           during installation  ___________    C-2                                                   A                                                               vii                    A           _______________________________________________________              Preface   >           This guide describes how to install Message Exchange           (MX).   L           __________________________________________________________________             Intended Audience   ?           This manual is intended for use by the system manager :           or any individual responsible for installing and           maintaining MX.   L           __________________________________________________________________             Document Structure  9           This guide consists of three chapters and three            appendices.   ;           Chapter    Contains pre-installation information.            1   =           Chapter    Describes the MX installation procedure.            2   <           Chapter    Contains post-installation information.           3   A           Appendix   Contains a listing of a sample installation.            A   5           Appendix   Describes the contents of the MX &           B          distribution kit.  ?           Appendix   Contains a list of the files created by an "           C          installation.  L           __________________________________________________________________             Related Documents   >           You can find additional information in the following           documents:  <           o  Message Exchange Management Guide describes the+              management of the MX software.   A                                                               vii                     Preface           @           o  Message Exchange User's Guide describes MX features(              available to general users.  >           o  Message Exchange Programmer's Guide describes the?              various programming interfaces for customizing MX.   <           o  Message Exchange Mailing List/File Server Guide;              describes the MX Mailing List and File Server.   ?           o  Message Exchange Release Notes contain information A              and updates not included in this manual. The release =              notes are part of the software distribution kit. @              Release notes are also included in the distribution:              kit for NETLIB, the TCP/IP interface library.  5           o  VMS Mail Utility Manual, part of the VMS >              documentation set, contains information about the              VMS Mail utility.                                                       viii                     A           _______________________________________________________   /    1      Preparing to Install Message Exchange       ?           This chapter describes the steps that should be taken <           prior to installing the Message Exchange software.  L           __________________________________________________________________      1.1    Software License Key  <           MX requires a license key to enable its operation.<           If you have not obtained a license key for MX from:           MadGoat, the installation kit will automatically>           register a temporary evaluation license for you. The8           temporary key enables the product for 30 days.  L           __________________________________________________________________      1.2    Prerequisite Software   >           MX requires VAX/VMS version V5.2 or later or OpenVMS=           Alpha V1.5 or later to run. The SMTP support option >           requires a NETLIB-supported TCP/IP package (refer to<           the NETLIB release notes for further information).@           SMTP-over-DECnet requires DECnet, but does not require?           either NETLIB or any TCP/IP package. The Jnet support >           option requires Jnet V3.5 or later. The UUCP support3           option requires DECUS UUCP V1.1 or later.   L           __________________________________________________________________  0    1.3    Upgrading from Previous Versions of MX  <           If you are currently running MX V4.0 or later, you=           can install MX V5.1 as an upgrade; the installation =           procedure will automatically detect this and notify =           you that it is upgrading your current installation. ?           If you are currently running a version of MX prior to             V4.0, you must either:  @           1  upgrade to MX V4.0, V4.1, V4.2, or V5.0 first, then.              install MX V5.1 as an upgrade; or  A                                                               1-1          /           Preparing to Install Message Exchange           /           2  install MX V5.1 in a new location.   L           __________________________________________________________________  ,    1.4    VMScluster Support and MX Clusters  6           MX fully supports VMScluster systems in both7           homogeneous and heterogeneous configurations.   <           An "MX cluster" consists of one or more VMScluster1           nodes that meet the following criteria:   7           1  All nodes in the MX cluster share one User =              Authorization File (SYSUAF.DAT) and one VMS Mail ,              profile (VMSMAIL_PROFILE.DATA).  A           2  All nodes have mounted the disk that contains the MX $              images and directories.  >           3  All nodes have mounted the disk that contains the              message queue.   ?           4  If MX is to be used for network mail, at least one =              node in the MX cluster is running the networkings<              software required for each type of network link              desired.   =           5  The logical name MAIL$SYSTEM_FLAGS is defined tod>              a value of at least 3. (Refer to VMS Mail Utility;              Manual for further information on MAIL$SYSTEM_               FLAGS.)  <           For homogeneous VMScluster systems, the MX cluster;           will usually include all nodes in the VMScluster.g  %           ___________________________n  =    1.4.1  Answering VMScluster-related Installation Questions   =           The MX installation procedure automatically detectsi>           that you are in a VMScluster and will ask additional:           questions during installation about where in the;           cluster each installed MX processing agent shouldl;           run. The processing agents are programs which aren>           run as detached processes. They can be run on any or  
           1-2t ,  a    A                             Preparing to Install Message Exchangea          <           all nodes in the cluster (following the MX Cluster<           guidelines outlined above), and will automatically;           cooperate in providing their respective services.s  ?           When asked to provide a cluster node name for runningt?           the processing agents, be sure to specify the SCSNODEn@           name (or use an asterisk ("*") to have an agent run on$           all nodes in the cluster).  %           ___________________________d  3    1.4.2  Mixed VMSclusters (VAX and Alpha systems)i  >           Mixed VMSclusters that consist of both VAX and Alpha=           systems are fully supported by MX. The MX directoryu=           tree can be shared by both systems if it resides onr?           a common disk. When the VAX and Alpha systems share aw>           common MX directory, agents may be run on both types           of systems.G  @           When MX determines that the node is part of a cluster,>           it will ask whether or not the cluster contains both>           VAX and Alpha systems. Additional questions relating:           to mixed-VMScluster support will be asked if the           cluster is mixed.e  A           Note: MX must be installed twice on a mixed-VMScluster: @           once on a VAX system and once on an Alpha system. This<           is necessary because the MX executables are linked<           during the MX installation. Installing MX on a VAX>           produces the VAX executable images and installing it0           on an Alpha produces the Alpha images.  <           If the VAX and Alpha systems will be sharing an MX=           directory, it is only necessary to install the full >           MX kit on one of the systems (VAX or Alpha). For the?           second installation on the other type of machine, youn<           can elect to install only the executables for that?           machine. The installation will prompt for the type of @           installation to be performed. Choosing to install only?           the executables on the second installation eliminatesG@           the need to specify MX configuration information (host           name, etc.) again.  A                                                               1-3O A  L    /           Preparing to Install Message Exchange           >           The MX_ROOT: directory tree contains two directories@           for executables: MX_ROOT:[EXE] for VAX executables and@           MX_ROOT:[ALPHA_EXE] for Alpha executables. The logical<           MX_EXE:, which is used in all examples below, will?           automatically be defined appropriately on each system            in the cluster._  L           __________________________________________________________________  $    1.5    Determining Your Node Name  7           MX requires two node names for its operation.n:           The first, the MX cluster name, is used by MX to1           coordinate access to the message queue.   =           o  For a stand-alone (non-clustered) system, the MX A              cluster name usually corresponds to your DECnet node A              name. If you are not running DECnet, you can use any #              1-to-6 character name._  @           o  For a VMScluster system, the MX cluster name should?              correspond to your DECnet cluster alias node name._;              If do not have a cluster alias, you should use <              the DECnet node name of one of the nodes in the              MX cluster.  ;           The second 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 your host has a registered Internet >           domain name, you should use that name. If you are on?           BITNET or a UUCP network and do not have a registered =           Internet domain name, you should use your BITNET or_?           UUCP host name. Otherwise, you should use a host name =           that fits with the naming conventions at your site._  <           In an MX cluster environment, MX will use a single=           network name to identify the entire cluster. If you_?           have several nodes with their own network node names,V?           and your networking software does not support the use_<           of a cluster-wide alias, you could either pick one<           node to be the "master" for E-mail purposes or use  
           1-4          A                             Preparing to Install Message Exchange_          <           the MX_VMSMAIL_FROM_FORMAT logical name (described<           in Message Exchange Management Guide) to have each>           node insert its own host name in return addresses on<           outgoing messages. What you do will depend on your%           network software and setup.   L           __________________________________________________________________  ,    1.6    Accessing the Online Release Notes  9           MX provides online release notes, which you can 6           display or print by using VMSINSTAL with the:           OPTIONS N parameter. After the installation, you9           can read the release notes by printing the fileL;           SYS$HELP:MXvvn.RELEASE_NOTES, where "vvn" denotes_>           the version number of the software. For example, for;           version V3.0 of MX, the file name would be MX030.   :           The release notes for NETLIB are provided in the<           file SYS$HELP:NETLIBvvn.RELEASE_NOTES, where "vvn">           identifies the version of NETLIB shipped with the MX>           distribution kit. This file is created during NETLIB>           installation and is not accessible through VMSINSTAL           OPTIONS N.  L           __________________________________________________________________      1.7    Mailer AccountsF  >           You can run the detached processes MX uses under the=           SYSTEM account, or, if you prefer, under a separate.           "mailer" account.   8           Note, however, that using a mailer account may;           complicate the process for starting up MX on your ?           system; see Section 3.4 for further information on MXX           startup procedures.   ?           If you intend 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:   4           o  a username of eight characters or less.  6           o  full batch access, no interactive access.  A                                                               1-5          /           Preparing to Install Message Exchange           A           o  network access, only if SMTP-over-DECnet is used andT>              you do not wish to create a dedicated account for)              the SMTP-over-DECnet object.   ?           o  the INTERNET_ACCESS identifier, if needed for CMU-               Tek TCP/IP access.   A           o  the ARPANET_ACCESS identifier, if needed for CMU-Tek               TCP/IP access.   =           o  the following authorized and default privileges:.;              CMKRNL, SYSNAM, DETACH, WORLD, PHY_IO, SYSPRV, =              SYSLCK, EXQUOTA, TMPMBX, and NETMBX. (BYPASS mayl3              also be required if using DECUS UUCP.)M  6           o  a subprocess limit (PRCLM) of at least 1.  8           o  no detached process limit (MAXDETACH of 0).  <           o  a login directory that is owned by the account.  =           Figure 1-1 shows the UAF entry for a typical Mailer_           account.  %           ____________________________  1    1.7.1  SMTP-over-DECnet/X.25 Dedicated Account   9           If you intend to use the MX SMTP-over-DECnet or_=           SMTP-over-X.25 support, you may want to establish a ;           special server account to be used exclusively for =           the DECSMTP and X25_SMTP DECnet objects. If so, you =           should ensure that the accounts have NETWORK access ?           and the privileges TMPMBX, NETMBX, SYSPRV, and SYSLCK =           (both authorized and default). Figure 1-2 shows the_;           UAF entry for a typical SMTP-over-DECnet or SMTP- <           over-X.25 server account. See Section 3.9 for more?           information on setting up the MX SMTP-over-DECnet and !           SMTP-over-X.25 support._  
           1-6          A                             Preparing to Install Message Exchange         /           Figure 1-1  Mailer Account attributes A           _______________________________________________________   N           Username: MAILER                           Owner:  MX Mailer accountQ           Account:  NETSTUF                          UIC:    [1076,76] ([MAILER])_F           CLI:      DCL                              Tables: DCLTABLES&           Default:  USER_DISK:[MAILER]           LGICMD:   NL:_&           Login Flags:  Disctly Defcli-           Primary days:   Mon Tue Wed Thu FriS5           Secondary days:                     Sat Sun P           Primary   000000000011111111112222  Secondary 000000000011111111112222P           Day Hours 012345678901234567890123  Day Hours 012345678901234567890123P           Network:  -----  No access  ------            -----  No access  ------P           Batch:    ##### Full access ######            ##### Full access ######P           Local:    -----  No access  ------            -----  No access  ------P           Dialup:   -----  No access  ------            -----  No access  ------P           Remote:   -----  No access  ------            -----  No access  ------N           Expiration:            (none)    Pwdminimum:  3   Login Fails:     0H           Pwdlifetime:           (none)    Pwdchange:             (none)Z           Last Login:            (none) (interactive), 19-JAN-1990 14:38 (non-interactive)C           Maxjobs:         0  Fillm:        60  Bytlm:        36000 C           Maxacctjobs:     0  Shrfillm:      0  Pbytlm:           0 C           Maxdetach:       0  BIOlm:        20  JTquota:       1024_C           Prclm:           4  DIOlm:        18  WSdef:          512mC           Prio:            4  ASTlm:       325  WSquo:          512dC           Queprio:       100  TQElm:        10  WSextent:      2048 C           CPU:        (none)  Enqlm:       600  Pgflquo:      25600_            Authorized Privileges:Q             CMKRNL SYSNAM DETACH TMPMBX WORLD EXQUOTA NETMBX PHY_IO SYSPRV SYSLCKd           Default Privileges:CQ             CMKRNL SYSNAM DETACH TMPMBX WORLD EXQUOTA NETMBX PHY_IO SYSPRV SYSLCKbG           Identifier                         Value           AttributesCQ             ARPANET_ACCESS                   %X80010042      NORESOURCE NODYNAMICnQ           __INTERNET_ACCESS__________________%X80010043______NORESOURCE NODYNAMICb  L           __________________________________________________________________  -    1.8    Installation Procedure Requirementsy  9           Before installing MX, ensure that the following_:           privileges, resources, and requirements are met:  A                                                               1-7n m  o    /           Preparing to Install Message Exchange         @           Figure 1-2  SMTP-over-DECnet server account attributesA           _______________________________________________________   V           Username: DNSMTP_SRV                       Owner:  MX DECSMTP object accountU           Account:  NETSTUF                          UIC:    [1076,77] ([DNSMTP_SRV]) F           CLI:      DCL                              Tables: DCLTABLES*           Default:  USER_DISK:[DNSMTP_SRV]           LGICMD:   NL: &           Login Flags:  Disctly Defcli-           Primary days:   Mon Tue Wed Thu Frin5           Secondary days:                     Sat SungP           Primary   000000000011111111112222  Secondary 000000000011111111112222P           Day Hours 012345678901234567890123  Day Hours 012345678901234567890123P           Network:  ##### Full access ######            ##### Full access ######P           Batch:    -----  No access  ------            -----  No access  ------P           Local:    -----  No access  ------            -----  No access  ------P           Dialup:   -----  No access  ------            -----  No access  ------P           Remote:   -----  No access  ------            -----  No access  ------N           Expiration:            (none)    Pwdminimum:  3   Login Fails:     0H           Pwdlifetime:           (none)    Pwdchange:             (none)Z           Last Login:            (none) (interactive), 19-JAN-1990 14:38 (non-interactive)C           Maxjobs:         0  Fillm:        60  Bytlm:        36000LC           Maxacctjobs:     0  Shrfillm:      0  Pbytlm:           0tC           Maxdetach:       0  BIOlm:        20  JTquota:       1024 C           Prclm:           4  DIOlm:        18  WSdef:          512eC           Prio:            4  ASTlm:       325  WSquo:          512rC           Queprio:       100  TQElm:        10  WSextent:      2048_C           CPU:        (none)  Enqlm:       600  Pgflquo:      25600i            Authorized Privileges:'             TMPMBX NETMBX SYSPRV SYSLCKe           Default Privileges:aA           __TMPMBX_NETMBX_SYSPRV_SYSLCK__________________________u  %           o  Operating System Version   ;              MX V5.1 runs on OpenVMS VAX (VAX/VMS) V5.2 and 6              higher and OpenVMS Alpha V1.5 and higher.  %           o  Layered Product Versionsk    
           1-8r         A                             Preparing to Install Message Exchangep          =              Refer to the NETLIB release notes for details on_;              TCP/IP requirements. For Jnet support, MX V5.1p>              requires Jnet V3.5 or later. For UUCP support, MX>              V5.1 requires DECUS UUCP V1.1 or later. For SMTP-A              over-X.25, MX V5.1 requires VAX P.S.I. or VAX P.S.I.m"              Access V4.2 or later.  @           o  all the normal privileges and quotas of the default              SYSTEM account.  <           o  approximately 5 minutes to 1 hour, depending on@              your system configuration, distribution medium, and              options selected.  >           o  On Alpha systems, 90 free global sections and 850A              free global pagelets. On VAX systems, 30 free globals0              sections and 405 free global pages.  A           o  For SMTP support (over TCP/IP): on Alpha systems, an_<              additional 40 free global sections and 300 free;              global pagelets; on VAX systems, an additionalr8              10 free global sections and 170 free global;              pages. To include NETLIB support for more than =              one TCP/IP package, you will need even more freet=              global sections and global pages; see the NETLIBe0              documentation for more information.  ?           o  approximately 30,000 free blocks on a disk for use ?              during the installation procedure; this can be the ?              system disk or a disk specified with the VMSINSTALv              AWD option.  ?           o  approximately 5 free blocks on the system disk foro              permanent files.e  ?           o  approximately 4,000 free blocks on any disk for MXk=              base software, and the following additional freei              disk blocks:   :             o  approximately 1,000 free blocks for each MX(                optional transport agent.  :             o  approximately 1,000 free blocks for mailing(                list/file server support.  A                                                               1-9          /           Preparing to Install Message Exchange           5             o  approximately 7,000 free blocks for MXM                documentation.u  ?             o  approximately 250 free blocks for the MX examplee                files.y  9             o  approximately 2,300 free blocks for the MXs.                contributed files and programs.  ;           o  a minimum of 5,000 free blocks on any disk for !              message queue space.e  @           o  if you are running CMU-Tek TCP/IP, the value of the;              SYSGEN parameter MAXBUF must be at least 2300.   L           __________________________________________________________________  &    1.9    Saving Current Configuration  ?           If MX is already installed on your system, you should 9           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:  0                            $ MCP :== $MX_EXE:MCPd                            $ 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.                               1-10 r  c                A           _______________________________________________________A  %    2      Installing Message Exchangeo      ;           MX uses VMSINSTAL for installation. If you do nots:           know how to use VMSINSTAL, you should first read>           the chapter on installing software in the VMS System?           Manager's Manual. For the installation, you should bei=           logged into the SYSTEM account, or another suitablye           privileged account.m  A           Note: MX must be installed twice on a mixed-VMScluster:u<           once on a VAX system, and once on an Alpha system.:           This is necessary because the MX executables are?           linked during the MX installation. Installing MX on a ?           VAX produces the VAX executable images and installingl8           it on an Alpha produces the Alpha images. When>           installing on a mixed VMScluster, be sure to specify>           a device name for the MX installation directory that@           is valid on both the VAX and Alpha systems, and refers=           to the same device in both cases. Using a platform- ;           specific logical name, such as SYS$SYSDEVICE will )           cause the installation to fail.o  L           __________________________________________________________________      2.1    Shutting down MX  ?           If any MX processes are currently running, you shouldp:           stop them before installing a new version of MX,<           including any SMTP servers (which are not shutdown?           with the MCP SHUTDOWN command in versions of MX priors;           to V2.2-2). Unprocessed mail should remain queuede/           until you start the new MX processes.b        A                                                               2-1o l       %           Installing Message Exchange,        L           __________________________________________________________________      2.2    Invoking VMSINSTAL  )           Invoke VMSINSTAL to install MX._  >                            $ @SYS$UPDATE:VMSINSTAL MXvvn ddcu:  =           Substitute the appropriate values for vvn and ddcu.s  Z                                     VAX/VMS Software Product Installation Procedure V5.5-2  6                            It is dd-Mmm-yyyy at hh:mm.J                            Enter a question mark (?) at any time for help.  <           If there are any users logged into the system, you           will see the message  Y                            %VMSINSTAL-W-ACTIVE, The following processes are still active: .                            ...process names...  >           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 your network links are shut           down.e  A                            * Do you want to continue anyway [NO]?a  .           If you wish to continue, answer YES.  Y                            * Are you satisfied with the backup of your system disk [YES]?m  ?           If you feel comfortable with your system disk backup,e?           answer YES. Otherwise, answer NO, perform the backup,m2           then restart the installation procedure.  L           __________________________________________________________________  0    2.3    Mixed VAX and Alpha VMScluster Support  >           If your system is part of a VMScluster that includes>           both VAX and Alpha systems, you will need to install=           MX twice: once on a VAX, and once on an Alpha. Thist:           is required because the MX executable images are=           linked during the installation and cross-linking is ;           not supported. The MX installation will display ad<           message indicating the possible need to install MX=           twice and will ask you if the cluster includes both   
           2-2          A                                       Installing Message ExchangeV          ;           VAX and Alpha systems that will share a common MXg           directory:  Y                            *Does this VMScluster include both VAX and Alpha systems [NO]?g  =           If you answer NO to this question, the installationt<           proceeds to the next step (Section 2.4). Answering;           YES will cause the installation to ask a few more            questions:  ]                            *Will the VAX and Alpha systems share a common MX directory [YES]? g                            *Has MX V5.0 already been installed on an Alpha system in this cluster [NO]?l  <           If they will share a common MX directory, you only?           need to configure MX during one of the installations.h:           For example, if you install MX on a VAX first as=           in the example above, you will have to provide siteo?           configuration information (described in the followingE>           sections). If you've already installed MX on another<           system in the cluster, answering YES to the second=           question will cause the following prompt to appear:c  R                            *Do you wish to install only the VAX executables [YES]?  <           You should answer YES to this question only if you=           have already installed the current version of MX ons>           another system in the cluster. Answering YES resulst&           in one further confirmation:  H                               Only the VAX executables will be installed  2                            *Is this correct [YES]?  L           __________________________________________________________________      2.4    Installation Options             The next question is  \                            * Do you want to purge files replaced by this installation [YES]?  :           If this is the first time you have installed MX,?           answering NO to this question can save some time whent8           the MX files are moved into their directories.  A                                                               2-3          %           Installing Message Exchangen        L           __________________________________________________________________      2.5    Component Selection   ;           A menu of MX components appears next, and you are 4           asked to enter your choices from the menu:  7                                 1. [ ] Base MX software =                                 2. [ ] NETLIB network supporti=                                 3. [ ] SMTP interface support =                                 4. [ ] Jnet interface support =                                 5. [ ] UUCP interface support ?                                 6. [ ] SMTP-over-DECnet support =                                 7. [ ] SMTP-over-X.25 supportsF                                 8. [ ] Site-provided interface supportG                                 9. [ ] Mailing List/File Server supportd4                                10. [ ] DocumentationA                                11. [ ] Example files and programs_J                                12. [ ] User-contributed files and programs  +                                13.     Exito  4                            *       Your choice [13]:  ?           Note: When installing MX on an Alpha system, the menu =           items for those agents whose third-party transportse?           have not been ported to Alpha (DECUS UUCP, X.25) willN           not be displayed.   =           Enter the number corresponding to the component yout>           wish to install; multiple components may be selected<           by entering the numbers as a comma-separated list.;           The menu is displayed again after each selection,o=           with asterisks appearing next to the items you haveM?           selected; selecting a component twice removes it from            the selection list.s  <           When you are upgrading to a new version of MX, the:           installation procedure will look at your current6           configuration to automatically determine the:           components that should be installed. If you wish=           to omit any of those components that were selected,(>           simply select them again to remove it from the list.  
           2-4S         A                                       Installing Message Exchangeo          ;           When you have selected the components you want tor=           install, enter 13 to exit the menu. Your selections ?           are displayed again and you are asked to confirm your1           selections:a  S                                You have selected the following optional components::  @                                (selected components listed here)  3                            * Is this correct [YES]?#  @           Press RETURN to continue the installation, or enter NO+           to return to the components menu.              Component Notes-  >           You must install the Base software component if this9           is your first installation of MX, or if you are <           upgrading from a previous version of MX. The other=           components are optional and may be installed at anyh@           time after the Base component is installed. If you re->           install the Base component, you must also re-install=           all desired optional components as well, except for 8           documentation, examples and contributed files.  >           If you elect to install SMTP support, NETLIB support>           will automatically be installed as well. If you have=           already installed the NETLIB support component, you @           can disable the NETLIB re-installation by re-selecting           it on the menu.   L           __________________________________________________________________  %    2.6    Base Software ConfigurationS  <           If you are installing the Base software component,?           the saveset containing the Base support files will beT?           loaded and you will be asked some questions regardingi1           the configuration of the Base software.u  A                                                               2-5R U       %           Installing Message Exchange_        %           ___________________________I  $    2.6.1  Placing the MX Directories  @           A brief description of the directory structure used by-           MX is displayed, and you are asked:s  _                            * 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._  >           Note: If you are installing MX on a mixed VMScluster9           where VAX and Alpha systems will share a common:7           directory, be sure you specify a disk that isS=           common to both types of systems. The default device @           (SYS$SYSDEVICE:) may not be appropriate, especially if@           you do not cross-mount your VAX and Alpha system disks5           between systems of different architectures.   =           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]]:7  <           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, any6           files already in the queue will be retained.  >           Note: If you are installing MX on a mixed VMScluster9           where VAX and Alpha systems will share a common 7           directory, be sure you specify a disk that isa=           common to both types of systems. The default devicee@           (SYS$SYSDEVICE:) may not be appropriate, especially if@           you do not cross-mount your VAX and Alpha system disks5           between systems of different architectures.   ?           MX actually uses 10 subdirectories under the MX queue @           directory. Those directories are automatically created(           by the installation procedure.  
           2-6     1    A                                       Installing Message Exchanger        %           ___________________________0  4    2.6.2  Selecting the Size of the MX Message Queue  @           The MX queueing subsystem uses a fixed-size sequential@           file for the MX queue. The size of the file determines@           the number of messages that can be in the queue at any=           one time. The size of the file can be extended at a 8           later date using the MCP command QUEUE EXTEND.  >           For each message, one block is required. To allow up?           to 5,000 messages to be in the queue at any one time, ;           the queue file must be slightly larger than 5,000p@           blocks. The required file size depends heavily on your@           site's e-mail traffic. For a workstation that normally>           receives a couple of hundred messages a day, a queue<           file of 100 blocks or less is probably sufficient.  @           For sites with a lot of mail traffic, a size of 5,000-<           10,000 blocks is recommended. If disk space is not>           a problem, you can specify as many as 131,072 (128K)>           messages, which is the maximum number MX is designed           to handle.  @           The installation prompts you for the size of the file:  T                            * Maximum number of entries to allow in the queue [5000]:  L           __________________________________________________________________  '    2.7    NETLIB Component Installation   >           If you are installing the NETLIB component (required@           for SMTP support using TCP/IP), the saveset containing>           the NETLIB support files will be loaded and you will@           be asked some questions regarding the configuration of           NETLIB.T  >           The NETLIB installation procedure displays a menu of=           supported TCP/IP packages and asks for the packagesa;           for which you wish to install NETLIB support. The =           list for Alpha and VAX systems may not be the same,n>           depending on the number of TCP/IP packages supported           on each platform.   A                                                               2-7A o  o    %           Installing Message Exchangec          1                                 1. [ ] CMU TCP/IP >                                 2. [ ] Digital TCP/IP Services5                                 3. [ ] Cisco MultiNetn6                                 4. [ ] Process TCPware9                                 5. [ ] Attachmate PathWayo  +                                 6.     Exito  3                            *       Your choice [6]:l  ;           The installation procedure attempts to pre-select <           those packages which appear to be installed on the9           system. Selections are made just as from the MXp<           optional components menu. When you exit this menu,<           your selections are displayed and you are asked to           confirm them:   N                                You have selected the following TCP/IP support:  7                                  (packages listed here)n  3                            * Is this correct [YES]?   ?           Press RETURN to continue or enter NO to return to theC           menu.f  =           If you elected to install support for more than one >           TCP/IP package, you are then asked to select the one>           that will be used by default when the NETLIB startup           procedure executes:l  Z                                You have selected support for more than one TCP/IP package.X                                You must now select which is to be used by default on the.                                current system.  7                                  (packages listed here)   /                            *       Your choice:_  ;           Select the package you wish to use by default. IfX?           you need to have different packages used on differenta<           systems in a VMScluster, you will need to edit the:           NETLIB_STARTUP command procedure as described in           Section 3.7.  
           2-8_ _  _    A                                       Installing Message ExchangeX          ?           The final NETLIB installation question asks where the 6           NETLIB shareable libraries should be placed:  _                            * Where should the NETLIB libraries be placed [SYS$COMMON:[SYSLIB]]:u  8           If you do not wish to install the libraries in;           SYS$LIBRARY, you may specify any other device and "           directory on the system.  =           If you are installing MX on a VMScluster containingp<           both VAX and Alpha systems, it is recommended that=           you install the NETLIB libraries in the appropriaten<           MX executable directory (MX_ROOT:[EXE] for VAX and=           MX_ROOT:[ALPHA_EXE] for Alpha). If you do not placeg?           them there, you may have to modify the NETLIB startups>           procedure to locate the proper files for each system           type.   L           __________________________________________________________________  $    2.8    The Installation Completes  @           After the configuration questions and NETLIB component<           installations, which always require input from the;           installer, all selected components are installed.28           Files are copied from the each save set of the9           installation kit and the appropriate images aree>           linked, then all installed files are copied to their?           destination directories. Informational messages abouto<           the individual components are displayed as needed.                    A                                                               2-9                      A           _______________________________________________________   '    3      Post-Installation Information       ;           This chapter contains important information about_:           setting up MX configuration and startup options.  L           __________________________________________________________________  "    3.1    License Key Registration  :           If the installation procedure did not detect the>           presence of a registered license key for MX, it will?           ask you if you have a license key. If you do, it will @           invoke MX_LICENSE.COM so you can enter the license key?           data. If you do not, it will automatically register ay@           temporary evaluation license key, which is enables the           product for 30 days.  L           __________________________________________________________________      3.2    Configuring MX  =           When installing MX for the first time, or upgradingr=           from a previous version, the installation procedurew4           automatically invokes the MXCONFIG command=           procedure to assist in creating or updating your MX]>           configuration files. If you are adding options to an>           existing MX installation, and have already created a>           configuration database, this step is skipped. If you=           want to create a new MX configuration from scratch, >           you may use the MXCONFIG command procedure to create=           an MX configuration database after the installation_           completes:  =                            $ @SYS$STARTUP:MX_STARTUP LOGICALS -                            $ @MX_DIR:MXCONFIGa  A                                                               3-1s l       '           Post-Installation Informationa          ?           MXCONFIG prompts you for some basic information about <           host names, agents, and your network connectivity,9           and creates an MCP command file to create an MX @           configuration database. You can use MXCONFIG to define>           all routing information and Postmaster aliases for a@           typical Internet- or BITNET-connected 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.u  L           __________________________________________________________________  #    3.3    Establishing a Postmastere  ;           All Internet and BITNET sites that use electronicl:           mail must be able to accept mail to the username;           Postmaster. BITNET sites must also accept mail tos>           the username POSTMAST (Postmaster truncated to eight@           characters). If you do not have a real username called@           POSTMASTER on your system, you should either establish4           aliases with the MCP DEFINE ALIAS command:  C                            MCP> DEFINE ALIAS Postmaster "user@host" C                            MCP> DEFINE ALIAS POSTMAST   "user@host"i  >           (substituting appropriate values for user and host),?           or use the SET FORWARD command in VMS Mail to forwarda.           mail from Postmaster to a real user:  A                            MAIL> SET FORWARD/USER=POSTMASTER usermA                            MAIL> SET FORWARD/USER=POSTMAST   userl  :           Even if you are not connected to the Internet or@           BITNET, it is still a good idea to create a Postmaster)           username or forwarding address.   L           __________________________________________________________________  -    3.4    Adding MX Startup to System Startupy  =           The startup procedure for MX may vary depending on:   5           o  you are running in a cluster environment_  A           o  you are running MX processes under a separate mailera              account  
           3-2t         A                                     Post-Installation Informationh          >           In either case, remember that if you are running the@           MX SMTP-over-TCP/IP support, you should start MX after@           you start your TCP/IP software, and if you are running=           the MX Jnet support, you should start MX before you <           start Jnet (although the Jnet interface is started,           during or after the Jnet startup).  =           If you are running L-Soft International's LISTSERV,e<           you must define the LISTSERV logicals, but not the3           process, before starting MX. For example:t  G                            $ @SYS$STARTUP:LISTSERV_STARTUP.COM LOGICALS 8                            $ @SYS$STARTUP:MX_STARTUP.COM>                            $ @SYS$STARTUP:LISTSERV_STARTUP.COM             Standalone Systems  ?           If you intend to run MX under the SYSTEM account, all[=           you need to add to your system startup procedure is[           the command:  4                            $ @SYS$STARTUP:MX_STARTUP  ?           If you are using a separate mailer account, you wouldi-           use the following commands instead:   =                            $ @SYS$STARTUP:MX_STARTUP LOGICALS N                            $ SUBMIT/NOPRINT/USER=mailer SYS$STARTUP:MX_STARTUP  <           For mailer substitute the username you assigned to           your mailer account.             Clustered Systems   >           In a cluster environment, as long as you are running@           MX under the SYSTEM account, the startup command is as)           easy as for standalone systems:o  4                            $ @SYS$STARTUP:MX_STARTUP  9           However, if you are running MX under a separatey@           mailer account, how each node in the cluster starts MX>           depends on whether or not it will run one or more of@           the MX processes (as selected during MX installation).  A                                                               3-3     h    '           Post-Installation Informationv          8           If the node will not run one or more of the MX:           processing agents, such as a satellite node in a=           Local-Area or Mixed-Interconnect VMScluster, all ito.           needs to start up MX is the command:  4                            $ @SYS$STARTUP:MX_STARTUP  <           which just defines the necessary logical names and?           install the necessary images for interfacing VMS Maill           with MX.  >           If the node will run one or more MX processes, those:           processes need to be started up under the mailer<           account's username, so you would use the commands:  =                            $ @SYS$STARTUP:MX_STARTUP LOGICALSn\                            $ SUBMIT/NOPRINT/USER=mailer/QUEUE=nodeque SYS$STARTUP:MX_STARTUP  =           substituting the mailer account name for mailer ando:           the name of a batch queue that runs on the local           system for nodeque.   %           ___________________________e      3.4.1  MX Jnet Startup   ;           If you installed MX Jnet support, you should editr>           the JAN_SYS:JANSITE.COM or JAN_SYS:JANSITECOMMON.COM:           command procedure for your system to include the           following commands:t  b                            $ DEFINE/SYSTEM/EXEC JAN_MFSDISP MX_EXE:MX_MFSDISP   ! under cold_startR                            $ SUBMIT/NOPRINT/QUEUE=batchque/USER=mailer/PARAM=JNET-T                                          SYS$STARTUP:MX_STARTUP   ! under warm_start  >           In a cluster environment, the queue name you specify=           for batchque must be a batch queue that executes on >           the same node that the Jnet startup is executing on.  3           You should also add the following to JAN_w<           SYS:JANSITESTOP.COM to ensure a proper shutdown of)           MX Jnet when Jnet is shut down:h  4                            $ MCP :== $MX_EXE:MCP.EXE.                            $ MCP SHUTDOWN JNET  
           3-4_ _  _    A                                     Post-Installation Information           @           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 the4           invocation of MX_STARTUP in JANSITECOMMON:  J                            $ DEFINE/SYSTEM/EXEC MX_LOCAL_MFSDISP file-spec  9           MX_MFSDISP will automatically invoke your local_?           mail/file dispatcher for all incoming Jnet files that '           it does not transfer into MX.u  %           ___________________________d      3.4.2  Example   ?           As an example, take a homogeneous VMScluster with twoa?           nodes, NODE1 and NODE2, each with a TCP/IP connectionc>           and a BITNET connection, and several satellite nodes?           that will just be used for sending and receiving maile<           by users (i.e., no MX processes will run on them).  ?           Both NODE1 and NODE2 have batch queues, called NODE1_X9           BATCH and NODE2_BATCH, respectively. The mailerm%           account username is MAILER.t  <           The commands to be added to SYS$MANAGER:SYSTARTUP_?           V5.COM, after TCP/IP startup and before Jnet startup,E           would be:i  9                            $ NODE = F$GETSYI ("NODENAME") K                            $ IF NODE .NES. "NODE1" .AND. NODE .NES. "NODE2" !                            $ THENd7                            $    @SYS$STARTUP:MX_STARTUP !                            $ ELSEed                            $    SUBMIT/NOPRINT/USER=MAILER/QUEUE='NODE'_BATCH SYS$STARTUP:MX_STARTUP"                            $ ENDIF  7           The commands to be added to the specific JAN_ 7           SYS:JANSITE.COM for NODE1 and NODE2 would be:   9                            $ NODE = F$GETSYI ("NODENAME")yM                            $ DEFINE/SYSTEM/EXEC JAN_MFSDISP MX_EXE:MX_MFSDISPyW                            $ SUBMIT/NOPRINT/USER=MAILER/QUEUE='NODE'_BATCH/PARAM=JNET -aB                                             SYS$STARTUP:MX_STARTUP  A                                                               3-5          '           Post-Installation Informationc        L           __________________________________________________________________  /    3.5    Adding MX Shutdown to System Shutdown   9           To ensure that MX agent processes are shut down 7           cleanly when the system is shut down, add thec7           following lines to SYS$MANAGER:SYSHUTDWN.COM:   /                            $ MCP := $MX_EXE:MCP )                            $ MCP SHUTDOWN   <           This will notify any agent processes on the system@           that they should shut down without affecting the agent2           processes on other nodes in the cluster.  L           __________________________________________________________________  %    3.6    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 do not like "EST" and "EDT" as time zone names,5>           you must make sure that at least one of several time7           zone logicals is defined in SYSTARTUP_V5.COM.   %           ___________________________h  1    3.6.1  The Product-Specific Time Zone Logicalsa  <           MX checks for the existence of one of several time;           zone logicals that specify the timezone string toe=           be used when generated RFC822 mail message headers. >           Because most of the delivery transports (Jnet, DECUS@           UUCP, the TCP/IP implementations, etc.) already define:           time zone logicals compatible with MX, it is not3           necessary to define MX-specific logicals.   >           On OpenVMS V6.0 and later, MX automatically uses the=           logical name SYS$TIMEZONE_DIFFERENTIAL as the basisl>           for its time zone strings. If you have not correctly0           set that logical name, use the command  ;                            $ @SYS$MANAGER:UTC$CONFIGURE_TDFa  
           3-6c o  t    A                                     Post-Installation Informationi          8           to set the timezone differential. If your site@           observes Daylight Savings Time, you may need to adjust=           the timezone differential each time you adjust yourd           system clock.   ;           On systems where SYS$TIMEZONE_DIFFERENTIAL is not <           defined (typically pre-V6.0 VMS), the value of the@           first logical defined in the following ordered list is.           used with no time-zone calculations.  $           MX_TIMEZONE             MX(           SYS$TIMEZONE_NAME       DECdts=           SYS$TIME_ZONE           DEC TCP/IP Services for VMSM0                                   (formerly UCX)0           MULTINET_TIMEZONE       TGV's MultiNet/           JAN_TIME_ZONE           Wingra's Jnet ,           UUCP_TIME_ZONE          DECUS UUCP:           WIN$TIME_ZONE           Wollongong's WIN/TCP and)                                   PathWayc  %           ___________________________   "    3.6.2  The MX Timezone Logicals  @           If you wish to define a specific timezone logical name9           for use by MX, you should define it as follows:s  @                            $ DEFINE/SYS/EXEC MX_TIMEZONE "tzstr"  =           where tzstr is a valid (RFC822-compliant) time zone <           designation, such as "-0500". No validity checking?           is performed on this string. Note that the string you ?           specify with MX_TIMEZONE is used verbatim. If you use:>           MX_TIMEZONE and you observe daylight savings time in@           your area, it is your responsibility for modifying the>           definition of MX_TIMEZONE as needed. You do not need%           to shut down MX to do this.       A                                                               3-7n k  t    '           Post-Installation Information         L           __________________________________________________________________  !    3.7    Interfacing with TCP/IPo  7           The SMTP interface uses the NETLIB transport- :           independent library to interface with the TCP/IP?           package or packages you have installed on the system.   %           ___________________________   '    3.7.1  Disabling Vendor SMTP Support   =           If your TCP/IP vendor provides SMTP support as part @           of its package, you should disable that support before           starting MX.  >           Note: The instructions provided below were valid for<           various versions of each vendor's software. Please=           consult your TCP/IP documentation for more accurate            instructions.s&                  _____________________.                  3.7.1.1  Disabling CMUIP SMTP<           For CMU-OpenVMS/IP (aka CMU-Tek TCP/IP), edit your7           INTERNET.CONFIG file and comment out the linea<           that begins with "WKS:25", then restart TCP/IP. In?           addition, you may wish to deassign the system logicalm           name TCP$SMTPSV.&                  _____________________1                  3.7.1.2  Disabling MultiNet SMTPt?           For MultiNet, use the Server Configuration Utility tom*           disable MultiNet's SMTP service:  6                            $ MULTINET CONFIGURE/SERVERH                            MultiNet Server Configuration Utility 2.2(25)U                            [Reading in symbols from SERVER image MULTINET:SERVER.EXE]uZ                            [Reading in configuration from MULTINET:SERVICES.MASTER_SERVER]5                            SERVER-CONFIG>DISABLE SMTP_0                            SERVER-CONFIG>RESTART-                            SERVER-CONFIG>EXITs  @           If the SMTP was previously enabled, you will also need=           to stop the MultiNet SMTP batch queue. For example:n  ;                            $ STOP/QUEUE MULTINET_SMTP_QUEUEv  
           3-8     n    A                                     Post-Installation Informationa        &                  _____________________0                  3.7.1.3  Disabling TCPware SMTP<           For TCPware, use the TCPware configuration utility<           to disable TCPware's SMTP server, if you installed/           TCPware-SMTP. For TCPware v3.0, type:   6                            $ @TCPWARE:CNFNET FULL SMTP  6           For versions of TCPware prior to v3.0, type:  9                            $ @TCPIP_ROOT:CNFNET FULL SMTPo             When asked  N                            Enter the number of listening SMTP-VMS servers [1]:  =           enter 0. When asked whether to restart SMTP, answere           YES.&                  _____________________,                  3.7.1.4  Disabling UCX SMTP>           VMS/ULTRIX Connection (in versions 1.0 through 1.3B)3           does not include any native SMTP support.n  >           DEC TCP/IP Services for VMS V2.x does include native<           SMTP support. To disable the UCX SMTP server under&           V2.x, perform the following:  8           o  Disable the currently running SMTP service:  9                                $ UCX DISABLE SERVICE SMTP_  3           o  Stop the UCX SMTP queues. For example:s  7                                $ STOP/QUEUE UCX_node_00m7                                $ STOP/QUEUE UCX_node_01   9           o  Modify the system startup (SYSTARTUP*.COM ind<              SYS$MANAGER:) procedure to not invoke UCX$SMTP_              STARTUP.COM.   :           For DEC TCP/IP Services for VMS V3.0 and higher,            perform the following:  1           o  Run the UCX configuration procedure:   <                                $ @SYS$MANAGER:UCX$CONFIG.COM  (           o  Select "Client components".  A                                                               3-9i a  t    '           Post-Installation Information                      o  Select "SMTP".G  ,           o  Answer YES to reconfigure SMTP.  '           o  Answer NO to disable SMTP. &                  _____________________;                  3.7.1.5  Disabling Wollongong PathWay SMTP >           To disable the SMTP server for Wollongong's PathWay,           follow these steps:   <           o  Edit the file TWG$TCP:[NETDIST.ETC]SERVERS.DAT.  =           o  Find the server description for the SMTP service >              and place pound signs (#)  in front of each line,>              including the blank lines preceding and following@              the SMTP server description. This marks those linesA              as comments and they will be ignored by INET_SERVERS                during its startup.  =           o  If the INET_SERVERS process is running, kill it._  ;           o  Restart INET_SERVER by executing the following               command:s  D                                $ @TWG$TCP:[NETDIST.MISC]INETSERV.COM  >           o  List the registered TCP/UDP services to make sure,              the SMTP service is not listed:  +                                $ netstat -as  :           o  You can now start the MX SMTP_SERVER process.  <           To prevent the PathWay SMTP server from restarting2           on the next system boot, comment out the5           SMTP_INIT line in the PathWay startup file, .           TWG$TCP:[NETDIST.MISC]STARTINET.COM.  ?           This procedure should permanently disable the PathWayi@           SMTP server. To reenable the PathWay SMTP server, undo=           all the edit changes, kill the MX SMTP_SERVER, killr7           the INET_SERVER, and restart the INET_SERVER.              3-10    I    A                                     Post-Installation InformationS        %           ___________________________v  '    3.7.2  Ensuring SMTP Server Restarts   =           The MX SMTP Server process automatically exits whent<           it detects the shutdown of the TCP/IP software. If?           you want to ensure that it starts back up again after >           restarting your TCP/IP software, you should create a3           command procedure for starting up TCP/IP:   5                            $ @vendor-supplied-startup e                            $ IF F$TRNLNM ("MX_EXE") .NES. "" THEN @SYS$STARTUP:MX_STARTUP SMTP_SERVER-  <           Substitute the name of the vendor-supplied startup>           procedure for your TCP/IP package in the first line.  %           ___________________________X  %    3.7.3  Enabling SMTP Kanji Supportr  4           The SMTP interface contains code that will=           automatically convert JIS Kanji character encoding, >           used on the Japanese Internet, to DEC Kanji encoding:           (and vice-versa). The conversion is performed on;           the body of any message passing into or out of MXI>           via SMTP. To enable this conversion, ensure that the?           following logical name definition is included in your >           system startup procedure prior to the startup of the           MX SMTP support:  E                            $ DEFINE/SYSTEM MX_SMTP_KANJI_SUPPORT TRUET  L           __________________________________________________________________      3.8    Interfacing with UUCPc  ?           If you have installed the support for DECUS UUCP, youu?           must ensure that DECUS UUCP calls MX to deliver mail.Y  @           If you are running DECUS UUCP v2.0 or higher, you must=           modify the UUCP configuration to define the logicale>           UUCP_UUXQT_DCL_RMAIL_MX. The logical should be added*           to UUCP_CFG:CONTROL. as follows:  A                                                              3-11b t       '           Post-Installation Informationm                                      !+t                            !a                            !       -- Make DECUS UUCP UUXQT_DCL procedure use MX to deliver mail.d                            !                            !- G                            UUCP_UUXQT_DCL_RMAIL_MX                 TRUE   <           For versions of DECUS UUCP prior to v2.0, you must;           modify the UUCP command procedure UUCP_BIN:UUXQT_h>           DCL.COM to accommodate the hook into MX. The section@           of the command file after the label DO_RMAIL should be           modified as follows:             The line that reads   R                            $        SET PROCESS/PRIVILEGE=(SYSPRV, DETACH, BYPASS)  =           should be modified to include the privilege SYSLCK:d  Z                            $        SET PROCESS/PRIVILEGE=(SYSPRV, DETACH, BYPASS, SYSLCK)  @           The corresponding line that turns off these privileges9           a few lines below should be similarly modified.l  >           The line that runs the mail message through the UUCP           mailer:   Q                            $        MAIL/PROTOCOL=UUCP_MAILSHR 'infile' "''addr'"   8           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 RMAIL5           symbol to the top of the command procedure.t  <           Note: UUCP must be started before MX in the system           startup sequence.l  L           __________________________________________________________________  *    3.9    SMTP Support for DECnet and X.25  @           If you elected to install support for SMTP-over-DECnet@           or SMTP-over-X.25, you must take some additional steps%           to configure DECnet and MX.              3-12 m  s    A                                     Post-Installation InformationE        %           ___________________________   2    3.9.1  Creating a DECnet Object for DECnet-SMTP  <           You must create a DECnet object called DECSMTP for9           establishing SMTP-over-DECnet connections, botht            incoming and outgoing.  ;           If you intend to accept incoming SMTP-over-DECnetc>           connections, you should establish an account (either<           your mailer account or a dedicated server account)@           for use with each DECnet object. See Section 1.7.1 for=           more information on the requirements for the DECnet            object account.M  ;           A DECnet object needs to be created to handle the >           incoming SMTP-over-DECnet connections and to map the?           DECSMTP object name to a DECnet object number. Choosef<           an unused DECnet object number. To see what object8           numbers are currently in use, use the command:  6                            $ MCR NCP SHOW KNOWN OBJECT  <           Assign the object name DECSMTP to an unused object:           number; the number used must be identical on all?           nodes on your network that use SMTP-over-DECnet (thisa8           example uses 254). In NCP, use these commands:  8                            NCP> PURGE OBJECT DECSMTP ALLR                            NCP> DEFINE OBJECT DECSMTP NUMBER 254 PROXY NONE FILE -d                            _NCP>    MX_EXE:DNSMTP_SERVER.EXE USER server-acct PASSWORD some-password6                            NCP> SET OBJECT DECSMTP ALL  @           You do not need to specify the FILE, USER, or PASSWORD<           parameters if you do not intend to accept incoming8           SMTP connections over DECnet. Be sure that the>           password in the DECnet database matches the password6           you set for the server account in AUTHORIZE.      A                                                              3-13  /  s    '           Post-Installation Informationo                     Using Proxies   >           Instead of storing the username and password for the:           server account in the DECnet database, you could=           grant access using DECnet proxies. Proxies give youA<           more control over who on the network has access to<           the object, and eliminate the need for storing the=           password to the server account in the DECnet objectD           database.o  =           Note: Using proxies allows the remote system accessO>           to all files the server account can access (by using@           regular DECnet file transfers with FAL). If you do not>           manage the remote system, it is recommended that you0           use DECnet objects instead of proxies.  ?           To enable proxy access to the DECSMTP object, use theY$           following commands in NCP:  8                            NCP> PURGE OBJECT DECSMTP ALLV                            NCP> DEFINE OBJECT DECSMTP NUMBER 254 PROXY INCOMING FILE -<                            _NCP>    MX_EXE:DNSMTP_SERVER.EXE6                            NCP> SET OBJECT DECSMTP ALL  @           Then in AUTHORIZE, create proxy entries for the mailer@           accounts on the other systems on the network that will3           be sending you mail via SMTP-over-DECnet:$  L                            UAF> ADD/PROXY remote::mailer server-acct/DEFAULT  >           For remote::mailer substitute the DECnet node of the>           remote system and the username of the mailer account=           on that system. For server-acct substitute the name_;           of the server account you set up for use with the6           DECnet-SMTP object.                      3-14 i  h    A                                     Post-Installation Information         %           ___________________________t  0    3.9.2  Creating a DECnet Object for X.25-SMTP  =           You must create a DECnet object called X25_SMTP for @           establishing SMTP-over-X.25 connections, both incoming           and outgoing.   9           If you intend to accept incoming SMTP-over-X.25 >           connections, you should establish an account (either<           your mailer account or a dedicated server account)@           for use with each DECnet object. See Section 1.7.1 for=           more information on the requirements for the DECnetU           object account.o  ;           A DECnet object needs to be created to handle thel<           incoming SMTP-over-X.25 connections and to map the@           X25_SMTP object name to a DECnet object number. Choose<           an unused DECnet object number. To see what object8           numbers are currently in use, use the command:  6                            $ MCR NCP SHOW KNOWN OBJECT  =           Assign the object name X25_SMTP to an unused objectF:           number; the number used must be identical on all?           nodes on your network that use SMTP-over-DECnet (this 8           example uses 253). In NCP, use these commands:  9                            NCP> PURGE OBJECT X25_SMTP ALL S                            NCP> DEFINE OBJECT X25_SMTP NUMBER 253 PROXY NONE FILE - c                            _NCP>    MX_EXE:XSMTP_SERVER.EXE USER server-acct PASSWORD some-password.7                            NCP> SET OBJECT X25_SMTP ALL   @           You do not need to specify the FILE, USER, or PASSWORD<           parameters if you do not intend to accept incoming?           SMTP connections over X.25. Be sure that the password =           in the DECnet database matches the password you set .           for the server account in AUTHORIZE.  ?           You must also add an X.25 "destination" to the P.S.I. 2           database that maps to the DECnet object:  A                                                              3-15          '           Post-Installation Information_          O                            NCP> DEFINE MODULE X25-SERVER DESTINATION X25_SMTP - ?                            _NCP>   OBJECT X25_SMTP PRIORITY 0 -lH                            _NCP>   CALL MASK  FFFFFFFFFFFFFFFFFFFFFFFF -F                            _NCP>   CALL VALUE FF0000005832355F534D5450  N                            NCP> SET MODULE X25-SERVER DESTINATION X25_SMTP ALL  L           __________________________________________________________________  8    3.10   Customizing Mailing List and File Server Files  =           The MX installation procedure provides three files,a>           MLIST_ADD_MESSAGE.TXT, MLIST_REMOVE_MESSAGE.TXT, and=           MLIST_FORWARD_MESSAGE.TXT, for use with the mailings:           list processor, and a help file called FILESERV_<           HELP.TXT for use with a file server. If you intend<           to use the mailing list or file server features of;           MX, you should modify the contents of these files3:           to reflect site dependencies. If you already had:           customized versions of these files, they are not<           purged; you should delete the new versions created(           by the installation procedure.  <           Refer to Message Exchange Mailing List/File Server:           Guide for more information on setting up mailing           lists.  L           __________________________________________________________________      3.11   Setting Up MXALIAS  :           MX includes a utility called MXALIAS which users>           can execute to define personal MX aliases for e-mail?           addresses. MXALIAS is fully documented in the Messaget            Exchange User's Guide.  =           In order to make MXALIAS accessible to users on the ?           system, you should add a symbol like the following to =           your system login procedure (SYS$SYLOGIN) or to thet           user's LOGIN.COM:e  <                            $ mxalias :== $mx_exe:mxalias.exe             3-16         A                                     Post-Installation Information           ?           Alternatively, you can add a command to the DCLTABLESe>           on your system that will invoke MXALIAS. In order to@           do so, create a file called MXALIAS.CLD containing the           following lines:                              !R                            !  CLD file for defining MXALIAS command as DCL command                            !^                            !  To install for all users, modify the dev:[dir] strings below and=                            !  execute the following commands:                             !]                            !       $ SET COMMAND MXALIAS.CLD/TABLE=SYS$LIBRARY:DCLTABLES.EXE- S                            !               /OUTPUT=SYS$COMMON:[SYSLIB]DCLTABLES.EXE A                            !       $ INSTALL :== $INSTALL/COMMAND N                            !       $ INSTALL REPLACE SYS$LIBRARY:DCLTABLES.EXE                            !.                            DEFINE VERB MXALIAS=                                    IMAGE   MX_EXE:MXALIAS.EXET4                                    CLIFLAGS(FOREIGN)  ;           The instructions in the file show you would entero8           the command in the system-wide DCLTABLES. This<           undocumented technique can be used for any program1           that must be run with a foreign symbol.@  8           MXALIAS includes its own on-line help. A brief:           description of MXALIAS that can be placed in the8           system help library can be found in MX_DIR: as<           MXALIAS_MAIN.HLP. To install it in the system-wide6           help library, execute the following command:  Z                            $ LIBRARY/HELP/REPLACE SYS$HELP:HELPLIB.HLB MX_DIR:MXALIAS_MAIN  <           Of course, any local help library may be specified*           instead of SYS$HELP:HELPLIB.HLB.          A                                                              3-17h o  w    '           Post-Installation Informationn        L           __________________________________________________________________      3.12   Starting MXM  @           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.C?           From the SYSTEM account, or other suitably privilegedT%           account, enter the command:   4                            $ @SYS$STARTUP:MX_STARTUP  9           If you are using a separate mailer account, youn"           instead use the command:  ]                            $ SUBMIT/NOPRINT/USER=mailer/QUEUE=batchque SYS$STARTUP:MX_STARTUP   =           If you are running MX Jnet support, you should alsoi+           start (or stop and restart) Jnet.o  =           In a VMScluster environment, you should execute MX_A.           STARTUP on each node in the cluster.                                                 3-18 _  _                A           _______________________________________________________s       A      Sample MX Installation      >           This appendix contains an example of a first-time MX3           installation on a clustered Alpha system.F  L           $ @SYS$UPDATE:VMSINSTAL MX051 device:[directory_of_kit_files]<RET>  J                   OpenVMS AXP Software Product Installation Procedure V7.1  %           It is 11-OCT-1998 at 08:41.   9           Enter a question mark (?) at any time for help.o  N           * Are you satisfied with the backup of your system disk [YES]? <RET>  3           The following products will be processed:,               MX V5.1   <                   Beginning installation of MX V5.1 at 08:41  @           %VMSINSTAL-I-RESTORE, Restoring product save set A ...U           %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP.   F                           Message Exchange V5.1 Installation Procedure  S                  Copyright  1993,1996,1998 MadGoat Software.  All Rights Reserved.   N                     This licensed material is the property of MadGoat SoftwareX              Installation use, duplication, or disclosure is subject to the restrictionsC                                 set forth in the License Agreement.   T                MadGoat, Message Exchange, and MX are trademarks of MadGoat Software.K                       DEC, VMS, OpenVMS, VAX, Alpha, DECnet, and VMScluster H                         are trademarks of Digital Equipment Corporation.H                        MultiNet and TCPware are registered trademarks of?                                   Process Software Corporation. N                    LISTSERV is a registered trademark of L-Soft International.N                    Jnet is a registered trademark of Wingra Technologies, Inc.Q                 WIN/TCP and Pathway are registered trademarks of AttachMate, Inc.i  A                                                               A-1d                     Sample MX Installation          Q           * Do you want to purge files replaced by this installation [YES]? <RET>   -               Mixed VAX and Alpha VMSclusters-+               -----------------------------o  O               This system is part of a VMScluster.  If this VMScluster includes O               both VAX and Alpha systems that will share the MX directories andrL               configuration files, it will be necessary to install MX twice:K               once on a VAX system and once on an Alpha system.  It is onlytH               necessary to install the FULL MX kit on one type of system               (VAX or Alpha).o  I               The dual installation is required because the MX images arehM               linked during installation.  However, when installing MX on theiM               second system, you may elect to install only the executables toe/               avoid the need to reconfigure MX.   P               The full MX installation MUST be installed from one of the systemsL               for MX to work.  During that installation, information must beL               supplied pertaining to which nodes will run which agents, etc.  R           * Does this VMScluster include both VAX and Alpha systems [NO]? YES<RET>  M               MX Alpha and MX VAX can share a common MX directory tree.  WhentJ               supplying MX directory information, be sure a common disk isO               specified.  Avoid using logical names like SYS$SYSDEVICE, because A               the two types of systems cannot share system disks!   P               If you elect to install NETLIB, you should specify that the NETLIBP               images should be installed in MX_ROOT:[EXE] for VAX systems and in4               MX_ROOT:[ALPHA_EXE] for Alpha systems.  S           * Will the VAX and Alpha systems share a common MX directory [YES]? <RET>CZ           * Has MX V5.1 already been installed on a VAX system in this cluster [NO]? <RET>  7                                     Component SelectionU  O               Select the MX components you wish to install from the menu below.fM               An asterisk appears next to the packages that have already beenlO               selected.  You can remove a package from the list by selecting it N               again.  You may enter more than one selection by separating your"               choices with commas.  
           A-2          A                                            Sample MX Installation           &                1. [ ] Base MX software,                2. [ ] NETLIB network support,                3. [ ] SMTP interface support,                4. [ ] Jnet interface support.                5. [ ] SMTP-over-DECnet support5                6. [ ] Site-provided interface support 6                7. [ ] Mailing List/File Server support0                8. [ ] LISTSERV interface support#                9. [ ] Documentation 0               10. [ ] Example files and programs9               11. [ ] User-contributed files and programs                  12.     Exit  6           *       Your choice [12]: 1,2,3,9,10,11<RET>  7                                     Component Selection   O               Select the MX components you wish to install from the menu below.9M               An asterisk appears next to the packages that have already beenpO               selected.  You can remove a package from the list by selecting itnN               again.  You may enter more than one selection by separating your"               choices with commas.  &                1. [*] Base MX software,                2. [*] NETLIB network support,                3. [*] SMTP interface support,                4. [ ] Jnet interface support.                5. [ ] SMTP-over-DECnet support5                6. [ ] Site-provided interface supportt6                7. [ ] Mailing List/File Server support0                8. [ ] LISTSERV interface support#                9. [*] Documentation 0               10. [*] Example files and programs9               11. [*] User-contributed files and programs1                 12.     Exit  )           *       Your choice [12]: <RET>   9               You have selected the following components:o  A                                                               A-3c n  n                Sample MX Installation          "                   Base MX software(                   NETLIB network support(                   SMTP interface support                   Documentation ,                   Example files and programs5                   User-contributed files and programs   (           * Is this correct [YES]? <RET>  :               Configuring Base MX Directories and Logicals:               --------------------------------------------  Q               MX places most of its files in a private directory structure.  ThisCV               directory structure can be located on any disk, but the disk must eitherU               have disk quotas disabled or sufficient diskquota to hold all of the MXS5               images, temporary files, and log files.   U           * Where should the MX top directory be located? [SYS$SYSDEVICE:[MX]]: <RET> ^           %VMSINSTAL-I-SYSDIR, This product creates system disk directory  SYS$SYSDEVICE:[MX].b           %VMSINSTAL-I-SYSDIR, This product creates system disk directory  SYS$SYSDEVICE:[MX.EXE].h           %VMSINSTAL-I-SYSDIR, This product creates system disk directory  SYS$SYSDEVICE:[MX.ALPHA_EXE].  S               MX uses a file queue directory for storing mail messages.  This queuenU               directory may be placed with the other MX directories, or may be placed V               on a different disk.  The disk on which the queue directory resides mustW               also have quotas disabled or must have sufficient system quota to provide 4               for a backlog of undelivered messages.  X           * Where would you like the MX message queue? [DISK$ALPHASYS:[MX.QUEUE]]: <RET>d           %VMSINSTAL-I-SYSDIR, This product creates system disk directory  DISK$ALPHASYS:[MX.QUEUE].  8               Selecting the Size of the MX Message Queue8               ------------------------------------------  M               The MX queueing subsystem uses a fixed-size sequential file forrJ               the MX queue.  The size of the file determines the number ofM               messages that can be in the queue at any one time.  The size ofBL               the file can be extended at a later date using the MCP command               QUEUE EXTEND.   
           A-4     _    A                                            Sample MX InstallationB          L               For each message, one block is required.  To allow up to 5,000N               messages to be in the queue at any one time, the queue file mustJ               be slightly larger than 5,000 blocks. The required file sizeN               depends heavily on your site's e-mail traffic. For a workstationJ               that normally receives a couple of hundred messages a day, aF               queue file of 100 blocks or less is probably sufficient.  K               For sites with a lot of mail traffic, a size of 5,000--10,000 M               blocks is recommended.  If disk space is not a problem, you can N               specify as many as 131,072 (128K) messages, which is the maximum.               number MX is designed to handle.  I           * Maximum number of entries to allow in the queue [5000]: <RET>T  P               MX uses 10 subdirectories under the MX message queue directory forM               the actual storage of files.  Those directories will be created                 now, if necessary.  f           %VMSINSTAL-I-SYSDIR, This product creates system disk directory  SYS$SYSDEVICE:[MX.QUEUE.0].f           %VMSINSTAL-I-SYSDIR, This product creates system disk directory  SYS$SYSDEVICE:[MX.QUEUE.1].f           %VMSINSTAL-I-SYSDIR, This product creates system disk directory  SYS$SYSDEVICE:[MX.QUEUE.2].f           %VMSINSTAL-I-SYSDIR, This product creates system disk directory  SYS$SYSDEVICE:[MX.QUEUE.3].f           %VMSINSTAL-I-SYSDIR, This product creates system disk directory  SYS$SYSDEVICE:[MX.QUEUE.4].f           %VMSINSTAL-I-SYSDIR, This product creates system disk directory  SYS$SYSDEVICE:[MX.QUEUE.5].f           %VMSINSTAL-I-SYSDIR, This product creates system disk directory  SYS$SYSDEVICE:[MX.QUEUE.6].f           %VMSINSTAL-I-SYSDIR, This product creates system disk directory  SYS$SYSDEVICE:[MX.QUEUE.7].f           %VMSINSTAL-I-SYSDIR, This product creates system disk directory  SYS$SYSDEVICE:[MX.QUEUE.8].f           %VMSINSTAL-I-SYSDIR, This product creates system disk directory  SYS$SYSDEVICE:[MX.QUEUE.9].@           %VMSINSTAL-I-RESTORE, Restoring product save set B ...  ?               Now installing NETLIB library for TCP/IP support.   U           %MX-I-NETLRNOT, Release notes for NETLIB V2.2 have been copied to SYS$HELP.i@           %VMSINSTAL-I-RESTORE, Restoring product save set D ...  9                                  TCP/IP Support Selectione  K               Select the NETLIB TCP/IP support you wish to install from theUM               menu below.  An asterisk appears next to the packages that have L               already been selected.  You can remove a package from the listK               by selecting it again.  You may enter more than one selectiont5               by separating your choices with commas.N  A                                                               A-5                      Sample MX Installation          -                1. [*] Digital TCP/IP ServicesF$                2. [ ] Cisco MultiNet%                3. [ ] Process TCPware2(                4. [ ] Attachmate PathWay                  5.     Exit  (           *       Your choice [5]: <RET>  =               You have selected the following TCP/IP support:3  )                   Digital TCP/IP Servicesr  (           * Is this correct [YES]? <RET>  <                                Choosing the NETLIB Directory  J               The NETLIB libraries can be placed in any directory, as longJ               as that directory is accessible to all users who plan to use3               or develop NETLIB-based applications.   T           * Where should the NETLIB libraries be placed [SYS$COMMON:[NETLIB]]: <RET>;           %NETLIB-I-LINKING, Linking image NETLIB_SHRXFR...e<           %NETLIB-I-LINKING, Linking image NETLIB_UCX_SHR...  I               The installation will continue for another 5 to 45 minutes,hF               depending on your CPU type, distribution media, etc.  NoF               further input is required during the installation.  OnceE               installation has completed, you may be asked additional &               configuration questions.  @           %VMSINSTAL-I-RESTORE, Restoring product save set F ...  =               Now loading the Message Exchange base software.             
           A-6s l       A                                            Sample MX Installation           e           %VMSINSTAL-I-SYSDIR, This product creates system disk directory  SYS$SYSDEVICE:[MX.ROUTER]. d           %VMSINSTAL-I-SYSDIR, This product creates system disk directory  SYS$SYSDEVICE:[MX.LOCAL].4           %MX-I-LINKING, Linking image MX_FLQ_SHR...0           %MX-I-LINKING, Linking image MX_MSG...0           %MX-I-LINKING, Linking image MX_SHR...5           %MX-I-LINKING, Linking image MX_MAILSHRP...o4           %MX-I-LINKING, Linking image MX_MAILSHR...>           %MX-I-LINKING, Linking image MX_MAILSHRP (relink)...-           %MX-I-LINKING, Linking image MCP...,3           %MX-I-LINKING, Linking image MX_ROUTER... 2           %MX-I-LINKING, Linking image MX_LOCAL...3           %MX-I-LINKING, Linking image MAILQUEUE...n0           %MX-I-LINKING, Linking image MLFAKE...1           %MX-I-LINKING, Linking image MXALIAS...a3           %MX-I-LINKING, Linking image MX_DECODE...a4           %MX-I-LINKING, Linking image MX_FLQ_MGR...3           %MX-I-LINKING, Linking image MGLICENSE... 0           %MX-I-LINKING, Linking image REJMAN...f           %MX-I-NEWQUE, The MX system message queue will be created later in the installation process.u           %MX-I-LICENSEASK, You will be asked to register your MX license key at the end of the installation process. @           %VMSINSTAL-I-RESTORE, Restoring product save set H ...  >               Now providing the SMTP support files and images.  c           %VMSINSTAL-I-SYSDIR, This product creates system disk directory  SYS$SYSDEVICE:[MX.SMTP].Eh           %VMSINSTAL-I-SYSDIR, This product creates system disk directory  SYS$SYSDEVICE:[MX.SMTP.LOCK].1           %MX-I-LINKING, Linking image MX_SMTP...q5           %MX-I-LINKING, Linking image SMTP_SERVER...r:           %MX-I-LINKING, Linking image DOMAIN_EXPANSION...@           %VMSINSTAL-I-RESTORE, Restoring product save set L ...  H               Now providing MX documentation to directory MX_ROOT:[DOC].  b           %VMSINSTAL-I-SYSDIR, This product creates system disk directory  SYS$SYSDEVICE:[MX.DOC].@           %VMSINSTAL-I-RESTORE, Restoring product save set M ...  P               Now providing MX example files and programs to MX_ROOT:[EXAMPLES].  g           %VMSINSTAL-I-SYSDIR, This product creates system disk directory  SYS$SYSDEVICE:[MX.EXAMPLES]. @           %VMSINSTAL-I-RESTORE, Restoring product save set N ...  K               Now providing MX user-contributed files to MX_ROOT:[CONTRIB]._  f           %VMSINSTAL-I-SYSDIR, This product creates system disk directory  SYS$SYSDEVICE:[MX.CONTRIB].  A                                                               A-7n t  o                Sample MX Installation          1               MX installation procedure complete.E  F               The MX message queue will be created after the new files:               have been moved to their target directories.  O               Be sure to follow the post-installation instructions described in M               the MX Installation Guide.  This will minimally include editingUL               the system startup procedure to include the following command:  2                          $ @SYS$STARTUP:MX_STARTUP  X           %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories...  6           Since this is a first-time installation, the6           MX installation procedure asks licensing and@           configuration questions once the files have been moved&           to their target directories.  #               MX License Managementa#               ---------------------   N               MX requires a license key for its operation.  If you do not haveQ               a license key for MX, a temporary evaluation key will be registerede<               in the license database for you automatically.  =           * Do you have a license key for MADGOAT MX? NO<RET>m  V               Use of this software is subject to the terms set forth in the EvaluationX               License Agreement.  If you have not yet read the License Agreement, please               do so now.  T           * Would you like to display the text of the License Agreement [YES]? <RET>  7           [... text of License Agreement displayed ...]l  I           * Do you agree to the terms of the License Agreement? YES <RET>   N               Registering an evaluation license key now.  This key will expireK               in 30 days.  After evaluating MX, contact MadGoat Software toe6               purchase a full license for the product.  P           %MGLIC-S-REGISTERED, license MADGOAT MX registered in license databased           %MGLIC-W-EXPIRING, license MADGOAT MX (authorization AUTO-EVAL) will expire on  3-FEB-1998N           %MGLIC-S-LOADED, license MADGOAT MX successfully loaded with 0 units  '               MX Message Queue Creationl'               -------------------------m  
           A-8q m       A                                            Sample MX Installationd          <               The MX message queue file will be created now.  U           %MCP-I-QNEWQFL, creating new system message queue file for 5000 entries.... K           %MCP-I-QNEWQDN, new system message queue created for 5000 entries.F           %MX-I-FLQCREDONE, MX message queue file successfully created  R               The MXCONFIG command procedure will now be run to assist in creating*               an initial MX configuration.  -               MX Message Queue "Cluster" Namer-               -------------------------------   O               This is a 1-to-6 character name that is used to coordinate access-P               to the message queue.  If this system is part of a VMScluster, allM               systems in the cluster that share this MX installation will uset2               the same message queue cluster name.  U               For further information on MX cluster support, see the Manager's Guide.l  K               This name is typically set to the DECnet cluster alias or the 3               DECnet node name of the local system.   3           Message queue cluster name [ALPHA]: <RET>   5               Immediate Deletion of Finished Messagesi5               ---------------------------------------   O               When an MX queue entry has been fully processed,  it is marked asiO               being "finished" and  is  left in the queue for a period of time.iO               The MX Router or MX FLQ Manager scans the file every  15 minutes,aJ               by default, and purges the finished entries.  This delay canQ               improve responsiveness of the delivery agents and reduce contention $               for the message queue.  R               However, sites processing a high volume of messages may need to haveN               the finished queue entries deleted immediately on completion, inK               order to reclaim message queue and file system resources more                quickly.  G           Should finished messages be deleted immediately? [YES]: <RET>   "               Maximum Message Size"               --------------------  A                                                               A-9R :  P                Sample MX Installation          L               You may set a fixed limit on the size of messages that MX willL               accept.  Any message that is larger than this fixed limit willK               be rejected by the message entry agents.  The maximum size is "               specified in KBytes.  L               By default, the maximum size is zero, meaning that there is no               fixed limit.  6           Maximum message size (in KBytes)? [0]: <RET>  9               Reserved Free Space on Message Queue Devicen9               -------------------------------------------   K               MX limits the size of messages it accepts based on the amount J               of free space available on the disk device where the message               queue resides.  J               You may reserve a percentage of the total space on the disk.K               MX will ensure that it accepts no message that will cause the-G               amount of remaining free space to drop below the reserved                amount.l  K               By default, the reserved free space setting is 10%.  The free 6               space percentage may range from 1 to 90.  A           Percentage of disk space to reserve (1-90)? [10]: <RET>d"               MX Network Host Name"               --------------------  L               This is a 1-to-255 character name that is your "official" host'               name for E-mail purposes.t  K               For Internet hosts, this should be your Internet domain name.t-               (Example: myhost.mycompany.com)r  K               For hosts not connected to the Internet, consult your networksH               consult your network manager for an appropriate host name.  C           Enter the MX network host name [Alpha.MadGoat.COM]: <RET>   ,               MX Message Queue Manager Agent,               ------------------------------             A-10 t       A                                            Sample MX Installationo          R               If this MX installation will be handling a large volume of messages,N               it is recommended that you run a separate Queue Manager agent toP               maintain the message queue.  For small installations, the separateT               Queue Manager is not required, since the Router Agent can also perform               queue management.   ?           Do you want to run the MX Queue Manager? [YES]: <RET> L           Enter names of VMScluster nodes to run MX Queue Manager [*]: <RET>  "               MX Processing Agents"               --------------------  P               You will now be asked to specify startup information for the other-               installed MX processing agents.   @           Do you want to run the MX Message Router? [YES]: <RET>M           Enter names of VMScluster nodes to run MX Message Router [*]: <RET>rL           How many MX Message Router processes should be started? [1]: <RET>F           Do you want to run the MX Local Delivery Agent? [YES]: <RET>S           Enter names of VMScluster nodes to run MX Local Delivery Agent [*]: <RET> R           How many MX Local Delivery Agent processes should be started? [1]: <RET>E           Do you want to run the MX SMTP Delivery Agent? [YES]: <RET>fR           Enter names of VMScluster nodes to run MX SMTP Delivery Agent [*]: <RET>Q           How many MX SMTP Delivery Agent processes should be started? [1]: <RET>V=           Do you want to run the MX SMTP Server? [YES]: <RET>SJ           Enter names of VMScluster nodes to run MX SMTP Server [*]: <RET>  %               SMTP Server Connections.%               -----------------------r  I               The MX SMTP Server can be configured to handle from 1 to 16 M               simultaneous incoming connections.  In VMScluster environments, F               this configuration setting affects all nodes running the               SMTP server.  M           Enter maximum number of SMTP server connections to allow [4]: <RET>   L               This procedure builds an MCP command file which will create an0               initial MX configuration database.  T               First-time MX managers should use this command procedure as a startingJ               point, then tailor the resulting MCP command file as needed.  A                                                              A-11e                     Sample MX Installation          N               NOTE:  In the following questions, when asked for an ADDRESS, beO                      sure to specify a full E-mail address, even if the addresse                      is local.@                                  Example:  user@host.company.ORG  Q           * What do you want to call the command file? [MX_DIR:CONFIG.MCP]: <RET>   <                                      Delivery Path Selection  K               Select the delivery paths you are using with MX from the menu L               below.  Selected items are marked with an asterisk ("*").  YouM               can remove a delivery path from the list by selecting it again. N               You may enter more than one selection by separating your choices               with commas.  &                1. [ ] SMTP over TCP/IP                  2.     Exit  (           *      Your choice [2]: 1<RET>  <                                      Delivery Path Selection  K               Select the delivery paths you are using with MX from the menu1L               below.  Selected items are marked with an asterisk ("*").  YouM               can remove a delivery path from the list by selecting it again.eN               You may enter more than one selection by separating your choices               with commas.  &                1. [*] SMTP over TCP/IP                  2.     Exit  '           *      Your choice [2]: <RET>   =               You have selected the following delivery paths:   "                   SMTP over TCP/IP  *           * Is this correct?  [Yes]: <RET>  '               TCP/IP (SMTP) InformationS  N               MX must be configured to recognize all possible names that couldQ               be used by other hosts on the network to identify the local system:d             A-12 s  i    A                                            Sample MX Installationi          2                   Examples:   myhost.mycompany.COMB                               myhost                (abbreviation)  M               It must also be able to recognize the bracketed, dotted-decimalr.               IP address for the local system:  ,                   Example:    [128.113.5.15]  S               In a VAXcluster with multiple TCP/IP-connected hosts you should enterSS               the node name(s) and bracketed address for each host connected to the7               TCP/IP network.I  N               When are finished entering node names, just press RETURN to move&               on to the next question.  =           * Enter a local Internet node name: [10.0.0.1]<RET>   9           * Enter another local Internet node name: <RET> N           %MXCONFIG-I-UUCPGW, uunet.uu.net has been added as your UUCP gatewayR           %MXCONFIG-I-BITGW, cunyvm.cuny.edu has been added as your BITNET gateway  -               Defining the "Postmaster" AliasD  P               If you have not set up a username on the system called POSTMASTER,P               you should create an alias in MX for username Postmaster to direct>               mail to the person performing postmaster duties.  J               All Internet- and BITNET-connected systems MUST have a valid!               Postmaster address.   I               If you have a valid POSTMASTER account on your system, justcH               press RETURN.  Otherwise, enter a full (user@host) addressH               to which all Postmaster-addressed messages should be sent.  T           * Enter an alias for Postmaster (user@host): system@alpha.madgoat.com<RET>  8               There are no more configuration questions.      A                                                              A-13o    :                Sample MX Installation          P           * Would you like to run MCP now to build the configuration? [Y]: <RET>*           ! MX_DEVICE:[MXTEST]CONFIG.MCP;1I           ! Created: 11-OCT-1998 08:45:40.46 by MX_CREATE_CONFIG_DATABASEE           !s(           DEFINE PATH "[10.0.0.1]" LOCALA           ! NOTE: The next path definition should always be LAST.            DEFINE PATH * SMTP           !e*           ! Done with routing information.           !i>           DEFINE ALIAS "Postmaster" "system@alpha.madgoat.com"W           DEFINE ALIAS "POSTMAST" "system@alpha.madgoat.com" ! for BITNET compatibilityNZ           %MCP-I-WROTECFG, wrote configuration to file MX_DEVICE:[MXTEST]MX_CONFIG.MXCFG;1I           Save agent and logical name configuration changes? [YES]: <RET>   <                   Installation of MX V5.1 completed at 08:46  H               Adding history entry in VMI$ROOT:[SYSUPD]VMSINSTAL.HISTORY  N               Creating installation data file: VMI$ROOT:[SYSUPD]MX051.VMI_DATA  3                   VMSINSTAL procedure done at 08:46n                                               A-14                     A           _______________________________________________________o  &    B      Contents of Distribution Kit      =           MX is provided in a VMSINSTALlable distribution kitE>           consisting of 14 save sets. Each save set is briefly!           described in Table B-1.L  A           Table_B-1__MX_installation_kit_save_sets_______________   A           Save_Set___Contents____________________________________n  ;           MX051.A    Kit files and common base installation_                      files.-  6           MX051.B    NETLIB common installation files.  3           MX051.C    NETLIB VAX installation files.M  5           MX051.D    NETLIB Alpha installation files.N  3           MX051.E    Base installation files (VAX).,  5           MX051.F    Base installation files (Alpha).i  @           MX051.G    MX SMTP (TCP/IP, DECnet, X.25) files (VAX).  9           MX051.H    MX SMTP (TCP/IP, DECnet, X.25) files                       (Alpha).a  ;           MX051.I    MX Jnet, SITE, UUCP, MLF, and ListServ_+                      interface files (VAX).e  ;           MX051.J    MX Jnet, SITE, UUCP, MLF, and ListServ.-                      interface files (Alpha).   A           MX051.K    Mailing List/File Server (MLF) common files.M  8           MX051.L    Documentation files, in PostScript,9                      Bookreader, and plain ASCII formats.V             MX051.M    Examples.  A           MX051.N____Contributed_software_and_files._____________l  A                                                               B-1  t  d                A           _______________________________________________________c  +    C      Files Created During Installation[      7           The files in Table C-1 are created during the.;           installation of the MX software. For an inventory <           of the MX user-contributed files and software, see:           the file 00README.TXT in save set MX051.M, or in?           directory MX_ROOT:[CONTRIB], if the contributed filesR           are installed.  :           The following notes are referenced in Table C-1:  0           1  Only if ML/FS support is installed.  0           2  Only if Documentation is installed.  ,           3  Only if Examples are installed.  3           4  Only if SMTP-over-DECnet is installed.,  /           5  Only if SMTP support is installed.S  /           6  Only if Jnet support is installed.O  /           7  Only if UUCP support is installed.   /           8  Only if SITE support is installed.T  1           9  Only if NETLIB support is installed.r  1          10  Only if SMTP-over-X.25 is installed.X  3          11  Only if LISTSERV support is installed.         A                                                               C-1          +           Files Created During Installation           :           Table C-1  Message Exchange files created duringA           ___________installation________________________________   A           File_name___________________Description________________r  A           __________________Files_in_MX_FLQ_DIR:_________________l  =           MX_SYSTEM_QUEUE.FLQ_CTL     System queue sequential *                                       file  A           _______________________________________________________VA           _______________Files_in_MX_ROOT:[000000]_______________   :           MGLICENSE_                  License key database           DATABASE.MGLICDB  A           MXALIAS_MAIN.HLP            Top-level MXALIAS help fileh5                                       for HELPLIB.HLB   >           MX_ALIAS_HELPLIB.HLB        Help library for MXALIAS  :           MX_MCP_HELPLIB.HLB          Help library for MCP  =           MX_REJMAN_HELPLIB.HLB       Help library for REJMANX-                                       utilitye  9           MLF_CONFIG.COM              ML/FS configuration.8                                       procedure (Note 1)  ;           MX_LICENSE.COM              Command procedure fore8                                       license management  ?           MXCONFIG.COM                MX configuration creation /                                       procedure   ?           MX_CREATE_CONFIG_           MX configuration database 8           DATABASE.COM                creation procedure  >           MX_LOGICALS.DAT             Logical name definitions>                                       used by MX___STARTUP.COM  8           MX_STARTUP_INFO.DAT         Describes which MX;                                       processes get startedu  
           C-2e         A                                 Files Created During Installationt          ;           Table C-1 (Cont.)  Message Exchange files createdMA           ___________________during_installation_________________M  A           _______________________________________________________   A           ____________Files_in_MX_ROOT:[DOC]_(Note_2)____________-  A           INDEX.HTML                  Index of HTML documentation ,                                       (HTML)                                                              A                                                               C-3  e  r    +           Files Created During Installation           ;           Table C-1 (Cont.)  Message Exchange files createdOA           ___________________during_installation_________________   A           File_name___________________Description________________   A           ____________Files_in_MX_ROOT:[DOC]_(Note_2)____________e  8           MX_INSTALL_                 Installation guide2           GUIDE.DECW$BOOK             (Bookreader)  ?           MX_INSTALL_GUIDE.HTML       Installation guide (HTML)e  8           MX_INSTALL_GUIDE.PS         Installation guide2                                       (PostScript)  @           MX_INSTALL_GUIDE.TXT        Installation guide (ASCII)  9           MX_LIBRARY.DECW$BOOKSHELF   Library file for MXu:                                       Bookreader documents  6           MX_MGMT_GUIDE.DECW$BOOK     Management guide2                                       (Bookreader)  =           MX_MGMT_GUIDE.HTML          Management guide (HTML)   6           MX_MGMT_GUIDE.PS            Management guide2                                       (PostScript)  >           MX_MGMT_GUIDE.TXT           Management guide (ASCII)  >           MX_MLF_GUIDE.DECW$BOOK      Mailing List/File Server8                                       guide (Bookreader)  >           MX_MLF_GUIDE.HTML           Mailing List/File Server2                                       guide (HTML)  >           MX_MLF_GUIDE.PS             Mailing List/File Server8                                       guide (PostScript)  >           MX_MLF_GUIDE.TXT            Mailing List/File Server3                                       guide (ASCII)q  ;           MX.DECW$BOOKSHELF           Bookshelf file for MX :                                       Bookreader documents  8           MX_PROG_GUIDE.DECW$BOOK     Programmer's guide2                                       (Bookreader)  
           C-4  s       A                                 Files Created During Installation           ;           Table C-1 (Cont.)  Message Exchange files created A           ___________________during_installation_________________t  A           File_name___________________Description________________t  A           ____________Files_in_MX_ROOT:[DOC]_(Note_2)____________y  ?           MX_PROG_GUIDE.HTML          Programmer's guide (HTML)c  8           MX_PROG_GUIDE.PS            Programmer's guide2                                       (PostScript)  @           MX_PROG_GUIDE.TXT           Programmer's guide (ASCII)  =           MX_USER_GUIDE.DECW$BOOK     User guide (Bookreader)   7           MX_USER_GUIDE.HTML          User guide (HTML)   =           MX_USER_GUIDE.PS            User guide (PostScript)n  8           MX_USER_GUIDE.TXT           User guide (ASCII)                                      A                                                               C-5o h  o    +           Files Created During Installationu          ;           Table C-1 (Cont.)  Message Exchange files createdtA           ___________________during_installation_________________   A           _______________________________________________________   A           __________Files_in_MX_ROOT:[EXAMPLES]_(Note_3)_________o  =           00README.ADDRESS_REWRITER   README file for address]/                                       rewriter.   :           00README.NAME_CONVERSION    README file for name8                                       conversion module.  >           ADDRESS_REWRITER.B32        BLISS source for address/                                       rewriter.   :           ADDRESS_REWRITER.C          C source for address/                                       rewriter.y  :           ADDRESS_REWRITER.MMS        Makefile for address/                                       rewriter.X  A           DOM_EXPANSION_CMU.B32       Sample domain name expanders5                                       for CMU TCP/IP.-  A           DOM_EXPANSION_UCX.B32       Sample domain name expander 5                                       for DEC TCP/IP.   ;           FILTER.C                    Sample message filterl.                                       callout.  <           MX_FILTERDEF.H              Header file for sample=                                       message filter callout.a  <           MX_FILTERDEF.R32            BLISS REQUIRE file for@                                       creating a message filter.  ;           MX_HDR.H                    C header file with MX 9                                       header definitions.a  ;           NAME_CONVERSION.B32         BLISS source for name 8                                       conversion module.  ;           NAME_CONVERSION.MAR         MACRO source for name 8                                       conversion module.  7           NAME_CONVERSION.C           C source for namee8                                       conversion module.  
           C-6     y    A                                 Files Created During Installationo          ;           Table C-1 (Cont.)  Message Exchange files creatednA           ___________________during_installation_________________R  A           File_name___________________Description________________s                                                                        A                                                               C-7n    P    +           Files Created During Installation           ;           Table C-1 (Cont.)  Message Exchange files created A           ___________________during_installation_________________e  A           _______________________________________________________   ?           DNSMTP_SERVER.EXE           SMTP-over-DECnet receiver-5                                       module (Note 4)r  @           DOMAIN_EXPANSION.EXE        Domain name expander (Note(                                       5)  A           MAILQUEUE.EXE               Program for listing delayed 7                                       messages in queueb  8           MCP.EXE                     MX Control Program  @           MGLICENSE.EXE               License management utility  A           MLFAKE.EXE                  Utility for faking messages =                                       to mailing list serverst  =           MXALIAS.EXE                 Utility for defining MXd-                                       aliases   >           MX_DECODE.EXE               Utility to decode BASE643                                       mail messages   >           MX_DNSMTP.COM               SMTP-over-DECnet command8                                       procedure (Note 4)  ?           MX_DNSMTP.EXE               SMTP-over-DECnet delivery 5                                       module (Note 4)   <           MX_FLQ_MGR.COM              MX FLQ Manager command/                                       procedureD  4           MX_FLQ_MGR.EXE              MX FLQ Manager  5           MX_FLQ_SHR.EXE              Shareable image >                                       implementing file queues  ?           MX_JNET.COM                 MX Jnet interface commandt8                                       procedure (Note 6)  >           MX_JNET.EXE                 MX Jnet interface module.                                       (Note 6)  >           MX_LOCAL.EXE                MX Local delivery module  
           C-8          A                                 Files Created During Installationv          ;           Table C-1 (Cont.)  Message Exchange files createdeA           ___________________during_installation_________________   A           File_name___________________Description________________   A           ___Files_in_MX_ROOT:[EXE]_and_in_MX_ROOT:[ALPHA_EXE]___o  ;           MX_LSV.COM                  MX LISTSERV interfaceo=                                       command procedure (Noteu)                                       11)a                                                            A                                                               C-9          +           Files Created During Installation           ;           Table C-1 (Cont.)  Message Exchange files created A           ___________________during_installation_________________a  A           File_name___________________Description________________   A           ___Files_in_MX_ROOT:[EXE]_and_in_MX_ROOT:[ALPHA_EXE]___x  ;           MX_LSV.EXE                  MX LISTSERV interfacey6                                       module (Note 11)  ?           MX_MAILSHR.EXE              VMS MAIL foreign protocol /                                       interface   :           MX_MAILSHRP.EXE             Service routines for@                                       foreign protocol interface  ?           MX_MFSDISP.EXE              Jnet Mail/File Dispatcherc5                                       for MX (Note 6)   >           MX_MLF.COM                  Mailing list/file server@                                       command procedure (Note 1)  >           MX_MLF.EXE                  Mailing list/file server5                                       module (Note 1)   3           MX_MSG.EXE                  Messages file   ?           MX_RMAIL.EXE                UUCP mail entry interface .                                       (Note 7)  A           MX_ROUTER.COM               MX Router command procedurep  6           MX_ROUTER.EXE               MX Router module  8           MX_SHR.EXE                  MX common routines7                                       shareable libraryt  ?           MX_SITE.COM                 Command procedure used bys?                                       site-spec interface (Note (                                       8)  >           MX_SITE.EXE                 Site-spec delivery agent.                                       (Note 8)  =           MX_SITE_IN.COM              Site-spec message entry 6                                       program (Note 8)             C-10 .  <    A                                 Files Created During Installation           ;           Table C-1 (Cont.)  Message Exchange files created A           ___________________during_installation_________________l  A           File_name___________________Description________________   A           ___Files_in_MX_ROOT:[EXE]_and_in_MX_ROOT:[ALPHA_EXE]___9  <           MX_SMTP.COM                 SMTP outbound delivery@                                       command procedure (Note 5)  <           MX_SMTP.EXE                 SMTP outbound delivery5                                       module (Note 5)m  ?           MX_SMTP_MSG.EXE             Message file for deliveryl>                                       status and SMTP messages  ;           MX_START.COM                Command procedure forO<                                       starting MX components  A           MX_UUCP.COM                 Used by UUCP delivery agent?.                                       (Note 7)  ?           MX_UUCP.EXE                 UUCP delivery agent (Notey(                                       7)  =           MX_XSMTP.COM                SMTP-over-X.25 deliveryX=                                       agent command procedure8/                                       (Note 10)   =           MX_XSMTP.EXE                SMTP-over-X.25 delivery_5                                       agent (Note 10)o  >           MX___STARTUP.COM            Master startup procedure-                                       for MX.   4           REJMAN.EXE                  REJMAN utility  ;           SMTP_SERVER.COM             SMTP inbound receivers=                                       command procedure (Note_(                                       5)  ;           SMTP_SERVER.EXE             SMTP inbound receiver 5                                       module (Note 5)n  <           XSMTP_SERVER.EXE            SMTP-over-X.25 inbound?                                       receiver module (Note 10)l  A                                                              C-11     5    +           Files Created During Installation           ;           Table C-1 (Cont.)  Message Exchange files created A           ___________________during_installation_________________   A           File_name___________________Description________________s  A           ____________Files_in_MX_ROOT:[MLF]_(Note_1)____________5  A           FILESERV_HELP.TXT           Help text for use with filei,                                       server  A           _______________________________________________________ A           _____Files_in_MX_ROOT:[MLF.MAILING_LISTS]_(Note_1)_____a  ?           MLIST_ADD_                  Template for mailing list 1           MESSAGE.TEMPLATE            add message.  ?           MLIST_ADD_MESSAGE.TXT       Template for mailing list 1                                       add message   @           MLIST_FORWARD_              Template for forwarded-to-8           MESSAGE.TEMPLATE            list-owner message  @           MLIST_FORWARD_MESSAGE.TXT   Template for forwarded-to-8                                       list-owner message  @           MLIST_HELP.TXT              Help file for mailing list/                                       processort  ?           MLIST_REMOVE_               Template for mailing listt5           MESSAGE.TEMPLATE            removal messagei  ?           MLIST_REMOVE_MESSAGE.TXT    Template for mailing list 5                                       removal message   A           _______________________________________________________-A           _____________Files_in_NETLIB_DIR:_(Note_9)_____________i  7           NETLIB_SHRXFR.EXE           NETLIB transport-d9                                       independent library   ?           NETLIB_xxx_SHR.EXE          NETLIB transport-specific A                                       library (one per transport)X             C-12         A                                 Files Created During Installation           ;           Table C-1 (Cont.)  Message Exchange files created A           ___________________during_installation_________________-  A           _______________________________________________________l  A           ______________Files_in_SYS$COMMON:[SYSHLP]______________  :           MXvvn.RELEASE_NOTES         Release notes for MX  >           NETLIBvvn.RELEASE_NOTES     Release notes for NETLIB  A           _______________________________________________________ A           ___________Files_in_SYS$COMMON:[SYS$STARTUP]____________  >           MX_STARTUP.COM              Startup procedure for MX  ;           NETLIB_STARTUP.COM          Startup procedure for A           ____________________________NETLIB_(Note_2)____________L                                            A                                                              C-13 