V'0)>2Message Exchange Installation Guide;

Message Exchange Installation Guide





+

February, 2001



EThis manual provides installation and setup instructions for Message 3Exchange, electronic mail software for VMS systems.

.Revision/Update Information: This is a revised manual.

.Operating System and Version:VAX/VMS V5.5 or later

OpenVMS Alpha V6.2 or later

"Software Version:Message Exchange V5.2


25 February 2001

EThe information in this document is subject to change without notice Aand should not be construed as a commitment by MadGoat Software. CMadGoat Software assumes no responsibility for any errors that may appear in this document.

<No part of this publication may be reproduced, transmitted, Btranscribed, stored in a retrieval system, or translated into any Glanguage or computer language, in any form or by any means electronic, Hmechanical, magnetic, optical, chemical, or otherwise without the prior 'written permission of MadGoat Software.

CUse of this software and documentation is subject to the terms and .conditions set forth in the License Agreement.

AThe Licensed Materials are provided with RESTRICTED RIGHTS. Use, Hduplication, or disclosure by the Government is subject to restrictions Has set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data <and Computer Software clause at DFARS §252.227-7013 or 8subparagraphs (c)(1) and (2) of the Commercial Computer FSoftware---Restricted Rights at 48 CFR §52.227-19, as applicable.

EMadGoat, Message Exchange, and MX are trademarks of MadGoat Software.

>The following are trademarks of Digital Equipment Corporation:               
DEC DECnet P.S.I.
ULTRIX VAX  VAXcluster
VMS AXP  VMScluster


CMultiNet and TCPware are registered trademarks of Process Software Corporation.

;LISTSERV is a registered trademark of L-Soft International.

AWIN/TCP and Pathway are registered trademarks of Attachmate, Inc.

Copyright ©2001



 ,  
JContents
 


$

Preface



:This guide describes how to install Message Exchange (MX).4

Intended Audience



HThis manual is intended for use by the system manager or any individual .responsible for installing and maintaining MX.5

Document Structure



;This guide consists of three chapters and three appendices.                        
 Chapter 1 , Contains pre-installation information.
 Chapter 2 . Describes the MX installation procedure.
 Chapter 3 - Contains post-installation information.
 Appendix A 2 Contains a listing of a sample installation.
 Appendix B 8 Describes the contents of the MX distribution kit.
 Appendix C > Contains a list of the files created by an installation.
4

Related Documents



?You can find additional information in the following documents:




S

Chapter 1
Preparing to Install Message Exchange




?This chapter describes the steps that should be taken prior to )installing the Message Exchange software.U

1.1 Software License Key



CMX requires a license key to enable its operation. If you have not Fobtained a license key for MX from MadGoat, the installation kit will Cautomatically register a temporary evaluation license for you. The .temporary key enables the product for 30 days.V

1.2 Prerequisite Software



DMX requires VAX/VMS version V5.5 or later, or OpenVMS Alpha V6.2 or Clater, to run. The SMTP support option requires a NETLIB-supported >TCP/IP package (refer to the NETLIB release notes for further Einformation). SMTP-over-DECnet requires DECnet, but does not require Feither NETLIB or any TCP/IP package. The UUCP support option requires DECUS UUCP V1.1 or later.$g

1.3 Upgrading from Previous Versions of MX



BIf you are currently running MX V4.0 or later, you can install MX 4V5.2 as an upgrade; the installation procedure will Cautomatically detect this and notify you that it is upgrading your Ccurrent installation. If you are currently running a version of MX prior to V4.0, you must either:

    E
  1. upgrade to MX V4.0, V4.1, V4.2, or V5.0 first, then install MX  V5.2 as an upgrade; or(
  2. install MX V5.2 in a new location.
c

1.4 VMScluster Support and MX Clusters



=MX fully supports VMScluster systems in both homogeneous and heterogeneous configurations.

HAn "MX cluster" consists of one or more VMScluster nodes that meet the following criteria:

    D
  1. All nodes in the MX cluster share one User Authorization File ? (SYSUAF.DAT) and one VMS Mail profile (VMSMAIL_PROFILE.DATA).F
  2. All nodes have mounted the disk that contains the MX images and  directories.F
  3. All nodes have mounted the disk that contains the message queue.H
  4. If MX is to be used for network mail, at least one node in the MX G cluster is running the networking software required for each type of  network link desired.E
  5. The logical name MAIL$SYSTEM_FLAGS is defined to a value of at Q least 3. (Refer to VMS Mail Utility Manual for further information on  MAIL$SYSTEM_FLAGS.)


HFor homogeneous VMScluster systems, the MX cluster will usually include all nodes in the VMScluster.^

1.4.1 Answering VMScluster-related Installation Questions



FThe MX installation procedure automatically detects that you are in a GVMScluster and will ask additional questions during installation about Hwhere in the cluster each installed MX processing agent should run. The Dprocessing agents are programs which are run as detached processes. EThey can be run on any or all nodes in the cluster (following the MX HCluster guidelines outlined above), and will automatically cooperate in $providing their respective services.

EWhen asked to provide a cluster node name for running the processing @agents, be sure to specify the SCSNODE name (or use an asterisk B("*") to have an agent run on all nodes in the cluster).*a

1.4.2 Mixed-Architecture VMSclusters (VAX and Alpha systems)



DMixed-architecture VMSclusters (those containing both VAX and Alpha Hsystems) are fully supported by MX. The MX directory tree can be shared Gby both systems if it resides on a common disk. When the VAX and Alpha Hsystems share a common MX directory, agents may be run on both types of systems.

EWhen MX is first installed, and the installation proceduredetermines @that the node is part of a cluster, it will record installation Ginformation in the MX directory tree. A subsequent installation of the Dsame version of MX in the same directory tree, but on a system of a Edifferent architecture, will cause the installation procedure to ask Dwhether or not just architecture-specific files should be installed.



/  
Note

DMX must be installed twice on a mixed-VMScluster: Eonce on a VAX system and once on an Alpha system. Installing MX on a EVAX installs the VAX executable images and installing it on an Alpha Hinstalls the Alpha images. Only the first installation needs to include 2all of the architecture-independent files.


FThe MX_ROOT: directory tree contains two directories for executables: DMX_ROOT:[EXE] for VAX executables and MX_ROOT:[ALPHA_EXE] for Alpha Gexecutables. The logical MX_EXE:, which is used in all examples below, Bwill automatically be defined appropriately on each system in the cluster.[

1.5 Determining Your Node Name



EMX requires two node names for its operation. The first, the MX Fcluster name, is used by MX to coordinate access to the message queue.



EThe second node name is the MX network node name. This is Fthe name that is used by the MX software to identify mail originating Alocally. You should decide on a node name for your system before Cinstalling the MX software. If your host has a registered Internet Hdomain name, you should use that name. If you are on a UUCP network and Hdo not have a registered Internet domain name, you should use your UUCP Dhost name. Otherwise, you should use a host name that fits with the naming conventions at your site.

CIn an MX cluster environment, MX will use a single network name to Fidentify the entire cluster. If you have several nodes with their own Fnetwork node names, and your networking software does not support the Fuse of a cluster-wide alias, you could either pick one node to be the 2"master" for E-mail purposes or use the fMX_VMSMAIL_FROM_FORMAT logical name (described in Message Exchange Management Guide) to have Ceach node insert its own host name in return addresses on outgoing Emessages. What you do will depend on your network software and setup.c

1.6 Accessing the Online Release Notes



DMX provides online release notes, which you can display or print by Fusing VMSINSTAL with the OPTIONS N parameter. After the installation, 4you can read the release notes by printing the file HSYS$HELP:MXvvn.RELEASE_NOTES, where "vvn" denotes the version Fnumber of the software. For example, for version V5.2 of MX, the file name would be MX052.

6The release notes for NETLIB are provided in the file GSYS$HELP:NETLIBvvn.RELEASE_NOTES, where "vvn" identifies the Eversion of NETLIB shipped with the MX distribution kit. This file is Acreated during NETLIB installation and is not accessible through VMSINSTAL OPTIONS N.P

1.7 Mailer Accounts



EYou can run the detached processes MX uses under the SYSTEM account, ?or, if you prefer, under a separate "mailer" account.

FNote, however, that using a mailer account may complicate the process jfor starting up MX on your system; see Section 3.5 for further %information on MX startup procedures.

EIf you intend to use an account other than SYSTEM for running the MX Hdetached processes, you should create the account before installing MX. 8The mailer account should have the following attributes:



fFigure 1-1 shows the UAF entry for a typical Mailer account.R

1.7.1 SMTP-over-DECnet/X.25 Dedicated Account



HIf 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 Dexclusively for the DECSMTP and X25_SMTP DECnet objects. If so, you Gshould ensure that the accounts have NETWORK access and the privileges BTMPMBX, NETMBX, SYSPRV, and SYSLCK (both authorized and default). mFigure 1-2 shows the UAF entry for a typical SMTP-over-DECnet or ~SMTP-over-X.25 server account. See Section 3.10 for more information on >setting up the MX SMTP-over-DECnet and SMTP-over-X.25 support.

5Figure 1-1 Mailer Account attributes




 

"
EUsername: MAILER                           Owner:  MX Mailer account HAccount:  NETSTUF                          UIC:    [1076,76] ([MAILER]) =CLI:      DCL                              Tables: DCLTABLES Default:  USER_DISK:[MAILER] LGICMD:   NL: Login Flags:  Disctly Defcli $Primary days:   Mon Tue Wed Thu Fri ,Secondary days:                     Sat Sun GPrimary   000000000011111111112222  Secondary 000000000011111111112222 GDay Hours 012345678901234567890123  Day Hours 012345678901234567890123 GNetwork:  -----  No access  ------            -----  No access  ------ GBatch:    ##### Full access ######            ##### Full access ###### GLocal:    -----  No access  ------            -----  No access  ------ GDialup:   -----  No access  ------            -----  No access  ------ GRemote:   -----  No access  ------            -----  No access  ------ EExpiration:            (none)    Pwdminimum:  3   Login Fails:     0 ?Pwdlifetime:           (none)    Pwdchange:             (none) QLast Login:            (none) (interactive), 19-JAN-1990 14:38 (non-interactive) :Maxjobs:         0  Fillm:        60  Bytlm:        36000 :Maxacctjobs:     0  Shrfillm:      0  Pbytlm:           0 :Maxdetach:       0  BIOlm:        20  JTquota:       1024 :Prclm:           4  DIOlm:        18  WSdef:          512 :Prio:            4  ASTlm:       325  WSquo:          512 :Queprio:       100  TQElm:        10  WSextent:      2048 :CPU:        (none)  Enqlm:       600  Pgflquo:      25600 Authorized Privileges: H  CMKRNL SYSNAM DETACH TMPMBX WORLD EXQUOTA NETMBX PHY_IO SYSPRV SYSLCK Default Privileges: H  CMKRNL SYSNAM DETACH TMPMBX WORLD EXQUOTA NETMBX PHY_IO SYSPRV SYSLCK >Identifier                         Value           Attributes H  ARPANET_ACCESS                   %X80010042      NORESOURCE NODYNAMIC H  INTERNET_ACCESS                  %X80010043      NORESOURCE NODYNAMIC 


 

FFigure 1-2 SMTP-over-DECnet server account attributes




 

"
MUsername: DNSMTP_SRV                       Owner:  MX DECSMTP object account LAccount:  NETSTUF                          UIC:    [1076,77] ([DNSMTP_SRV]) =CLI:      DCL                              Tables: DCLTABLES !Default:  USER_DISK:[DNSMTP_SRV] LGICMD:   NL: Login Flags:  Disctly Defcli $Primary days:   Mon Tue Wed Thu Fri ,Secondary days:                     Sat Sun GPrimary   000000000011111111112222  Secondary 000000000011111111112222 GDay Hours 012345678901234567890123  Day Hours 012345678901234567890123 GNetwork:  ##### Full access ######            ##### Full access ###### GBatch:    -----  No access  ------            -----  No access  ------ GLocal:    -----  No access  ------            -----  No access  ------ GDialup:   -----  No access  ------            -----  No access  ------ GRemote:   -----  No access  ------            -----  No access  ------ EExpiration:            (none)    Pwdminimum:  3   Login Fails:     0 ?Pwdlifetime:           (none)    Pwdchange:             (none) QLast Login:            (none) (interactive), 19-JAN-1990 14:38 (non-interactive) :Maxjobs:         0  Fillm:        60  Bytlm:        36000 :Maxacctjobs:     0  Shrfillm:      0  Pbytlm:           0 :Maxdetach:       0  BIOlm:        20  JTquota:       1024 :Prclm:           4  DIOlm:        18  WSdef:          512 :Prio:            4  ASTlm:       325  WSquo:          512 :Queprio:       100  TQElm:        10  WSextent:      2048 :CPU:        (none)  Enqlm:       600  Pgflquo:      25600 Authorized Privileges:   TMPMBX NETMBX SYSPRV SYSLCK Default Privileges:   TMPMBX NETMBX SYSPRV SYSLCK 


 d

1.8 Installation Procedure Requirements



GBefore installing MX, ensure that the following privileges, resources, and requirements are met:

]

1.9 Saving Current Configuration



DIf MX is already installed on your system, you should create an MCP Bcommand file from your current MX configuration database prior to Ginstalling a new version of MX. To do this, use the following commands:

 

"
$ MCP :== $MX_EXE:MCPI$ 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.


I

Chapter 2
Installing Message Exchange




BMX uses VMSINSTAL for installation. If you do not know how to use GVMSINSTAL, you should first read the chapter on installing software in Dthe VMS System Manager's Manual. For the installation, you >should be logged into the SYSTEM account, or another suitably privileged account.



/  
Note

EMX must be installed twice on a mixed-architecture ?VMScluster: once on a VAX system, and once on an Alpha system. >Installing MX on a VAX installs the VAX executable images and ?installing it on an Alpha installs the Alpha images. The first 2installation (VAX or Alpha) will also provide the Garchitecture-independent files. When installing on a mixed VMScluster, Hbe sure to specify a device name for the MX installation directory that Cis valid on both the VAX and Alpha systems, and refers to the same Fdevice in both cases. Using a platform-specific logical name, such as ;SYS$SYSDEVICE, will cause the installation to fail.
Q

2.1 Shutting down MX



GIf any MX processes are currently running, you should stop them before Finstalling a new version of MX, including any SMTP servers (which are Fnot shutdown with the MCP SHUTDOWN command in versions of MX prior to GV2.2-2). Unprocessed mail should remain queued until you start the new MX processes.S

2.2 Invoking VMSINSTAL



Invoke VMSINSTAL to install MX.

 

"
#$ @SYS$UPDATE:VMSINSTAL MXvvn ddcu:




ESubstitute the appropriate values for vvn and ddcu.

 

"
 @         VAX/VMS Software Product Installation Procedure V5.5-2  It is dd-Mmm-yyyy at hh:mm. 0Enter a question mark (?) at any time for help.  




GIf there are any users logged into the system, you will see the message

 

"
?%VMSINSTAL-W-ACTIVE, The following processes are still active: ...process names...  




DYou can install MX while users are logged in, though it is safer to Bperform the installation while no one is logged in and while your network links are shut down.

 

"
&* Do you want to continue anyway [NO]?




$If you wish to continue, answer YES.

 

"
>* Are you satisfied with the backup of your system disk [YES]?




BIf you feel comfortable with your system disk backup, answer YES. HOtherwise, answer NO, perform the backup, then restart the installation procedure.#`

2.3 Preliminary Installation Checks



FThe installation procedure first checks to make sure that the version Gof VMS that you are running is compatible with the version of MX being Cinstalled, and does some preliminary checks on disk space. It then Gtries to determine the type of installation and the location of the MX directory tree.R

2.3.1 Ensuring that MX is Currently Shut Down



FIf a version of MX is currently installed, the installation procedure Fwill check to see if any MX delivery agents are currently running. If Fso, it will warn you of this and ask if you wish to continue with the installation:

 

"
:%MX-I-NOTDOWN, MX delivery agents have not been shut down.* Do you wish to continue [NO]?


?It is strongly recommended that you answer NO to this 6question, shut down MX, then restart the installation.L

2.3.2 Determining the Installation Type



AThe installation procedure examines the system to determine if a @version of MX is already installed. If there is a version of MX Ginstalled, it then determines whether this is an upgrade from Ean upgradable previous version of MX, or a reinstall of the Hcurrent version. In either case, the installation procedure asks you if 0you wish to update the MX installation it found:

 

"
]%MX-I-INSTALDET, An installation of MX Vv.u has been detected at dev:[dir].9* Do you wish to update the existing installation [YES]? 


DIf you answer YES to this question, the installation procedure will Gskip the question about selecting a location for the MX directory tree.

GIf this is a fresh install, or you answer NO when asked about updating -an existing installation, you are then asked:

 

"
D* Where should the MX top directory be located [SYS$SYSDEVICE:[MX]]:




HYou may place the MX directories on any disk you like. If MX is already Ginstalled on the system and its logical names are defined, the default Aanswer will be the definition of your existing MX root directory.



/  
Note

CIf you are installing MX on a mixed VMScluster where VAX and Alpha Gsystems will share a common directory, be sure you specify a disk that His common to both types of systems. The default device (SYS$SYSDEVICE:) Fmay not be appropriate, especially if you do not cross-mount your VAX Cand Alpha system disks between systems of different architectures. 
!J

2.3.3 Mixed-Architecture Installation



EMX next determines if the system is part of a VMScluster, and if the Hversion of MX currently being installed has already been installed once Gon a node in the cluster of a different architecture. If both of these :are found to be true the installation procedure then asks:

 

"
C*  Do you wish to install only arch-specific files [YES]? 




AYou should answer YES to this question unless you really want to .re-install the architecture-independent files.

(The last of the preliminary questions is

 

"
A* Do you want to purge files replaced by this installation [YES]?




FIf this is the first time you have installed MX, answering NO to this Cquestion can save some time when the MX files are moved into their directories.T

2.4 Component Selection



FA menu of MX components appears next, and you are asked to enter your choices from the menu:

 

"
     1. [ ] Base MX software #     2. [ ] NETLIB network support #     3. [ ] SMTP interface support #     4. [ ] UUCP interface support %     5. [ ] SMTP-over-DECnet support #     6. [ ] SMTP-over-X.25 support ,     7. [ ] Site-provided interface support -     8. [ ] Mailing List/File Server support      9. [ ] Documentation '    10. [ ] Example files and programs 0    11. [ ] User-contributed files and programs      13.     Exit  *       Your choice [13]: 




CThe exact contents of this menu may differ from the above display, Gdepending on the system's architecture (VAX or Alpha). In addition, if this is an architecture-specific-only installation (see Section 2.3.3), 9the last three choices in the menu will not be displayed.

EEnter the number corresponding to the component you wish to install; Amultiple components may be selected by entering the numbers as a Hcomma-separated list. The menu is displayed again after each selection, Hwith asterisks appearing next to the items you have selected; selecting 5a component twice removes it from the selection list.

@When you are upgrading to a new version of MX, the installation Cprocedure will look at your current configuration to automatically Gdetermine the components that should be installed. If you wish to omit Hany of those components that were selected, simply select them again to remove it from the list.

AWhen you have selected the components you want to install, enter D13 to exit the menu. Your selections are displayed 3again and you are asked to confirm your selections:

 

"
9    You have selected the following optional components:  &    (selected components listed here)  * Is this correct [YES]? 




HPress RETURN to continue the installation, or enter NO to return to the components menu.

Component Notes


FYou must install the Base software component if this is your Bfirst installation of MX, or if you are upgrading from a previous Fversion of MX. The other components are optional and may be installed Eat any time after the Base component is installed. If you re-install Bthe Base component, you must also re-install all desired optional Gcomponents as well, except for documentation, examples and contributed files.

HIf you elect to install SMTP support, NETLIB support will automatically Gbe installed as well. If you have already installed the NETLIB support Fcomponent, you can disable the NETLIB re-installation by re-selecting it on the menu.^

2.5 NETLIB Component Installation



FIf you are installing the NETLIB component (required for SMTP support Gusing TCP/IP), the saveset containing the NETLIB support files will be Hloaded and you will be asked some questions regarding the configuration of NETLIB.

FThe NETLIB installation procedure displays a menu of supported TCP/IP Hpackages and asks for the packages for which you wish to install NETLIB Asupport. The list for Alpha and VAX systems may not be the same, Fdepending on the number of TCP/IP packages supported on each platform.

 

"
     1. [ ] CMU TCP/IP $     2. [ ] Digital TCP/IP Services      3. [ ] Process MultiNet      4. [ ] Process TCPware      5. [ ] Attachmate PathWay       6.     Exit  *       Your choice [6]: 




GThe installation procedure attempts to pre-select those packages which Gappear to be installed on the system. Selections are made just as from ?the MX optional components menu. When you exit this menu, your ;selections are displayed and you are asked to confirm them:

 

"
4    You have selected the following TCP/IP support:        (packages listed here)  * Is this correct [YES]? 




;Press RETURN to continue or enter NO to return to the menu.

HIf you elected to install support for more than one TCP/IP package, you Gare then asked to select the one that will be used by default when the "NETLIB startup procedure executes:

 

"
@    You have selected support for more than one TCP/IP package. >    You must now select which is to be used by default on the     current system.        (packages listed here)  *       Your choice: 




CSelect the package you wish to use by default. If you need to have Gdifferent packages used on different systems in a VMScluster, you will Bneed to edit the NETLIB_STARTUP command procedure as described in ;Section 3.8.

GThe final NETLIB installation question asks where the NETLIB shareable libraries should be placed:

 

"
L* Where should the NETLIB libraries be placed [device:[directory]]:




EIf this is your first installation of NETLIB, the default answer for Athis question will be the directory where the MX executables are Elocated. However, you may specify any valid location for these files.[

2.6 The Installation Completes



FAfter the configuration questions and NETLIB component installations, Gwhich always require input from the installer, all selected components >are installed. Files are copied from the each save set of the ?installation kit, then all installed files are copied to their Edestination directories. Informational messages about the individual #components are displayed as needed.


K

Chapter 3
Post-Installation Information




@This chapter contains important information about setting up MX "configuration and startup options.Y

3.1 License Key Registration



?If the installation procedure did not detect the presence of a Eregistered license key for MX, it will ask you if you have a license Ckey. If you do, it will invoke MX_LICENSE.COM so you can enter the Blicense key data. If you do not, it will automatically register a Ftemporary evaluation license key, which is enables the product for 30 days.O

3.2 Configuring MX



DWhen installing MX for the first time, or upgrading from a previous Gversion, the installation procedure automatically invokes the MXCONFIG <command procedure to assist in creating or updating your MX Aconfiguration files. If you are adding options to an existing MX Finstallation, and have already created a configuration database, this Cstep is skipped. If you want to create a new MX configuration from Dscratch, you may use the MXCONFIG command procedure to create an MX 8configuration database after the installation completes:

 

"
"$ @SYS$STARTUP:MX_STARTUP LOGICALS$ @MX_DIR:MXCONFIG




EMXCONFIG prompts you for some basic information about the MX message Hqueue, your local host name, and MX processing agents. This information Gis used to create logical names used by MX and control the parts of MX Fthat are started during the system startup procedure. The prompts for Gthese configuration elements contain detailed descriptions for each of these configuration options.

HIf MXCONFIG is invoked as part of an initial installation, it will also Gask about your network connectivity, and create an MCP command file to Hcreate an MX configuration database. You can use MXCONFIG to define all 9routing information and Postmaster aliases for a typical HInternet-connected system. Once the basic configuration is created with ?MXCONFIG, you can tailor it as you wish using the MCP commands 8described in Message Exchange Management Guide.b

3.3 Message Queue Location and Limits



DThe first step of the MXCONFIG procedure (option 1 on the menu when Ainvoked outside the installation procedure) asks questions about Bconfiguring the MX message queue. The first question asks for the Gdirectory where the queue should be located. If you are configuring MX Bfor the first time, the default location will be MX_ROOT:[QUEUE]; Ghowever, the queue may be located on any accessible disk on the system Eor cluster. If you are re-configuring MX, the default answer to this Fquestion will be your current MX message queue directory. You may use Fthis procedure to move the message queue to a new location, if needed.

CAfter other questions about the cluster name and whether completed Hmessages should be deleted from the queue immediately, MXCONFIG prompts Gfor configuration information regarding the maximum allowable size for Emessages and minimum amount of space that should be kept free on the )disk device containing the message queue.?

3.3.1 Maximum Message Size



HYou may specify a maximum size for any message that enters your system. FBy default, the maximum size is set to zero, indicating that there is Eno fixed maximum. This default setting is adequate for most systems; Husers sometimes send very large files through e-mail, and if sufficient Gspace is available, this is not a problem. However, if your system has Climited disk space available, restricting messages to a reasonable Emaximum size may help prevent mailboxes from consuming too much disk space.?

3.3.2 Message Queue Limits



HTo prevent system failures or other undesirable behavior from occurring Ddue to disk devices becoming too full, MX checks the amount of free @space available on the disk containing the message queue before Haccepting a message for delivery. MXCONFIG prompts you for a value that Hrepresents, as a percentage value, the amount of free space that should Fbe reserved on the queue disk. If a message is entered (via SMTP, VMS HMAIL, or any other source) that would cause the amount of free space to Hdrop below this value, the message is automatically refused and deleted from the system.

GMXCONFIG sets the reserved free space to a default value of 10%, which Hwill ensure that MX never causes the disk to become more than 90% full. HIf you elected during installation to place the message queue on a very Elarge disk (larger than 1GB), you may wish to configure the reserved Ffree space to a smaller value; the minimum allowed value is 1% (which ?allows the disk to become 99% full before MX refuses to accept Gmessages). If your message queue is on a very small disk (smaller than F500MB), you may wish to configure the reserved free space to a larger value.

EAt some sites, the message queue disk may be located on a very large Fdisk that is also very full, and even the 1% minimum that is settable >through MXCONFIG may not be low enough to allow MX to operate Gconsistently. MX provides a means for configuring the minimum reserved ?free space as an absolute number of disk blocks, rather than a Dpercentage. This is not settable through MXCONFIG; to configure the Greserved free space in disk blocks, you must add the following logical 1name definition to your system startup procedure:

 

"
8$DEFINE/SYSTEM/EXEC MX_FLQ_DISK_FREE_ABSOLUTE n


Hwhere n is the minimum allowed free space on the disk, in disk Cblocks. This logical name overrides the percentage setting that is Fconfigured through MXCONFIG. The minimum allowed value for n is 1024.



/  
Note

CWarning: MX may temporarily exceed the reserved free space setting Awhile a message is being entered into the queue. Configuring the Breserved free space setting to too low a value may cause the disk Dcontaining the message queue to become 100% full at times; this may Ghave undesirable side-effects, especially if the message queue resides on your system disk.
Z

3.4 Establishing a Postmaster



HAll Internet sites that use electronic mail must be able to accept mail Gto the username Postmaster. If you do not have a real Gusername called POSTMASTER on your system, you should either establish *aliases with the MCP DEFINE ALIAS command:

 

"
+MCP> DEFINE ALIAS Postmaster "user@host"




?(substituting appropriate values for user and Fhost), or use the SET FORWARD command in VMS Mail to ,forward mail from Postmaster to a real user:

 

"
)MAIL> SET FORWARD/USER=POSTMASTER user




GEven if you are not connected to the Internet, it is still a good idea 6to create a Postmaster username or forwarding address.d

3.5 Adding MX Startup to System Startup



3The startup procedure for MX may vary depending on:



8In either case, remember that if you are running the MX ESMTP-over-TCP/IP support, you should start MX after you start your TCP/IP software.

HIf you are running L-Soft International's LISTSERV, you must define the HLISTSERV logicals, but not the process, before starting MX. For example:

 

"
,$ @SYS$STARTUP:LISTSERV_STARTUP.COM LOGICALS$ @SYS$STARTUP:MX_STARTUP.COM#$ @SYS$STARTUP:LISTSERV_STARTUP.COM




#Standalone Systems


FIf you intend to run MX under the SYSTEM account, all you need to add 0to your system startup procedure is the command:

 

"
$ @SYS$STARTUP:MX_STARTUP




HIf you are using a separate mailer account, you would use the following commands instead:

 

"
"$ @SYS$STARTUP:MX_STARTUP LOGICALS3$ SUBMIT/NOPRINT/USER=mailer SYS$STARTUP:MX_STARTUP




HFor mailer substitute the username you assigned to your mailer account.

"Clustered Systems


BIn a cluster environment, as long as you are running MX under the ASYSTEM account, the startup command is as easy as for standalone systems:

 

"
$ @SYS$STARTUP:MX_STARTUP




DHowever, if you are running MX under a separate mailer account, how Eeach 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).

@If the node will not run one or more of the MX ?processing agents, such as a satellite node in a Local-Area or BMixed-Interconnect VMScluster, all it needs to start up MX is the command:

 

"
$ @SYS$STARTUP:MX_STARTUP


?which just defines the necessary logical names and install the 2necessary images for interfacing VMS Mail with MX.

FIf the node will run one or more MX processes, those Hprocesses need to be started up under the mailer account's username, so you would use the commands:

 

"
"$ @SYS$STARTUP:MX_STARTUP LOGICALSA$ SUBMIT/NOPRINT/USER=mailer/QUEUE=nodeque SYS$STARTUP:MX_STARTUP


Fsubstituting the mailer account name for mailer and the name Dof a batch queue that runs on the local system for nodeque.2

3.5.1 Example



GAs an example, take a homogeneous VMScluster with two nodes, NODE1 and GNODE2, each with a TCP/IP connection, and several satellite nodes that Gwill just be used for sending and receiving mail by users (i.e., no MX processes will run on them).

?Both NODE1 and NODE2 have batch queues, called NODE1_BATCH and ANODE2_BATCH, respectively. The mailer account username is MAILER.

:The commands to be added to SYS$MANAGER:SYSTARTUP_V5.COM, (after TCP/IP startup, would be:

 

"
$ NODE = F$GETSYI ("NODENAME")0$ IF NODE .NES. "NODE1" .AND. NODE .NES. "NODE2"$ THEN$    @SYS$STARTUP:MX_STARTUP$ ELSEI$    SUBMIT/NOPRINT/USER=MAILER/QUEUE='NODE'_BATCH SYS$STARTUP:MX_STARTUP$ ENDIF


f

3.6 Adding MX Shutdown to System Shutdown



HTo ensure that MX agent processes are shut down cleanly when the system Cis shut down, add the following lines to SYS$MANAGER:SYSHUTDWN.COM:

 

"
$ MCP := $MX_EXE:MCP$ MCP SHUTDOWN


DThis will notify any agent processes on the system that they should Fshut down without affecting the agent processes on other nodes in the cluster.\

3.7 Establishing Your Time Zone



HIf you are not in the US Eastern time zone, or you are not following US Fstandard daylight savings time, or you do not like "EST" and "EDT" as Ftime zone names, you must make sure that at least one of several time -zone logicals is defined in SYSTARTUP_V5.COM.(R

3.7.1 The Product-Specific Time Zone Logicals



FMX checks for the existence of one of several time zone logicals that Bspecify the timezone string to be used when generated RFC822 mail Fmessage headers. Because most of the delivery transports (DECUS UUCP, Dthe TCP/IP implementations, etc.) already define time zone logicals Gcompatible with MX, it is not necessary to define MX-specific logicals.

BOn OpenVMS V6.0 and later, MX automatically uses the logical name ESYS$TIMEZONE_DIFFERENTIAL as the basis for its time zone strings. If =you have not correctly set that logical name, use the command

 

"
 $ @SYS$MANAGER:UTC$CONFIGURE_TDF




Ato set the timezone differential. If your site observes Daylight DSavings Time, you may need to adjust the timezone differential each "time you adjust your system clock.

EOn systems where SYS$TIMEZONE_DIFFERENTIAL is not defined (typically Gpre-V6.0 VMS), the value of the first logical defined in the following 4ordered list is used with no time-zone calculations.                
 MX_TIMEZONE  MX
 MULTINET_TIMEZONE  MultiNet
 UUCP_TIME_ZONE  DECUS UUCP
 WIN$TIME_ZONE  WIN/TCP and PathWay
%C

3.7.2 The MX Timezone Logicals



FIf you wish to define a specific timezone logical name for use by MX, you should define it as follows:

 

"
%$ DEFINE/SYS/EXEC MX_TIMEZONE "tzstr"




=where tzstr is a valid (RFC822-compliant) time zone Hdesignation, such as "-0500". No validity checking is performed on this Bstring. Note that the string you specify with MX_TIMEZONE is used Gverbatim. If you use MX_TIMEZONE and you observe daylight savings time Hin your area, it is your responsibility for modifying the definition of BMX_TIMEZONE as needed. You do not need to shut down MX to do this.X

3.8 Interfacing with TCP/IP



DThe SMTP interface uses the NETLIB transport-independent library to Hinterface with the TCP/IP package or packages you have installed on the system.H

3.8.1 Disabling Vendor SMTP Support



HIf your TCP/IP vendor provides SMTP support as part of its package, you /should disable that support before starting MX.



/  
Note

HThe instructions provided below were valid for various versions of each Evendor's software. Please consult your TCP/IP documentation for more accurate instructions.
C

3.8.1.1 Disabling CMUIP SMTP



HFor CMU-OpenVMS/IP (aka CMU-Tek TCP/IP), edit your INTERNET.CONFIG file Cand comment out the line that begins with "WKS:25", then Arestart TCP/IP. In addition, you may wish to deassign the system logical name TCP$SMTPSV.F

3.8.1.2 Disabling MultiNet SMTP



>For MultiNet, use the Server Configuration Utility to disable MultiNet's SMTP service:

 

"
$ MULTINET CONFIGURE/SERVER-MultiNet Server Configuration Utility 2.2(25):[Reading in symbols from SERVER image MULTINET:SERVER.EXE]?[Reading in configuration from MULTINET:SERVICES.MASTER_SERVER]SERVER-CONFIG>DISABLE SMTPSERVER-CONFIG>RESTARTSERVER-CONFIG>EXIT




CIf the SMTP was previously enabled, you will also need to stop the 'MultiNet SMTP batch queue. For example:

 

"
 $ STOP/QUEUE MULTINET_SMTP_QUEUE


E

3.8.1.3 Disabling TCPware SMTP



HFor TCPware, use the TCPware configuration utility to disable TCPware's CSMTP server, if you installed TCPware-SMTP. For TCPware v3.0, type:

 

"
$ @TCPWARE:CNFNET FULL SMTP




,For versions of TCPware prior to v3.0, type:

 

"
$ @TCPIP_ROOT:CNFNET FULL SMTP




When asked

 

"
3Enter the number of listening SMTP-VMS servers [1]:




Eenter 0. When asked whether to restart SMTP, answer YES.A

3.8.1.4 Disabling UCX SMTP



FVMS/ULTRIX Connection (in versions 1.0 through 1.3B) does not include any native SMTP support.

FDEC TCP/IP Services for VMS V2.x does include native SMTP support. To >disable the UCX SMTP server under V2.x, perform the following:

GFor DEC TCP/IP Services for VMS V3.0 and higher, perform the following:P

3.8.1.5 Disabling Wollongong PathWay SMTP



HTo disable the SMTP server for Wollongong's PathWay, follow these steps:



FTo prevent the PathWay SMTP server from restarting on the next system Bboot, comment out the SMTP_INIT line in the PathWay startup file, $TWG$TCP:[NETDIST.MISC]STARTINET.COM.

FThis procedure should permanently disable the PathWay SMTP server. To Freenable the PathWay SMTP server, undo all the edit changes, kill the BMX SMTP_SERVER, kill the INET_SERVER, and restart the INET_SERVER.H

3.8.2 Ensuring SMTP Server Restarts



CThe MX SMTP Server process automatically exits when it detects the Fshutdown of the TCP/IP software. If you want to ensure that it starts Gback up again after restarting your TCP/IP software, you should create +a command procedure for starting up TCP/IP:

 

"
$ @vendor-supplied-startup K$ IF F$TRNLNM ("MX_EXE") .NES. "" THEN @SYS$STARTUP:MX_STARTUP SMTP_SERVER 




FSubstitute the name of the vendor-supplied startup procedure for your !TCP/IP package in the first line.V

3.9 Interfacing with UUCP



GIf you have installed the support for DECUS UUCP, you must ensure that $DECUS UUCP calls MX to deliver mail.

GIf you are running DECUS UUCP v2.0 or higher, you must modify the UUCP Aconfiguration to define the logical UUCP_UUXQT_DCL_RMAIL_MX. The 8logical should be added to UUCP_CFG:CONTROL. as follows:

 

"
!+ ! G!       -- Make DECUS UUCP UUXQT_DCL procedure use MX to deliver mail. ! !- -UUCP_UUXQT_DCL_RMAIL_MX                 TRUE 




CFor versions of DECUS UUCP prior to v2.0, you must modify the UUCP Fcommand procedure UUCP_BIN:UUXQT_DCL.COM to accommodate the hook into GMX. The section of the command file after the label DO_RMAIL should be modified as follows:

The line that reads

 

"
8$        SET PROCESS/PRIVILEGE=(SYSPRV, DETACH, BYPASS) 




3should be modified to include the privilege SYSLCK:

 

"
@$        SET PROCESS/PRIVILEGE=(SYSPRV, DETACH, BYPASS, SYSLCK) 




CThe corresponding line that turns off these privileges a few lines #below should be similarly modified.

<The line that runs the mail message through the UUCP mailer:

 

"
7$        MAIL/PROTOCOL=UUCP_MAILSHR 'infile' "''addr'" 




.should be replaced by the following two lines:

 

"
#$        RMAIL := $MX_EXE:MX_RMAIL "$        RMAIL 'infile' "''addr'" 




FYou may want to move the definition of the RMAIL symbol to the top of the command procedure.



/  
Note

FUUCP must be started before MX in the system startup sequence.
c

3.10 SMTP Support for DECnet and X.25



:If you elected to install support for SMTP-over-DECnet or HSMTP-over-X.25, you must take some additional steps to configure DECnet and MX.U

3.10.1 Creating a DECnet Object for DECnet-SMTP



@You must create a DECnet object called DECSMTP for establishing 9SMTP-over-DECnet connections, both incoming and outgoing.

CIf you intend to accept incoming SMTP-over-DECnet connections, you Gshould establish an account (either your mailer account or a dedicated sserver account) for use with each DECnet object. See Section 1.7.1 for Cmore information on the requirements for the DECnet object account.

;A DECnet object needs to be created to handle the incoming ESMTP-over-DECnet connections and to map the DECSMTP object name to a DDECnet object number. Choose an unused DECnet object number. To see :what object numbers are currently in use, use the command:

 

"
$ MCR NCP SHOW KNOWN OBJECT




FAssign the object name DECSMTP to an unused object number; the number Fused must be identical on all nodes on your network that use ESMTP-over-DECnet (this example uses 254). In NCP, use these commands:

 

"
 NCP> PURGE OBJECT DECSMTP ALL:NCP> DEFINE OBJECT DECSMTP NUMBER 254 PROXY NONE FILE -^_NCP>    MX_EXE:DNSMTP_SERVER.EXE USER server-acct PASSWORD some-passwordNCP> SET OBJECT DECSMTP ALL




EYou do not need to specify the FILE, USER, or PASSWORD parameters if Fyou do not intend to accept incoming SMTP connections over DECnet. Be Gsure that the password in the DECnet database matches the password you (set for the server account in AUTHORIZE.

Using Proxies


GInstead of storing the username and password for the server account in Bthe DECnet database, you could grant access using DECnet proxies. HProxies give you more control over who on the network has access to the Fobject, and eliminate the need for storing the password to the server &account in the DECnet object database.



/  
Note

FUsing proxies allows the remote system access to all files the server Faccount can access (by using regular DECnet file transfers with FAL). GIf you do not manage the remote system, it is recommended that you use *DECnet objects instead of proxies.


@To enable proxy access to the DECSMTP object, use the following commands in NCP:

 

"
 NCP> PURGE OBJECT DECSMTP ALL>NCP> DEFINE OBJECT DECSMTP NUMBER 254 PROXY INCOMING FILE -$_NCP>    MX_EXE:DNSMTP_SERVER.EXENCP> SET OBJECT DECSMTP ALL




GThen in AUTHORIZE, create proxy entries for the mailer accounts on the ?other systems on the network that will be sending you mail via SMTP-over-DECnet:

 

"
FUAF> ADD/PROXY remote::mailer server-acct/DEFAULT




FFor remote::mailer substitute the DECnet node of the Eremote system and the username of the mailer account on that system. CFor server-acct substitute the name of the server 7account you set up for use with the DECnet-SMTP object. S

3.10.2 Creating a DECnet Object for X.25-SMTP



AYou must create a DECnet object called X25_SMTP for establishing 7SMTP-over-X.25 connections, both incoming and outgoing.

HIf you intend to accept incoming SMTP-over-X.25 connections, you should Gestablish an account (either your mailer account or a dedicated server qaccount) for use with each DECnet object. See Section 1.7.1 for more >information on the requirements for the DECnet object account.

;A DECnet object needs to be created to handle the incoming DSMTP-over-X.25 connections and to map the X25_SMTP object name to a DDECnet object number. Choose an unused DECnet object number. To see :what object numbers are currently in use, use the command:

 

"
$ MCR NCP SHOW KNOWN OBJECT




GAssign the object name X25_SMTP to an unused object number; the number Fused must be identical on all nodes on your network that use ESMTP-over-DECnet (this example uses 253). In NCP, use these commands:

 

"
!NCP> PURGE OBJECT X25_SMTP ALL;NCP> DEFINE OBJECT X25_SMTP NUMBER 253 PROXY NONE FILE -]_NCP>    MX_EXE:XSMTP_SERVER.EXE USER server-acct PASSWORD some-passwordNCP> SET OBJECT X25_SMTP ALL




EYou do not need to specify the FILE, USER, or PASSWORD parameters if Dyou do not intend to accept incoming SMTP connections over X.25. Be Gsure 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. (database that maps to the DECnet object:

 

"
7NCP> DEFINE MODULE X25-SERVER DESTINATION X25_SMTP -'_NCP>   OBJECT X25_SMTP PRIORITY 0 -0_NCP>   CALL MASK  FFFFFFFFFFFFFFFFFFFFFFFF -._NCP>   CALL VALUE FF0000005832355F534D5450 6NCP> SET MODULE X25-SERVER DESTINATION X25_SMTP ALL 


q

3.11 Customizing Mailing List and File Server Files



4The MX installation procedure provides three files, 5MLIST_ADD_MESSAGE.TXT, MLIST_REMOVE_MESSAGE.TXT, and HMLIST_FORWARD_MESSAGE.TXT, for use with the mailing list processor, and Ha help file called FILESERV_HELP.TXT for use with a file server. If you Bintend to use the mailing list or file server features of MX, you Hshould modify the contents of these files to reflect site dependencies. DIf you already had customized versions of these files, they are not Gpurged; you should delete the new versions created by the installation procedure.

sRefer to Message Exchange Mailing List/File Server Guide for more information on setting up mailing lists.$U

3.12 Setting Up MXALIAS



GMX includes a utility called MXALIAS which users can execute to define Fpersonal MX aliases for e-mail addresses. MXALIAS is fully documented .in the Message Exchange User's Guide.

GIn 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 the user's LOGIN.COM:

 

"
"$ mxalias :== $mx_exe:mxalias.exe 




EAlternatively, you can add a command to the DCLTABLES on your system Bthat will invoke MXALIAS. In order to do so, create a file called +MXALIAS.CLD containing the following lines:

 

"
! 8!  CLD file for defining MXALIAS command as DCL command ! D!  To install for all users, modify the dev:[dir] strings below and #!  execute the following commands: ! C!       $ SET COMMAND MXALIAS.CLD/TABLE=SYS$LIBRARY:DCLTABLES.EXE- 9!               /OUTPUT=SYS$COMMON:[SYSLIB]DCLTABLES.EXE '!       $ INSTALL :== $INSTALL/COMMAND 4!       $ INSTALL REPLACE SYS$LIBRARY:DCLTABLES.EXE ! DEFINE VERB MXALIAS #        IMAGE   MX_EXE:MXALIAS.EXE         CLIFLAGS(FOREIGN) 




EThe instructions in the file show you would enter the command in the Gsystem-wide DCLTABLES. This undocumented technique can be used for any /program that must be run with a foreign symbol.

FMXALIAS includes its own on-line help. A brief description of MXALIAS Fthat can be placed in the system help library can be found in MX_DIR: Das MXALIAS_MAIN.HLP. To install it in the system-wide help library, execute the following command:

 

"
?$ 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.N

3.13 Starting MX



AOnce you have created an MX configuration database and added the Fappropriate startup commands to your system startup, you are ready to Estart up the MX software. From the SYSTEM account, or other suitably &privileged account, enter the command:

 

"
$ @SYS$STARTUP:MX_STARTUP




HIf you are using a separate mailer account, you instead use the command:

 

"
B$ SUBMIT/NOPRINT/USER=mailer/QUEUE=batchque SYS$STARTUP:MX_STARTUP




HIn a VMScluster environment, you should execute MX_STARTUP on each node in the cluster.


F

Appendix A
Sample MX Installation




GThis appendix contains an example of a first-time MX installation on a clustered Alpha system.

 

"
X$ @SYS$UPDATE:VMSINSTAL MX052 device:[kit_dir][RET] : OpenVMS AXP Software Product Installation Procedure V7.1   It is 10-JAN-2001 at 07:44.  0Enter a question mark (?) at any time for help.  O* Are you satisfied with the backup of your system disk [YES]? [RET] *The following products will be processed:  
  MX V5.2  , Beginning installation of MX V5.2 at 07:44  7%VMSINSTAL-I-RESTORE, Restoring product save set A ... L%VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP.  =                Message Exchange I5.2 Installation Procedure  N      Copyright © 1993,1996,1998-2001 MadGoat Software.  All Rights Reserved.  G           This licensed material is the property of MadGoat Software. Q    Installation, use, duplication, or disclosure is subject to the restrictions 9                     set forth in the License Agreement.  L      MadGoat, Message Exchange, and MX are trademarks of MadGoat Software. B            DEC, VMS, OpenVMS, VAX, Alpha, DECnet, and VMScluster =              are trademarks of Compaq Computer Corporation. ?             MultiNet and TCPware are registered trademarks of 6                        Process Software Corporation. E         LISTSERV is a registered trademark of L-Soft International. H      WIN/TCP and Pathway are registered trademarks of AttachMate, Inc.       MX Root Directory Location     --------------------------  H    MX places most of its files in a private directory tree.  This tree F    can be located on any disk that has sufficient space available to G    hold the installed files plus all temporary files and logs created     by MX agent processes.  F    In a VMScluster, the disk device selected should be accessible to 0    all VMScluster nodes that will be using MX.  W* Where should the MX root directory be located? [SYS$SYSDEVICE:[MX]]: [RET]U%VMSINSTAL-I-SYSDIR, This product creates system disk directory  SYS$SYSDEVICE:[MX]. Y%VMSINSTAL-I-SYSDIR, This product creates system disk directory  SYS$SYSDEVICE:[MX.EXE]. _%VMSINSTAL-I-SYSDIR, This product creates system disk directory  SYS$SYSDEVICE:[MX.ALPHA_EXE]. R* Do you want to purge files replaced by this installation [YES]? [RET] .                          Component Selection  F    Select the MX components you wish to install from the menu below. D    An asterisk appears next to the packages that have already been F    selected.  You can remove a package from the list by selecting it E    again.  You may enter more than one selection by separating your     choices with commas.  (     1. [*] Base MX software (REQUIRED) #     2. [ ] NETLIB network support #     3. [ ] SMTP interface support %     4. [ ] SMTP-over-DECnet support ,     5. [ ] Site-provided interface support -     6. [ ] Mailing List/File Server support '     7. [ ] LISTSERV interface support      8. [*] Documentation '     9. [ ] Example files and programs 0    10. [ ] User-contributed files and programs      11.     Exit   <*       Your choice [11]: 3[RET]O%MX-I-WILLDONETLIB, Will also install NETLIB network support for SMTP support. 




 

"
.                          Component Selection  F    Select the MX components you wish to install from the menu below. D    An asterisk appears next to the packages that have already been F    selected.  You can remove a package from the list by selecting it E    again.  You may enter more than one selection by separating your     choices with commas.  (     1. [*] Base MX software (REQUIRED) #     2. [*] NETLIB network support #     3. [*] SMTP interface support %     4. [ ] SMTP-over-DECnet support ,     5. [ ] Site-provided interface support -     6. [ ] Mailing List/File Server support '     7. [ ] LISTSERV interface support      8. [*] Documentation '     9. [ ] Example files and programs 0    10. [ ] User-contributed files and programs      11.     Exit   **       Your choice [11]: [RET] 0    You have selected the following components:          Base MX software         NETLIB network support         SMTP interface support         Documentation   )* Is this correct [YES]? [RET]7%VMSINSTAL-I-RESTORE, Restoring product save set B ... F%MX-I-INSTALL_NETLIB, Installing NETLIB library for TCP/IP support... L%MX-I-NETLRNOT, Release notes for NETLIB V2.3 have been copied to SYS$HELP. 7%VMSINSTAL-I-RESTORE, Restoring product save set D ...  .%NETLIB-I-INSTALVERS, Installing NETLIB V2.3.  0                       TCP/IP Support Selection  B    Select the NETLIB TCP/IP support you wish to install from the D    menu below.  An asterisk appears next to the packages that have C    already been selected.  You can remove a package from the list B    by selecting it again.  You may enter more than one selection ,    by separating your choices with commas.  $     1. [ ] Digital TCP/IP Services      2. [*] Process MultiNet      3. [ ] Process TCPware      4. [ ] Attachmate PathWay       5.     Exit   )*       Your choice [5]: [RET] 4    You have selected the following TCP/IP support:          Process MultiNet   )* Is this correct [YES]? [RET]  3                     Choosing the NETLIB Directory  A    The NETLIB libraries can be placed in any directory, as long A    as that directory is accessible to all users who plan to use *    or develop NETLIB-based applications.  ^* Where should the NETLIB libraries be placed [SYS$SYSDEVICE:[MX.ALPHA_EXE]]: [RET]_%VMSINSTAL-I-SYSDIR, This product creates system disk directory  SYS$SYSDEVICE:[MX.ALPHA_EXE]. >%CREATE-I-EXISTS, SYS$SYSDEVICE:[MX.ALPHA_EXE] already exists  @    The installation will continue for another 5 to 45 minutes, =    depending on your CPU type, distribution media, etc.  No =    further input is required during the installation.  Once <    installation has completed, you may be asked additional     configuration questions.  7%VMSINSTAL-I-RESTORE, Restoring product save set F ... 7%MX-I-INSTALL_BASE, Installing the MX base software... \%VMSINSTAL-I-SYSDIR, This product creates system disk directory  SYS$SYSDEVICE:[MX.ROUTER]. [%VMSINSTAL-I-SYSDIR, This product creates system disk directory  SYS$SYSDEVICE:[MX.LOCAL]. l%MX-I-LICENSEASK, You will be asked to register your MX license key at the end of the installation process. 7%VMSINSTAL-I-RESTORE, Restoring product save set H ... /%MX-I-INSTALL_SMTP, Installing SMTP support... Z%VMSINSTAL-I-SYSDIR, This product creates system disk directory  SYS$SYSDEVICE:[MX.SMTP]. _%VMSINSTAL-I-SYSDIR, This product creates system disk directory  SYS$SYSDEVICE:[MX.SMTP.LOCK]. 7%VMSINSTAL-I-RESTORE, Restoring product save set L ... 5%MX-I-INSTALL_DOC, Installing documentation files... Y%VMSINSTAL-I-SYSDIR, This product creates system disk directory  SYS$SYSDEVICE:[MX.DOC].  (    MX installation procedure complete.  F    Be sure to follow the post-installation instructions described in D    the MX Installation Guide.  This will minimally include editing C    the system startup procedure to include the following command:  )               $ @SYS$STARTUP:MX_STARTUP  O%VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... 




GSince this is a first-time installation, the MX installation procedure Dasks licensing and configuration questions once the files have been "moved to their target directories.

 

"
     MX License Management     ---------------------  E    MX requires a license key for its operation.  If you do not have H    a license key for MX, a temporary evaluation key will be registered 3    in the license database for you automatically.  




 

"
O* Do you have a license key for MADGOAT MX? NO[RET] M    Use of this software is subject to the terms set forth in the Evaluation O    License Agreement.  If you have not yet read the License Agreement, please     do so now.  s* Would you like to display the text of the Evaluation License Agreement [YES]? NO[RET] Z* Do you agree to the terms of the License Agreement? YES[RET] E    Registering an evaluation license key now.  This key will expire B    in 30 days.  After evaluating MX, contact MadGoat Software to -    purchase a full license for the product.  G%MGLIC-S-REGISTERED, license MADGOAT MX registered in license database [%MGLIC-W-EXPIRING, license MADGOAT MX (authorization AUTO-EVAL) will expire on  9-FEB-2001 E%MGLIC-S-LOADED, license MADGOAT MX successfully loaded with 0 units  H    The MXCONFIG command procedure may now be run to assist in creating !    an initial MX configuration.  <* Would you like to run MXCONFIG now [YES]? [RET]     Message Queue Directory     -----------------------  O    MX uses a directory tree for storing queued mail messages.  This directory L    tree may be placed with the other MX directories, or may be placed on a H    different disk.  The disk on which the queue directory resides must I    have quotas disabled or must have sufficient system quota to provide +    for a backlog of undelivered messages.  @Message queue root directory [MX_ROOT:[QUEUE]]: [RET]+%CREATE-I-CREATED, MX_ROOT:[QUEUE] created  /    Selecting the Size of the MX Message Queue /    ------------------------------------------  D    The MX queueing subsystem uses a fixed-size sequential file for B    queue control.  The size of the file determines the number of D    messages that can be in the queue at any one time.  The size of C    the file can be extended at a later date using the MCP command     QUEUE EXTEND.  C    For each message, one block is required.  To allow up to 5,000 E    messages to be in the queue at any one time, the queue file must A    be slightly larger than 5,000 blocks. The required file size @    depends heavily on your site's e-mail traffic.  The minimum "    required size is 100 entries.  B    For sites with a lot of mail traffic, a size of 5,000--10,000 D    blocks is recommended.  If disk space is not a problem, you can E    specify as many as 131,072 (128K) messages, which is the maximum %    number MX is designed to handle.  IMaximum number of entries to allow in the queue? [5000]: [RET]L%MCP-I-QNEWQFL, creating new system message queue file for 5000 entries.... B%MCP-I-QNEWQDN, new system message queue created for 5000 entries -%CREATE-I-CREATED, MX_ROOT:[QUEUE.1] created -%CREATE-I-CREATED, MX_ROOT:[QUEUE.2] created -%CREATE-I-CREATED, MX_ROOT:[QUEUE.3] created -%CREATE-I-CREATED, MX_ROOT:[QUEUE.4] created -%CREATE-I-CREATED, MX_ROOT:[QUEUE.5] created -%CREATE-I-CREATED, MX_ROOT:[QUEUE.6] created -%CREATE-I-CREATED, MX_ROOT:[QUEUE.7] created -%CREATE-I-CREATED, MX_ROOT:[QUEUE.8] created -%CREATE-I-CREATED, MX_ROOT:[QUEUE.9] created  $    MX Message Queue "Cluster" Name $    -------------------------------  F    This is a 1-to-6 character name that is used to coordinate access G    to the message queue.  If this system is part of a VMScluster, all D    systems in the cluster that share this MX installation will use )    the same message queue cluster name.  L    For further information on MX cluster support, see the Manager's Guide.  B    This name is typically set to the DECnet cluster alias or the *    DECnet node name of the local system.  5Message queue cluster name [MLHOST]: [RET] ,    Immediate Deletion of Finished Messages ,    ---------------------------------------  F    When an MX queue entry has been fully processed,  it is marked as F    being "finished" and  is  left in the queue for a period of time. F    The MX Router or MX FLQ Manager scans the file every  15 minutes, A    by default, and purges the finished entries.  This delay can H    improve responsiveness of the delivery agents and reduce contention     for the message queue.  I    However, sites processing a high volume of messages may need to have E    the finished queue entries deleted immediately on completion, in B    order to reclaim message queue and file system resources more 
    quickly.  GShould finished messages be deleted immediately? [NO]: [RET] 




 

"
    Maximum Message Size     --------------------  C    You may set a fixed limit on the size of messages that MX will C    accept.  Any message that is larger than this fixed limit will B    be rejected by the message entry agents.  The maximum size is     specified in KBytes.  C    By default, the maximum size is zero, meaning that there is no     fixed limit.  7Maximum message size (in KBytes)? [0]: [RET] 0    Reserved Free Space on Message Queue Device 0    -------------------------------------------  B    MX limits the size of messages it accepts based on the amount A    of free space available on the disk device where the message     queue resides.  A    You may reserve a percentage of the total space on the disk. B    MX will ensure that it accepts no message that will cause the >    amount of remaining free space to drop below the reserved     amount.  B    By default, the reserved free space setting is 10%.  The free -    space percentage may range from 1 to 90.  BPercentage of disk space to reserve (1-90)? [10]: [RET]     MX Network Host Name     --------------------  C    This is a 1-to-255 character name that is your "official" host     name for E-mail purposes.  B    For Internet hosts, this should be your Internet domain name. $    (Example: myhost.mycompany.com)  B    For hosts not connected to the Internet, consult your network ?    consult your network manager for an appropriate host name.  GEnter the MX network host name [MAILHOST.MADGOAT.COM]: [RET] K    MX timezone information will be taken from the system timezone setting 3    in the logical name SYS$TIMEZONE_DIFFERENTIAL.   #    MX Message Queue Manager Agent #    ------------------------------  I    If this MX installation will be handling a large volume of messages, E    it is recommended that you run a separate Queue Manager agent to G    maintain the message queue.  For small installations, the separate K    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]MEnter names of VMScluster nodes to run MX Queue Manager [*]: [RET]     MX Processing Agents     --------------------  G    You will now be asked to specify startup information for the other $    installed MX processing agents.  ADo you want to run the MX Message Router? [YES]: [RET]NEnter names of VMScluster nodes to run MX Message Router [*]: [RET]MHow many MX Message Router processes should be started? [1]: [RET]GDo you want to run the MX Local Delivery Agent? [YES]: [RET]TEnter names of VMScluster nodes to run MX Local Delivery Agent [*]: [RET]SHow many MX Local Delivery Agent processes should be started? [1]: [RET]FDo you want to run the MX SMTP Delivery Agent? [YES]: [RET]SEnter names of VMScluster nodes to run MX SMTP Delivery Agent [*]: [RET]RHow many MX SMTP Delivery Agent processes should be started? [1]: [RET]>Do you want to run the MX SMTP Server? [YES]: [RET]KEnter names of VMScluster nodes to run MX SMTP Server [*]: [RET]     SMTP Server Connections     -----------------------  @    The MX SMTP Server can be configured to handle from 1 to 36 D    simultaneous incoming connections.  In VMScluster environments, =    this configuration setting affects all nodes running the     SMTP server.  OEnter maximum number of SMTP server connections to allow [16]: [RET] C    This procedure builds an MCP command file which will create an '    initial MX configuration database.  K    First-time MX managers should use this command procedure as a starting A    point, then tailor the resulting MCP command file as needed.  




 

"
E    NOTE:  In the following questions, when asked for an ADDRESS, be F           sure to specify a full E-mail address, even if the address            is local. 7                       Example:  user@host.company.ORG  R* What do you want to call the command file? [MX_DIR:CONFIG.MCP]: [RET] 3                           Delivery Path Selection  B    Select the delivery paths you are using with MX from the menu C    below.  Selected items are marked with an asterisk ("*").  You D    can remove a delivery path from the list by selecting it again. E    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] 3                           Delivery Path Selection  B    Select the delivery paths you are using with MX from the menu C    below.  Selected items are marked with an asterisk ("*").  You D    can remove a delivery path from the list by selecting it again. E    You may enter more than one selection by separating your choices     with commas.       1. [*] SMTP over TCP/IP       2.     Exit   (*      Your choice [2]: [RET] 4    You have selected the following delivery paths:          SMTP over TCP/IP   +* Is this correct?  [Yes]: [RET]     TCP/IP (SMTP) Information  E    MX must be configured to recognize all possible names that could H    be used by other hosts on the network to identify the local system:  )        Examples:   myhost.mycompany.COM 9                    myhost                (abbreviation)  D    It must also be able to recognize the bracketed, dotted-decimal %    IP address for the local system:  #        Example:    [128.113.5.15]   J    In a VAXcluster with multiple TCP/IP-connected hosts you should enter J    the node name(s) and bracketed address for each host connected to the     TCP/IP network.  E    When are finished entering node names, just press RETURN to move     on to the next question.   Y* Enter a local Internet node name: mailhost.madgoat.com[RET] :* Enter another local Internet node name: [RET] $    Defining the "Postmaster" Alias  G    If you have not set up a username on the system called POSTMASTER, G    you should create an alias in MX for username Postmaster to direct 5    mail to the person performing postmaster duties.  A    All Internet- and BITNET-connected systems MUST have a valid     Postmaster address.  @    If you have a valid POSTMASTER account on your system, just ?    press RETURN.  Otherwise, enter a full (user@host) address ?    to which all Postmaster-addressed messages should be sent.  i* Enter an alias for Postmaster (user@host): system@mailhost.madgoat.com[RET] /    There are no more configuration questions.  Q* Would you like to run MCP now to build the configuration? [Y]: [RET]! MX_DEVICE:[MX]CONFIG.MCP;1 @! Created: 10-JAN-2001 07:46:33.76 by MX_CREATE_CONFIG_DATABASE ! )DEFINE PATH "mailhost.madgoat.com" LOCAL 8! NOTE: The next path definition should always be LAST. DEFINE PATH * SMTP ! !! Done with routing information. ! 8DEFINE ALIAS "Postmaster" "system@mailhost.madgoat.com" QDEFINE ALIAS "POSTMAST" "system@mailhost.madgoat.com" ! for BITNET compatibility M%MCP-I-WROTECFG, wrote configuration to file MX_DEVICE:[MX]MX_CONFIG.MXCFG;1 JSave agent and logical name configuration changes? [YES]: [RET] , Installation of MX V5.2 completed at 07:46  ?    Adding history entry in VMI$ROOT:[SYSUPD]VMSINSTAL.HISTORY  E    Creating installation data file: VMI$ROOT:[SYSUPD]MX052.VMI_DATA  # VMSINSTAL procedure done at 07:47 





L

Appendix B
Contents of Distribution Kit




EMX is provided in a VMSINSTALlable distribution kit consisting of 14 esave sets. Each save set is briefly described in Table B-1.

M  # #                                                          
Table B-1 MX installation kit save sets
Save Set Contents
MX051.A 3 Kit files and common base installation files.
MX051.B ' NETLIB common installation files.
MX051.C $ NETLIB VAX installation files.
MX051.D & NETLIB Alpha installation files.
MX051.E $ Base installation files (VAX).
MX051.F & Base installation files (Alpha).
MX051.G 1 MX SMTP (TCP/IP, DECnet, X.25) files (VAX).
MX051.H 3 MX SMTP (TCP/IP, DECnet, X.25) files (Alpha).
MX051.I = MX SITE, UUCP, MLF, and ListServ interface files (VAX).
MX051.J ? MX SITE, UUCP, MLF, and ListServ interface files (Alpha).
MX051.K 2 Mailing List/File Server (MLF) common files.
MX051.L N Documentation files, in PostScript, Bookreader, and plain ASCII formats.
MX051.M  Examples.
MX051.N % Contributed software and files.



Q

Appendix C
Files Created During Installation




qThe 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 Ddirectory MX_ROOT:[CONTRIB], if the contributed files are installed.

\The following notes are referenced in Table C-1:

    )
  1. Only if ML/FS support is installed.)
  2. Only if Documentation is installed.%
  3. Only if Examples are installed.,
  4. Only if SMTP-over-DECnet is installed.(
  5. Only if SMTP support is installed.(
  6. Only if UUCP support is installed.(
  7. Only if SITE support is installed.*
  8. Only if NETLIB support is installed.*
  9. Only if SMTP-over-X.25 is installed.,
  10. Only if LISTSERV support is installed.


b  $ &   9       >                                               D                                                                                               I                                                                               V                                                                                                                                                                       D       R                               B           A           F          
Table C-1 Message Exchange files created during installation
File name Description
Files in MX_FLQ_DIR:
 MX_SYSTEM_QUEUE.FLQ_CTL " System queue sequential file
Files in MX_ROOT:[000000]
MGLICENSE_DATABASE.MGLICDB  License key database
 MXALIAS_MAIN.HLP 1 Top-level MXALIAS help file 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 REJMAN utility
 MLF_CONFIG.COM , ML/FS configuration procedure (Note 1)
 MX_LICENSE.COM . Command procedure for license management
 MXCONFIG.COM ) MX configuration creation procedure
# MX_CREATE_CONFIG_DATABASE.COM 2 MX configuration database creation procedure
 MX_LOGICALS.DAT 7 Logical name definitions used by MX___STARTUP.COM
 MX_STARTUP_INFO.DAT . Describes which MX processes get started
Files in MX_ROOT:[DOC] (Note 2)
 INDEX.HTML ( Index of HTML documentation (HTML)
MX_INSTALL_GUIDE.DECW$BOOK % Installation guide (Bookreader)
 MX_INSTALL_GUIDE.HTML  Installation guide (HTML)
 MX_INSTALL_GUIDE.PS % Installation guide (PostScript)
 MX_INSTALL_GUIDE.TXT Installation guide (ASCII)
 MX_LIBRARY.DECW$BOOKSHELF . Library file for MX Bookreader documents
 MX_MGMT_GUIDE.DECW$BOOK # Management guide (Bookreader)
 MX_MGMT_GUIDE.HTML  Management guide (HTML)
 MX_MGMT_GUIDE.PS # Management guide (PostScript)
 MX_MGMT_GUIDE.TXT  Management guide (ASCII)
 MX_MLF_GUIDE.DECW$BOOK 1 Mailing List/File Server guide (Bookreader)
 MX_MLF_GUIDE.HTML + Mailing List/File Server guide (HTML)
 MX_MLF_GUIDE.PS 1 Mailing List/File Server guide (PostScript)
 MX_MLF_GUIDE.TXT , Mailing List/File Server guide (ASCII)
 MX.DECW$BOOKSHELF 0 Bookshelf file for MX Bookreader documents
 MX_PROG_GUIDE.DECW$BOOK % Programmer's guide (Bookreader)
 MX_PROG_GUIDE.HTML  Programmer's guide (HTML)
 MX_PROG_GUIDE.PS % Programmer's guide (PostScript)
 MX_PROG_GUIDE.TXT Programmer's guide (ASCII)
 MX_USER_GUIDE.DECW$BOOK  User guide (Bookreader)
 MX_USER_GUIDE.HTML  User guide (HTML)
 MX_USER_GUIDE.PS  User guide (PostScript)
 MX_USER_GUIDE.TXT  User guide (ASCII)
Files in MX_ROOT:[EXAMPLES] (Note 3)
 00README.ADDRESS_REWRITER ' README file for address rewriter.
 00README.NAME_CONVERSION - README file for name conversion module.
 ACCESS_CHECK_EXAMPLE.C 3 Sample callout for SMTP client access checks.
 ADDRESS_REWRITER.B32 ( BLISS source for address rewriter.
 ADDRESS_REWRITER.C $ C source for address rewriter.
 ADDRESS_REWRITER.MMS $ Makefile for address rewriter.
 AUTH_CALLOUT_EXAMPLE.C - Sample callout for SMTP authentication.
 CHARCONV_EXAMPLE.C . Sample character set conversion callout.
! CHARCONV_EXAMPLE_README.TXT D Documentation for the sample character set conversion callout.
 DOM_EXPANSION_CMU.B32 1 Sample domain name expander for CMU TCP/IP.
 DOM_EXPANSION_UCX.B32 1 Sample domain name expander for DEC TCP/IP.
 FILTER.C $ Sample message filter callout.
 MX_FILTERDEF.H 4 Header file for sample message filter callout.
 MX_FILTERDEF.R32 7 BLISS REQUIRE file for creating a message filter.
 MX_HDR.H / C header file with MX header definitions.
 NAME_CONVERSION.B32 . BLISS source for name conversion module.
 NAME_CONVERSION.MAR . MACRO source for name conversion module.
 NAME_CONVERSION.C * C source for name conversion module.
 VIRTDOM.ZIP L ZIP file containing a sample address-rewriter callout that implements " "virtual domains".
Files in MX_ROOT:[EXE] and in MX_ROOT:[ALPHA_EXE]
 DNSMTP_SERVER.EXE / SMTP-over-DECnet receiver module (Note 4)
 DOMAIN_EXPANSION.EXE # Domain name expander (Note 5)
 MAILQUEUE.EXE 3 Program for listing delayed messages in queue
MCP.EXE  MX Control Program
 MGLICENSE.EXE License management utility
 MLFAKE.EXE 9 Utility for faking messages to mailing list servers
 MXALIAS.EXE % Utility for defining MX aliases
 MX_DECODE.EXE , Utility to decode BASE64 mail messages
 MX_DNSMTP.COM 1 SMTP-over-DECnet command procedure (Note 4)
 MX_DNSMTP.EXE / SMTP-over-DECnet delivery module (Note 4)
 MX_FLQ_MGR.COM & MX FLQ Manager command procedure
 MX_FLQ_MGR.EXE  MX FLQ Manager
 MX_FLQ_SHR.EXE . Shareable image implementing file queues
 MX_LOCAL.EXE  MX Local delivery module
 MX_LSV.COM 7 MX LISTSERV interface command procedure (Note 10)
 MX_LSV.EXE , MX LISTSERV interface module (Note 10)
 MX_MAILSHR.EXE ) VMS MAIL foreign protocol interface
 MX_MAILSHRP.EXE 5 Service routines for foreign protocol interface
 MX_MLF.COM 9 Mailing list/file server command procedure (Note 1)
 MX_MLF.EXE . Mailing list/file server module (Note 1)
 MX_MSG.EXE  Messages file
 MX_RMAIL.EXE ( UUCP mail entry interface (Note 6)
 MX_ROUTER.COM ! MX Router command procedure
 MX_ROUTER.EXE  MX Router module
 MX_SHR.EXE * MX common routines shareable library
 MX_SITE.COM < Command procedure used by site-spec interface (Note 7)
 MX_SITE.EXE ' Site-spec delivery agent (Note 7)
 MX_SITE_IN.COM . Site-spec message entry program (Note 7)
 MX_SMTP.COM 7 SMTP outbound delivery command procedure (Note 5)
 MX_SMTP.EXE , SMTP outbound delivery module (Note 5)
 MX_SMTP_MSG.EXE 8 Message file for delivery status and SMTP messages
 MX_START.COM 2 Command procedure for starting MX components
 MX_UUCP.COM * Used by UUCP delivery agent (Note 6)
 MX_UUCP.EXE " UUCP delivery agent (Note 6)
 MX_XSMTP.COM > SMTP-over-X.25 delivery agent command procedure (Note 9)
 MX_XSMTP.EXE , SMTP-over-X.25 delivery agent (Note 9)
 MX___STARTUP.COM & Master startup procedure for MX.
 REJMAN.EXE  REJMAN utility
 SMTP_SERVER.COM 6 SMTP inbound receiver command procedure (Note 5)
 SMTP_SERVER.EXE + SMTP inbound receiver module (Note 5)
 XSMTP_SERVER.EXE 5 SMTP-over-X.25 inbound receiver module (Note 9)
Files in MX_ROOT:[MLF] (Note 1)
 FILESERV_HELP.TXT ( Help text for use with file server
Files in MX_ROOT:[MLF.MAILING_LISTS] (Note 1)
MLIST_ADD_MESSAGE.TEMPLATE + Template for mailing list add message
 MLIST_ADD_MESSAGE.TXT + Template for mailing list add message
$ MLIST_FORWARD_MESSAGE.TEMPLATE 2 Template for forwarded-to-list-owner message
 MLIST_FORWARD_MESSAGE.TXT 2 Template for forwarded-to-list-owner message
 MLIST_HELP.TXT * Help file for mailing list processor
# MLIST_REMOVE_MESSAGE.TEMPLATE / Template for mailing list removal message
 MLIST_REMOVE_MESSAGE.TXT / Template for mailing list removal message
Files in NETLIB_DIR: (Note 8)
 NETLIB_SHRXFR.EXE * NETLIB transport-independent library
 NETLIB_xxx_SHR.EXE ; NETLIB transport-specific library (one per transport)
Files in SYS$COMMON:[SYSHLP]
 MXvvn.RELEASE_NOTES  Release notes for MX
 NETLIBvvn.RELEASE_NOTES  Release notes for NETLIB
Files in SYS$COMMON:[SYS$STARTUP]
 MX_STARTUP.COM  Startup procedure for MX
 NETLIB_STARTUP.COM + Startup procedure for NETLIB (Note 2)


 .
a Contents