MailWorks_for_UNIX____________________________ Installation Part Number: AA-Q4M8F-TH August 1996 This manual describes how to install MailWorks for UNIX[R] on a Digital UNIX system. It also describes how to install the Motif client on a SunOS[TM] or Solaris[R] system. Revision/Update Information: This is a revised manual. Operating System: Digital UNIX Version 3.2C or later Software Version: MailWorks for UNIX Version 2.0 __________________________________________________________ August 1996 Digital Equipment Corporation makes no representations that the use of its products in the manner described in this publication will not infringe on existing or future patent rights, nor do the descriptions contained in this publication imply the granting of licenses to make, use, or sell equipment or software in accordance with the description. Possession, use, or copying of the software described in this publication is authorized only pursuant to a valid written license from Digital or an authorized sublicensor. The postpaid Reader's Comments forms at the end of this document request your critical evaluation to assist in preparing future documentation. © Digital Equipment Corporation 1996. All rights reserved. The following are trademarks of Digital Equipment Corporation: DEC, DECnet, Digital, InfoBroker, MAILbus, MAILbus 400, MailWorks, TeamLinks, and the DIGITAL Logo. The following copyrights and notices apply to the xloadimage program, which is supplied as an image viewer with the MailWorks software: Copyright © 1989, 1990 Jim Frost, Kirk L. Johnson, Mark Majhor, Massachusetts Institute of Technology Permission to use, copy, modify, distribute, and sell the xloadimage software and its documentation for any purpose is hereby granted without fee, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation. The authors make no representations about the suitability of this software for any purpose. It is provided "as is" without express or implied warranty. The following are third-party trademarks: FrameMaker is a registered trademark of Frame Technology Inc. Motif, OSF, OSF/1, and OSF/Motif are registered trademarks of the Open Software Foundation. Microsoft and MS-DOS are registered trademarks of the Microsoft Corporation. SCO is a trademark of the Santa Cruz Operation, Inc. UNIX is a registered trademark of UNIX System Laboratories, Inc. a wholly-owned subsidiary of Novell, Inc. The X Window System is a trademark of the Massachusetts Institute of Technology. Macintosh is a registered trademark of Apple Computer, Inc. LDAP is a registered trademark of the Regents of the University of Michigan. SPARCstation and SunOS are trademarks of, and Solaris and Sun are registered trademarks of Sun Microsystems, Inc. This document was prepared using VAX DOCUMENT Version 2.1. ________________________________________________________________ Contents Preface.................................................. v 1 Preparing to Install MailWorks 1.1 Checking the Software Distribution Kit....... 1-1 1.2 Reading the Release Notes.................... 1-1 1.3 Login Privileges Requirements................ 1-1 1.4 Hardware Requirements........................ 1-1 1.5 Software Requirements........................ 1-2 1.5.1 Digital UNIX............................. 1-2 1.5.2 InfoBroker Server........................ 1-2 1.5.3 Mail Transport Agents.................... 1-3 1.5.4 DEC C++ Shareable Library................ 1-3 1.6 Disk Space Requirements...................... 1-3 1.7 Performing System Backup..................... 1-4 1.8 MailWorks Components......................... 1-4 1.9 Planning the X.400 API Client Name .......... 1-4 1.10 Setting Up the Local Directory File Search Base......................................... 1-5 1.11 Registering Your Software License............ 1-5 1.12 Saving Any Modified DMW-add Scripts.......... 1-7 1.13 Removing Prior Installations of MailWorks.... 1-8 1.14 Using MailWorks While Reinstalling........... 1-8 1.15 Stopping the Installation.................... 1-8 iii 2 Installing MailWorks 2.1 Installation Errors.......................... 2-1 2.2 Installing MailWorks......................... 2-2 2.3 Installing MailWorks on Additional Machines in Your Network.............................. 2-9 3 After Installing MailWorks 3.1 Updating the Enclosures Directory............ 3-1 3.2 Updating the MAILworksrc File................ 3-1 3.3 Updating the DMW-add Scripts................. 3-2 3.4 Providing an Alias for the Tutorial Message Stores....................................... 3-2 3.5 Using Fully Qualified Internet Domain Names........................................ 3-2 3.6 Running the Installation Verification Procedure ................................... 3-3 3.7 Setting up MailWorks to Work with a Remote MSR.......................................... 3-3 3.8 Running MailWorks............................ 3-3 A Installing the Motif Client on a SunOS or Solaris System A.1 Preparing to Install the SunOS or Solaris Kit.......................................... A-1 A.2 Installing the SunOS or Solaris Kit.......... A-2 A.3 After Installing the SunOS or Solaris Kit.... A-2 A.3.1 Editing the .forward File................ A-3 A.3.2 Enabling the SunOS or Solaris System to Locate the MailWorks Server.............. A-3 A.3.3 Starting MailWorks....................... A-4 B Contents of the Software Distribution Kit B.1 Contents of the Base Component............... B-1 iv C Removing a MailWorks Installation D Failures During Product Use Index Tables 1-1 Disk Space Requirements.................. 1-3 B-1 Files and Directories Installed in sharedDir................................ B-1 B-2 Files and Directories Installed in sharedDir/installDir..................... B-3 B-3 Files and Directories Installed in localDir................................. B-3 B-4 Linked Commands.......................... B-5 v ________________________________________________________________ Preface MailWorks for UNIX[R] is a mail server that includes a Motif[R] client for the Digital UNIX, SunOS[TM], and Solaris[R] operating systems, and supports the following existing PC-based mail clients for sending, receiving, organizing, querying, and sharing multimedia messages: o MailWorks for MS-DOS Version 1.2 and later o TeamLinks[TM] Mail for Windows Version 2.1 or later o TeamLinks Mail for Macintosh Version 2.1 or later o Microsoft[R] Mail Driver for MailWorks Intended Audience MailWorks for UNIX Installation Guide is intended for system managers or others who will install MailWorks for UNIX. Related Documentation For more information about MailWorks for UNIX, see the following books: o MailWorks for UNIX Workgroup/System Administration o MailWorks for UNIX Motif Client User's Guide o MailWorks for UNIX Release Notes This book does not explain the basics of administering Digital UNIX. For information about this topic, refer to your Digital UNIX operating system documentation. v Conventions The following conventions apply to this book. __________________________________________________________ Convention_______Meaning__________________________________ monospace Indicates a literal example of system output or user input. In text, indicates command names, keywords, node names, filenames, directories, utilities, and tools. italic Indicates a variable, for which you must supply a value. bold Indicates a new term. In a code example, it indicates user input. Indicates that you press the Return or Enter key. Indicates that you press the Control key while you press the key noted by X. | Separates items in a list of choices. . . . Indicates that you can repeat the preceding item one or more times. [ ] In command format descriptions, indicates optional elements. You can enter as many as you want. { } In command format descriptions, indicates you must enter at least one listed element. Entering When instructed to enter a command, type commands_________the_command_name,_and_press_Return.______ vi 1 ________________________________________________________________ Preparing to Install MailWorks This chapter provides information about what you need to do to prepare to install MailWorks. 1.1 Checking the Software Distribution Kit Use the Bill of Materials (BOM) included with your order to check the contents of your MailWorks software distribution kit. If your software distribution kit is damaged or incom- plete, contact your Digital[TM] representative. 1.2 Reading the Release Notes Digital recommends that you read the release notes before installing the MailWorks software. The release notes are located in the docs subset on the Digital UNIX Layered Product Consolidated Software Distribution disk. 1.3 Login Privileges Requirements To install and configure MailWorks and to register the software license Product Authorization Key (PAK), if required, you need superuser privileges. For more information about registering the PAK, see Section 1.11. 1.4 Hardware Requirements This section outlines the hardware required for you to install MailWorks. On your Digital UNIX [R] system, you need: o Software installation device name (if installing from media) Preparing to Install MailWorks 1-1 Locate the CD-ROM drive for the CD-ROM software distribution media. The CD booklet or the documentation for the CD-ROM drive you are using explains how to load the CD-ROM media. o Terminal You can use either a hardcopy or video terminal to communicate with the operating system and respond to prompts from the installation procedure. See the MailWorks Software Product Description (SPD) for additional hardware requirements. 1.5 Software Requirements This section outlines the software required for you to install MailWorks. You can use the /usr/sbin/setld -i command to see which software subsets are installed on your system. 1.5.1 Digital UNIX Your system must be running Digital UNIX Version 3.2C or later. See the MailWorks for UNIX Release Notes for a list of patches to Digital UNIX that MailWorks requires. 1.5.2 InfoBroker Server You must install InfoBroker Server Version 2.0 and related software before installing MailWorks. In addition, InfoBroker Server Version 2.0 requires the following subsets: o X.500 V2.0 DXDABASE200 subset o DECnet/OSI DNARFC1006300 and DNANETMAN300 subsets You will not need to configure DECnet or X.500, nor will you need DECnet or X.500 licenses. For information about installing the InfoBroker[TM] Server, see the InfoBroker Server Administration Guide. 1-2 Preparing to Install MailWorks 1.5.3 Mail Transport Agents To send mail to recipients outside of your local area network or to users of other UNIX mail systems, you need one or more of the following mail transport agents: o sendmail, the default Internet mail system provided with Digital UNIX o MAILbus 400[TM] Message Transfer Agent o DECnet/OSI for Digital UNIX or TCP/IP, for connections to MAILbus 400 For DECnet/OSI for Digital UNIX, you need the following subsets: - DECnet/OSI Base Components - DECnet/OSI Datalink Components 1.5.4 DEC C++ Shareable Library You must have the DEC C++ shareable library installed on your system. The DEC C++ shareable library, libcxx.so, is on the CDROM as part of the CXXSHRDAxxx subset, which you can find under ALPHA/DEC_C++_RTL. The library differs depending on which version of Digital UNIX you are using: o Digital UNIX Version 3.0-CXXSHRDA201 o Digital UNIX Version 3.2-CXXSHRDA305 1.6 Disk Space Requirements You need sufficient disk space to install the software. Table 1-1 summarizes the disk space requirements for MailWorks. Table_1-1_Disk_Space_Requirements_________________________ Subset_or_Directory________Disk_Space_Required____________ DMW subset 30 Mbytes MailWorks sharedDir 30 Mbytes (continued on next page) Preparing to Install MailWorks 1-3 Table_1-1_(Cont.)_Disk_Space_Requirements_________________ Subset_or_Directory________Disk_Space_Required____________ MailWorks_localDir_________less_than_1_Mbyte______________ To check the amount of disk space you have available, use the df command. 1.7 Performing System Backup Digital recommends that you back up your system before installing MailWorks. Refer to the your Digital UNIX system documentation for information about backing up your system. 1.8 MailWorks Components MailWorks consists of the following components. For a description of these components, see MailWorks for UNIX Workgroup/System Administration. o User agent o MailWorks compatibility server o Message store server o Message store registry o Transport service o Internet mail transport interface o X.400 mail transport interface o Local-store-and-forward daemon o Utilities for managing message stores 1.9 Planning the X.400 API Client Name If you plan to run the MailWorks X.400 mail transport interface, you need to supply the X.400 API client name. The client name must match the MAILbus 400 Message Transfer Agent (MTA) client name. 1-4 Preparing to Install MailWorks To obtain the current X.400 API client name, enter the following ncl command: ncl> show MTA Agent * See MailWorks for UNIX Workgroup/System Administration for more information about the X.400 mail transport interface. 1.10 Setting Up the Local Directory File Search Base The installation procedure prompts you for the information needed to set up local directory or X.500 database lookups. To set up lookups for your organization, substitute your organizational-unit (finance, for example), organization, and country for the defaults provided by the installation procedure. For more information about the local directory file and setting up search parameters, see MailWorks for UNIX Workgroup /System Administration. 1.11 Registering Your Software License You may need a software license Product Authorization Key (PAK) to install the MailWorks software. If a PAK is required, you will have to select the license PAK appropriate for your configuration. Use one of the following PAKs: o Server - MAILWORKS - MAILWORKS-USER o UNIX Client - MAILWORKS-CLIENT - MAILWORKS-CLIENT-USER To register your PAK, use the License Management Facility (LMF). LMF is a system management software tool that you use to comply with your license agreement. LMF offers options for many kinds of license agreements. Preparing to Install MailWorks 1-5 The terms and conditions of your contract determine your legal use of this software. LMF maintains the file of registered software license PAKs and keeps a library of functions used by licensed software. The following instructions show how you might register your MailWorks software license PAK using LMF: 1. Make sure that you have your PAK. 2. Log on to your system as a superuser. 3. Issue an lmfsetup command as follows: # lmfsetup 4. After you issue this command, you receive the following confirmation: # Register PAK (type q or quit to exit) [template] 5. Press Return. After you do this, you are prompted to answer a series of questions. These questions correspond to the fields on your PAK form. Use the information from your MailWorks PAK to reply to each question. Any fields that are left blank on the PAK should be left blank when you type in the data. 6. After you answer all the questions, you should receive a completion message like the following: PAK registered for template successfully 7. Leave lmfsetup by answering quit when this question appears as in this example: # Register PAK (type q or quit to exit) [template] quit 8. Issue an lmf reset command as follows: # lmf reset If the command was successful, go to step 7. If you attempted to load a PAK when a previous PAK was already loaded, you would receive an error message similar to the following: Combine pak-license SQM014419 with pak-license SQM010892 1-6 Preparing to Install MailWorks If you receive this kind of message, use the following instructions: a. List the license PAK templates using the following command: # lmf list full for pak-license b. Compare the information on the templates, and note the authorization number of the software license PAK you want to delete. c. Use the following command to delete the old PAK: # lmf delete pak-license DEC authorization-number d. Issue another lmf reset command. 9. Issue an lmf list command to verify your registration: # lmf list If you want to know how to obtain a license and PAK or how you use the LMF facility, refer to the Digital UNIX Guide to Software License Management. You can also refer to the lmf and lmfsetup man pages (lmf(8) and lmfsetup(8)) for information. 1.12 Saving Any Modified DMW-add Scripts When you remove the prior installation of MailWorks (see Section 1.13), the procedure removes the DMW-add scripts, which are used to create new users. If you have modified any DMW-add scripts, you must copy them to a different directory to avoid having them deleted. Follow these steps: 1. If the current version of MailWorks is V1.5, copy your modified scripts from the /usr/opt/DMWBASE150 /bin directory to a temporary directory. If the current version is V1.7, copy the scripts from /usr/opt/DMWBASE170/bin. If the current version is V2.0, copy the scripts from /usr/opt/DMWBASE200/bin. 2. After the installation, merge your saved scripts with the new ones in the directory /usr/opt/DMWBASE200/bin. Preparing to Install MailWorks 1-7 1.13 Removing Prior Installations of MailWorks Before installing MailWorks Version 2.0, delete any old versions of the subsets: o DMWBASE150 - the MailWorks Version 1.5 or Version 1.5B Base subset o DMWBASE170 - the MailWorks Version 1.7-A, ECO#1 and ECO#2 Base subset o DMWBASE200 - the MailWorks Version 2.0 Base subset (if you are reinstalling Version 2.0) Use the setld -d command to remove any previously installed MailWorks subsets. MailWorks user's message stores are not affected by the setld -d command. 1.14 Using MailWorks While Reinstalling Do not use MailWorks until the removal of files and reinstallation is complete and you have replaced the files from the kit with your customized saved files. Attempting to use MailWorks while removing and then reinstalling the product may produce undesirable results. Files shipped with the product might be used rather than files that you have customized, such as the Keys and MAILworksrc files or the enclosure database. Saved files are renamed filename.sav(n), where n is a number. The highest number is the most recently saved file. Saved files are located in the directory where they normally reside. 1.15 Stopping the Installation To stop the installation procedure at any time, press Ctrl-C. If you do this, the installation terminates before it completes. You must then interactively delete files created up to this point. For a list of the directories and files created during the MailWorks installation, see Appendix B. 1-8 Preparing to Install MailWorks 2 ________________________________________________________________ Installing MailWorks This chapter explains how to install the default configuration of MailWorks on the first (or only) machine in your network. For information about installing MailWorks on additional systems in your network, see Section 2.3. The installation procedure installs MailWorks into two directories: o localDir, which resides on each machine running MailWorks. localDir contains all machine-specific files and is known as the local directory. The MailWorks installation procedure defines /var/opt/DMW to be the local directory. o sharedDir, which can be shared among different machines. sharedDir contains all the files that can be shared among machines of the same architecture and is known as the shared directory. You can mount the shared directory on a read-only file system because all the files it contains are read-only. The MailWorks installation procedure defines /usr/opt/DMW to be the shared directory. The installation takes approximately 5 to 10 minutes, depending on your hardware configuration. 2.1 Installation Errors If you receive errors from the setld utility during the installation, make sure you have the correct prerequisite software and disk space. Refer to the Diagnostics section of the setld man page for further information. Installing MailWorks 2-1 2.2 Installing MailWorks To install the software from the CDROM (the Digital UNIX Layered Product Consolidated Software Distribution disk), use the following steps: 1. Determine the directory of the MailWorks files. Refer to the Master Index table in the Consolidated Software Distribution Disk User's Guide for the name of the directory on the CDROM that contains the MailWorks software. 2. Log on as superuser (login name root) on the system where you are installing MailWorks. 3. Make sure you are at the root (/) directory: # cd / 4. Insert the disk into the drive and determine the device name for the drive. Use the following command to list the available disk devices. The drive you are using will be either RRD40 or RRD42. # file /dev/rrz*c 5. Mount the disk, using your device's name and the following command: # mount -r -d /dev/device_name /mnt ________________________Note ________________________ If the mount point /mnt does not exist, create it with the mkdir /mnt command. _____________________________________________________ 6. Install the software on your system, using the software's directory name and this setld(8) command: # setld -l /mnt/directory_name directory_name represents the directory which contains the MailWorks files. 2-2 Installing MailWorks After you enter the setld command, the installation procedure displays the names of the MailWorks subsets and asks you to specify the subsets that you want to load. 7. After entering setld -l, the system displays a menu, and as the install script runs, you receive a number of prompts and messages. The subsets listed below are optional: There may be more optional subsets than can be presented on a single screen. If this is the case, you can choose subsets screen by screen or all at once on the last screen. All of the choices you make will be collected for your confirmation before any subsets are installed. 1) MailWorks Version 2.0 BASE for Digital UNIX Or you may choose one of the following options: 2) ALL of the above 3) CANCEL selections and redisplay menus 4) EXIT without installing any subsets Enter your choices or press RETURN to redisplay menus. Choices (for example, 1 2 4-6): 1 If you specify more than one number at the prompt, separate each number with a space, not a comma. 8. The procedure verifies your choices. You are installing the following optional subsets: MailWorks Version 2.0 BASE for Digital UNIX Is this correct? (y/n): y If the displayed subsets are not the ones you intended to choose, enter n. The subset selection is displayed again, and you can correct your choice of subsets. If the displayed subsets are the ones you want to load, enter y. The installation continues and some status messages and copyright information appear. Installing MailWorks 2-3 Checking file system space required to install selected subsets: File system space checked OK. MailWorks V2.0 Installation Procedure Copyright Digital Equipment Corporation 1993, 1994, 1995, 1996 All rights reserved. Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c) (1) (ii) of DFARS 252.227-7013, or in FAR 52.227-19, or in FAR 52.227-14 Alt. III, as applicable. This software is proprietary to and embodies the confidential technology of Digital Equipment Corporation. Possession, use, or copying of this software and media is authorized only pursuant to a valid written license from Digital or an authorized sublicensor. The installation will complete in 3 to 5 minutes depending on the processor type. MailWorks Version 2.0 BASE for Digital UNIX Copying from . (disk) Working....Mon Jun 17 08:46:30 EDT 1996 Verifying 9. The procedure may check your system for the presence of the software license for MailWorks. If the PAK is not found, a status message indicates that, and the installation continues. MailWorks may not run unless this PAK is registered on this system, so you may have to register a license on this system before the MailWorks processes start. The MailWorks for UNIX Product Authorization Key (PAK) has been found on this system 10.The procedure asks you for the pathname for user commands. Digital recommends that you use the default directory, /usr/bin. (These commands are linked rather than copied.) The commands are listed in Table B-4. Enter directory pathname (or 'none') for user commands, [./usr/bin]: Make sure all MailWorks command language users have /usr/opt/DMW/clbin in their PATH. 2-4 Installing MailWorks 11.The procedure asks if you want the online manual pages (man pages) installed on this machine. Press Return to select the default. If you select the default or answer yes, you are prompted for the location in which to install the man pages. The default action of installing the man pages is taken in the following example. If you don't want to install the man pages now, you can answer 'no' to the next question and run the install command again later. Both unformatted and formatted man pages can be installed. Do you want to install the MailWorks man pages? (y/n) [y] Enter the man directory for unformatted user commands (or 'none') [./usr/man/man1]: Installing man pages for user commands Enter the man directory for formatted user commands (or 'none') [./usr/man/cat1]: Installing man pages for user commands Enter the man directory for unformatted administrative commands (or 'none') [./usr/man/man8]: Installing man pages for administrative commands Enter the man directory for formatted administrative commands (or 'none') [./usr/man/cat8]: Installing man pages for administrative commands 12.If it is not already present from a previous in- stallation, the procedure asks if this machine will have the tutorial message store on it. The tutorial message store should be installed on one machine in the network. Do you want the tutorial message store installed on this machine? (n/y) [y]: Copying the MailWorks app-defaults file to ./usr/lib/X11/app-defaults Adding symbolic links for boot-time startup. 13.The procedure asks if this machine will have the message store registry on it. Usually, you place the message store registry on one machine on your LAN, such as the machine that acts as a communication server in your network. Installing MailWorks 2-5 If you are installing MailWorks on the first machine in the network, enter y. If you are installing MailWorks on additional machines, enter n, unless you have read the MailWorks for UNIX Workgroup/System Administration guide for information about setting up multiple message store registries. Will this machine be the one machine in your network running the Message Store Registry? (y/n) [y] The procedure asks if you want to accept POP3 connections. Enter y if you want to allow clients who are using POP3 to fetch mail from the MailWorks message store. Would you like MailWorks to accept POP3 connections? (y/n) [y] Note that there are sample scripts and templates in /usr/opt/DMW/installDir/scripts and /usr/opt/DMW/installDir/templates Execute /usr/opt/DMW/bin/startMAILworks to activate the MailWorks server processes immediately. See the MailWorks for UNIX Workgroup/System Administration for further configuration information. 14.The procedure provides default information for the sample local directory file included with MailWorks. If you do not want the defaults, the procedure prompts you for the information needed to set up your local directory or X.500 database lookups. Enter your organizational-unit (finance, for example), organization, and country. For more information, see the discussion of setting up search parameters in MailWorks for UNIX Workgroup /System Administration. To enter a blank value in a field wich contains a default, enter a period. The directory local-search-base default is: Organizational Unit = ZKO, Organization = DEC, Country = US. Accept the default? (y/n) [n] : n 2-6 Installing MailWorks Enter organizational-unit for directory local search [ ZKO ] : SALES Enter organization for directory local search [ DEC ] : ACME Enter country for directory local search [ US ] : US The directory escalated-search-base default is: Organizational Unit = LKG, Organization = DEC, Country = US. Accept the default? (y/n) [n] : n Enter organizational-unit for directory escalated search [ LKG ] : SALES Enter organization for directory escalated search [ DEC ] : ACME Enter country for directory escalated search [ US ] : US The directory world-search-base default is: Organization = DEC, Country = US. Accept the default? (y/n) [n] : n Enter organization for world search [ DEC ] : ACME Enter country for world search [ US ] : US Enter country for directory complete search [ US ] : US Modifying /etc/services. 15.Provide the name of the node where the InfoBroker Server will run. The installation procedure provides a default for your node. Enter the name of the node on which the InfoBroker will run [local-system]: 16.If you are using a MAILbus 400 Message Router gateway (XMR), provide the X.400 address. Enter the address in business card format (for example, c=us; a=admd; p=myhost; o=myorg; ou1=1) To find your XMR address, log into the system that is running XMR and enter one of the following commands: o $ Type XMR$DATA:XMR$CONFIG.DAT The value for gateway_orname is the XMR X.400 address. Installing MailWorks 2-7 o $ RUN SYS$SYSTEM:NCL NCL> show xmr oraddress The ORAddress returned is the XMR X.400 address. Do you want to define an X400/Message Router Gateway ? (y/n) [n] : y What is the X400 address of the X400/Message Router Gateway? : c=us; a=admd; p=myhost; o=myorg; ou1=1 17.Provide the name of the X.400 API client: Enter X.400 interconnect API Client name [MAILworks]: Press Return when prompted for the API client name to select MailWorks as the default API client name. The API client name must match the client name on the Message Transfer Agent (MTA). 18.The procedure checks the system configuration: What is the maximum number of users acessing the MailWorks server at one time? System name: local-system Current Values: maxusers: 32 vpagemax: 16384 mapentries: 200 Required Values: maxusers: 512 vpagemax: 64000 mapentries: 400 -> It is recommended that your maxusers parameter be increased to 512 -> It is recommended that your vpagemax parameter be increased to 64000 -> It is recommended that your mapentries parameter be increased to 400 -> Please see the MailWorks for Digital UNIX Release Notes for more details -> The DMW-system-check script is available in the /usr/opt/DMW/bin directory. -> Use this to recheck your system after configuration changes are complete. 2-8 Installing MailWorks 19.The procedure asks if you want to run the IVP. You can do so now or at another time. You may run the IVP at any time after the installation by issuing the command, setld -v DMWBASE200 Would you like to run the MailWorks IVP now? (y/n) [y] Running the MailWorks Installation Verification Procedure Copyright Digital Equipment Corporation 1993, 1994, 1995, 1996 All rights reserved. IVP terminated with success Configuring "MailWorks Version 2.0 BASE for Digital UNIX" (DMWBASE200) If the IVP fails, examine the /var/opt/DMW/logs/ivplog file. It will contain information to help you diagnose the problem. The MailWorks installation is complete. Chapter 3 discusses other actions that may be necessary after you install MailWorks. 2.3 Installing MailWorks on Additional Machines in Your Network To install MailWorks on additional systems in your network, follow the procedures described in Section 2.2. You will need a software license (PAK) for each system. When installing on additional systems, keep the following in mind: o There should be only one Message Store Registry running in a local area network broadcast area, unless you intend to configure multiple mailgroups as described in MailWorks for UNIX Workgroup/System Administration. o The X.400 Interconnect component should only run on one system for each MailWorks group, unless you intend to configure multiple mailgroups as described in MailWorks for UNIX Workgroup/System Administration. Installing MailWorks 2-9 3 ________________________________________________________________ After Installing MailWorks After installing MailWorks you may need to do some of the following tasks in this chapter, depending on your particular configuration. 3.1 Updating the Enclosures Directory If you have installed a previous version of MailWorks on this system and have modified any files in the /usr /opt/DMW/Enclosures directory, you need to merge the information in the new Enclosures directory with that in the old directory. The installation procedure renames the old directory to /usr/opt/DMW/Enclosures.sav*, where * is a number one higher than the previous version in that directory. For example, if the installation procedure detects an existing file Enclosures.sav1 in the directory, it saves the current directory to Enclosures.sav2. 3.2 Updating the MAILworksrc File If you have installed a previous version of MailWorks on this system and have modified the /usr/opt/DMW/MAILworksrc file, you need to merge the information in the new MAILworksrc file with that in the old file. The installation procedure renames the old file to /usr /opt/DMW/MAILworksrc.sav*, where * is a number one higher than the previous version in that directory. For example, if the installation procedure detects an existing file MAILworksrc.sav1 in the directory, it saves the current file to MAILworksrc.sav2. After Installing MailWorks 3-1 3.3 Updating the DMW-add Scripts If you have copied your modified DMW-add scripts to a temporary directory (see Section 1.12), merge them with the Version 2.0 scripts in the directory /usr/opt /DMWBASE170/bin. 3.4 Providing an Alias for the Tutorial Message Stores If you are installing MailWorks for the first time on this system and it contains the tutorial message store, give the tutorial message store an alias by entering the following command: # msrset MAILworks-Tutorial hostname/var/opt/DMW/tutorial.po In this example, hostname is the name of this machine and localDir specifies the full pathname of the local directory. (Be aware that there is a thirty-second delay when starting the message store registry (msr) process, so if you give this command before thirty seconds have passed, it may return with an error.) 3.5 Using Fully Qualified Internet Domain Names If this system contains the message store registry (msr), and this site has an Internet domain name (for example, dec.com), and the hostname of this machine is not fully qualified (for example, the hostname command returns ace, rather than ace.dec.com), tell the registry by entering the following command: # msrset -domain xxx.yyy xxx.yyy represents the Internet domain name for this site. For the example given above (ace.dec.com), xxx.yyy would be dec.com. This causes MailWorks to use the fully qualified domain name when generating message IDs, rather than simply the host name. There is no need to use the msrset command if the hostname is fully qualified (the hostname command returns a fully qualified hostname). 3-2 After Installing MailWorks 3.6 Running the Installation Verification Procedure After installing MailWorks, you can run the Installation Verification Procedure (IVP) independently to verify that the software is available on your system. You may also want to run the IVP after a system failure to be sure that users can access MailWorks. To run the IVP after an installation, enter the following command: # setld -v DMWBASE170 If the IVP fails, examine the /var/opt/DMW/logs/ivplog file. It will contain information to help you diagnose the problem. 3.7 Setting up MailWorks to Work with a Remote MSR If the Message Store Registry (MSR) is running on a different system than the one where MailWorks is installed, perform the tasks in this section: o Copy the usr/opt/DMW/Keys file from the system running the MSR, and place it in usr/opt/DMW/Keys on the system where MailWorks is installed. o On the system where MailWorks is installed, prevent the X400 interconnect process from starting by renaming the file /var/opt/DMW/runx400g to a different name (for example, runx400g.sav). 3.8 Running MailWorks To restart MailWorks, do one of the following: o Shut down and reboot the system on which you installed MailWorks o Run the /usr/opt/DMW/bin/startMAILworks script from the root account to start the MailWorks processes immediately After Installing MailWorks 3-3 A ________________________________________________________________ Installing the Motif Client on a SunOS or Solaris System The MailWorks for UNIX kit contains the installation kits for the MailWorks Motif Client for SunOS[TM] and Motif Client for Solaris[R]. This appendix contains instructions for installing the kit and setting up the SunOS and Solaris Motif clients. A.1 Preparing to Install the SunOS or Solaris Kit The system requirements for installing and running the MailWorks Motif Client for SunOS or the MailWorks Motif Client for Solaris are: o Sun SPARCstation[TM] o Either of the following: - SunOS Version 4.1.3 or later - Solaris Version 2.4 or later o OpenWindows V3, patch level #100444-58 (included on kit) o 30 Mbytes of available disk space If you need to install the proper Openwindows patch level, the patch tape is included the MailWorks for UNIX kit in the file 100444-58.tar.Z. To install the patch, uncompress and restore the tar file, and follow the instructions in the README file. This will install patch level 3000-107 of the xnews server. To check the current xnews server patch level, do the following: strings $OPENWINHOME/bin/xnews | grep "Patch #" If the current patch level is 3000-107 or higher, you do not need to install the patch. Installing the Motif Client on a SunOS or Solaris System A-1 A.2 Installing the SunOS or Solaris Kit To install the MailWorks Motif Client for SunOS or MailWorks Motif Client for Solaris from the CDROM kit, follow these steps: 1. Log on as superuser (login name root) on the system where you are installing the MailWorks Motif Client for SunOS or MailWorks Motif Client for Solaris. 2. Make sure you are at the root (/) directory: # cd / 3. Insert the disk into the drive and determine the device name for the drive. 4. Mount the disk. For example, to mount the disk at the mount point /mnt: # mount -r -d /dev/device_name /mnt 5. Change directory to a convenient location. For example: # mkdir /usr/MAILworks_Suninstall # cd /usr/MAILworks_Suninstall 6. Restore the contents of the tar file: For the MailWorks Motif Client for SunOS kit: # tar xf /mnt/DMWSUNOS/filename For the MailWorks Motif Client for Solaris kit: # tar xf /mnt/DMWSOLARIS/filename 7. Execute the install script: # ./install 8. Answer the installation script questions. A.3 After Installing the SunOS or Solaris Kit After installing the MailWorks Motif Client for SunOS or MailWorks Motif Client for Solaris, you may need to perform one or both of the following tasks: o Edit the .forward file A-2 Installing the Motif Client on a SunOS or Solaris System o Enable the Sun or Solaris system to locate the MailWorks for UNIX server by editing the Keys file. The Keys file should contain the fully specified node name of the UNIX server (for example, mynode.zko.dec.com). A.3.1 Editing the .forward File The .forward file is a one-line text file that is added to your home directory during installation. The file contains the pathname of the inetgrecv mailer, which is invoked when the UNIX mail system has mail for the MailWorks user. Place the following line at the beginning of each user's $HOME/.forward file: "|/usr/bin/inetgrecv username" where username specifies the username of the user. Be sure to place quotes (" ") around the contents of your .forward file, and do not put any spaces between the | and /. For more information about .forward files, see the MailWorks for UNIX Workgroup/System Administration. A.3.2 Enabling the SunOS or Solaris System to Locate the MailWorks Server The information in this section is based on the following assumptions: o The message store server (mss) is set up on a UNIX system o Your user name and password on the Sun or Solaris system are the same as on the UNIX system The Motif user agent uses the following protocol to locate the MailWorks server: 1. It looks in the /var/kits/MAILworks/msrHost file for the name of the machine last talked to. If this file exists and has a name in it, the Motif user agent looks on that host for the MailWorks server. 2. If not, the Motif user agent uses the name in the /sharedDir/Keys file and broadcasts it. The Keys file contains validation keys used for configuration. Installing the Motif Client on a SunOS or Solaris System A-3 If the Keys file does not contain the name of your Mailworks for UNIX server, you must edit the file to place the server name in it. Usually, if both the SunOS or Solaris system and the MailWorks server are on the same LAN, you will not need to edit the Keys file. For more information about Keys files, see the MailWorks for UNIX Workgroup/System Administration. A.3.3 Starting MailWorks To start MailWorks, enter the following command from the shell: % mailworks You see the following two windows appear in sequence: o The "About MailWorks" dialog box, which contains information about the version and copyright of the MailWorks software. (This box disappears automatically after a few seconds.) o The MailWorks Browser window. See the MailWorks for UNIX Motif Client User's Guide for more information. A-4 Installing the Motif Client on a SunOS or Solaris System B ________________________________________________________________ Contents of the Software Distribution Kit This appendix explains the contents of the MailWorks software distribution. When you install the MailWorks software, files and directories are installed in sharedDir, sharedDir/installDir, and localDir. B.1 Contents of the Base Component Table B-1 lists the files that are installed in sharedDir. Table_B-1_Files_and_Directories_Installed_in_sharedDir____ Name__________________Purpose_____________________________ bin/ A directory containing all the MailWorks binaries except those for the command line interface. clbin/ A directory containing the MailWorks binaries for the command line interface. These are in their own directory so that users can add that directory to their $PATH environment variable. bitmaps/ A directory containing bitmaps used by MailWorks. (continued on next page) Contents of the Software Distribution Kit B-1 Table B-1 (Cont.) Files and Directories Installed in __________________sharedDir_______________________________ Name__________________Purpose_____________________________ Encl1.7/ A directory containing the database Enclosures/ file of enclosure configuration information (DB) and the scripts used by DB. The DB file contains definitions for attachment types and their corresponding viewers. install A Bourne Shell (v/bin/sh) script for installing the MailWorks software in the appropriate system directories. installDir/ A directory containing files to be installed in other directories. install.X488 Location of X.400 interconnect files. Keys A file containing the validation keys for the MailWorks configuration key. The installation default is to use the system hostname. nlslib/OM A directory containing the message catalogs, which provide the text in the MailWorks interface. MAILworksrc A file for configuring MailWorks, which includes parameters for chang- ing the installation directories. /usr/opt/DMW/bin Receiver component. /x488grecv /usr/opt/DMW/bin Transmitter component. /x488gsend /usr/opt/DMW Installation procedure. /install.X488_____________________________________________ Table B-2 lists the files in the sharedDir/installDir subdirectory. This directory contains some important files that are subsequently installed elsewhere in the file system. B-2 Contents of the Software Distribution Kit Table B-2 Files and Directories Installed in sharedDir __________/installDir_____________________________________ Name_____________Purpose__________________________________ chkkey/ A program that processes validation /configuration keys. man/ A directory containing man pages. Install them as you want. MAILworks A file containing X Window System[TM] resources for the mailworks user agent for either monochrome or color displays. The install script puts this file in /usr /lib/X11/app-defaults. scripts Location of scripts for users. sendmail/ A directory containing sample sendmail configuration files: gateway.cf and leaf.cf. templates Location of templates for users. tutorial.po A message store containing the MailWorks tutorial. If you reply yes to the prompt from the install script about installing the tutorial, this file is installed in the localDir directory. XKeysymDB A file containing X keyboard symbols _________________needed_for_Motif_1.1.____________________ Table B-3 lists the files and directories created in localDir, the default directory for local files. These are files that need to be on each machine where MailWorks runs. Table_B-3_Files_and_Directories_Installed_in_localDir_____ Name_____________Purpose__________________________________ DAXdatafile Default local directory for InfoBroker Server entries. (continued on next page) Contents of the Software Distribution Kit B-3 Table B-3 (Cont.) Files and Directories Installed in __________________localDir________________________________ Name_____________Purpose__________________________________ dndatafile A file containing information that maps local MailWorks user names and the X.500 directory name logs/ A directory for holding the MailWorks log files. Each binary generates a log file, such as msrlog, msslog, and so on. msrHost A file containing the name of the host on which the msr is running. msrAliasFile A file containing the global aliases and distribution lists stored by the message store registry. runmsr A lock file that indicates where the runmsr process should be run. runmss A lock file that indicates where the runmss process should be run. runx400g A lock file that indicates where the runx400g process should be run. sf/ A directory for holding queued messages. tmp/ A directory for holding temporary files. tutorial.po A message store containing the MailWorks _________________tutorial.________________________________ The installation script also: o Makes links from sharedDir/bin to /usr/bin, using the commands shown in Table B-4. o If /usr/lib/X11/XKeysymDB already exists, the script moves it to /usr/lib/X11/XKeysymDB.old and adds appropriate keysyms to the file. If the file does not exist, the script installs it. o Sets the owner of sharedDir/bin/lsfd and localDir/sf to be the group that owns /bin/mail or /usr/spool/mail. This is usually the mail group. B-4 Contents of the Software Distribution Kit The script installs localDir/sf so that it is writable by this group as well. If the install script sets the group inappropriately for your configuration, you can change the group (and permissions if needed) for sharedDir/bin/lsfd and localDir/sf to whatever is appropriate. Table_B-4_Linked_Commands_________________________________ Name________Purpose_______________________________________ inetgrecv The MailWorks internet mail gateway, which sends messages to and receives messages from MailWorks users and users of other UNIX mail programs. mschk Recovers and converts MailWorks message stores. msrset Lists and defines MailWorks message store aliases. mailworks Starts the user agent of the MailWorks electronic messaging system. poster Sends mail with the MailWorks electronic messaging system. xloadimage Loads images into an X11 window or onto the ____________root_window.__________________________________ Contents of the Software Distribution Kit B-5 C ________________________________________________________________ Removing a MailWorks Installation To remove a MailWorks installation, complete the following steps: ________________________Note ________________________ If you share your sharedDir with other users across a network, coordinate your actions so you do not disrupt current users. _____________________________________________________ 1. To deinstall the MailWorks subsets, you must deinstall the X.400 Interconnect and InfoBroker Server subsets before deinstalling the Base subset. For example, if all three subsets are currently installed, use the following command: # setld -d DMWBASE170 Deinstalling DMW results in the following: o /usr/opt/DMW/bin/stopMAILworks is executed, stopping all MailWorks and Interconnect processes. o X.400 address and API client name is removed from the MAILworksrc file. o /usr/lib/X11/app-defaults/MAILworks file is removed. o Tutorial message store file is removed. o MailWorks boot-time, start-stop symbolic links are removed (symbolic links for S91mailworks and K09mailworks in /sbin/rc3.d, /sbin/rc2.d, and /sbin /rc0.d are removed, and the file /sbin/mailworks is removed). o Symbolic links for mschk, msrset, mailworks, poster, and xloadimage from /usr/bin are removed. Removing a MailWorks Installation C-1 2. If you are sure there are no important files in any of the subdirectories (such as personal message stores), you can remove the localDir (/var/opt/DMW). 3. If you are sure there are no important files in any of the subdirectories, you can remove sharedDir (/usr/opt /DMW). C-2 Removing a MailWorks Installation D ________________________________________________________________ Failures During Product Use If an error occurs while MailWorks is in use and you believe the error is caused by a problem with the product, take one of the following actions: o If you have a Software Product Services Support Agreement, contact your Customer Support Center (CSC) by telephone or by using the electronic means provided with your support agreement (such as DSNlink). The CSC provides telephone support for high-level advisory and remedial assistance. When you initially contact the CSC, indicate the following: - The name and version number of the operating system you are using - The version number of MailWorks you are using - The hardware system you are using (such as a model number) - A brief description of the problem (on sentence if possible) - How critical the problem is o If you have a Self-Maintenance Software Agreement, you can submit a Software Performance Report (SPR). o If you do not have any type of software services support agreement and you purchased MailWorks within the past year, you can submit an SPR if you think the problem is caused by a software error. When you submit an SPR, take the following steps: 1. Describe as accurately as possible the circumstances and state of the system when the problem occurred. Include the description and version number for Failures During Product Use D-1 MailWorks. Demonstrate the problem with specific examples. 2. Reduce the problem to as small a size as possible. 3. Remember to include listings of any command files, INCLUDE files, or relevant data files, and so forth. 4. Report only one problem per SPR. This will facilitate a faster response. 5. Mail the SPR package to Digital. If the problem is related to the MailWorks documentation, you can do one of the following: o Report the problem to the CSC (if you have a Software Product Services Support Agreement and the problem is severe). o Fill out the Reader's Comments form (in the back of the document that contains the error) and send the form to Digital. Be sure to include the section and page number where the error occurred. D-2 Failures During Product Use ________________________________________________________________ Index A__________________________ D__________________________ API client name DEC C++ shareable library planning, 1-4 prerequisite, 1-3 Audience De-installing MailWorks, of manual, v C-1 B Digital UNIX ___________________________ prerequisite, 1-2 Backup Disk space, 1-3 performing before DMW-add scripts installation, 1-4 saving before installing, Bill of Materials 1-7 checking, 1-1 DMW-add scripts Braces updating after use in manual, vi installation, 3-2 Brackets use in manual, vi E__________________________ C Enclosures directory ___________________________ updating after Commands installation, 3-1 entering, vi Errors linked, B-4 during installation, 2-1 Components, 1-4 Configuring F__________________________ multiple MSRs, 2-9 Failures Conventions reporting, D-1 used in manual, vi Files Ctrl key installed in localDir, use in manual, vi B-3 installed in sharedDir, B-1 Index-1 Files (cont'd) Installing (cont'd) installed in sharedDir XKeysymDB, B-4 /installDir, B-2 XMR gateway, 2-7 list of, B-1 Internet domain names .forward file updating after editing after Solaris kit installation, 3-2 installation, A-3 editing after SunOS kit K__________________________ installation, A-3 Keys file editing after Solaris kit I__________________________ installation, A-3 InfoBroker Server editing after SunOS kit prerequisite, 1-2 installation, A-3 Installation Kit on Solaris, A-1 contents, B-1 on SunOS, A-1 overview, 2-1 L__________________________ removal, C-1 License stopping, 1-8 installing, 1-5 time required, 2-1 Linked commands, B-4 Installing localDir, B-3 command links, B-4 Local directory file search disk space required, 1-3 base errors during, 2-1 setting up, 1-5 hardware requirements, Login privileges, 1-1 1-1 installation procedure, M 2-2 to 2-9 ___________________________ kit contents, B-1 Mail transport agents localDir, 2-1, B-3 prerequisite, 1-3 multiple MSRs, 2-9 MailWorks on additional systems, components of, 1-4 2-9 de-installing, C-1 preparing, 1-1, 2-1 installing, 2-1 Product Authorization Key preparing to install, 1-1 (PAK), 1-5 removing prior version, sharedDir, 2-1, B-1 1-8 sharedDir/installDir, B-2 restarting after software requirements, installation, 3-3 1-2 using while reinstalling, time to install, 2-1 1-8 X.400 Interconnect, 2-8 working with remote MSR, X.400 Interconnect files, 3-3 B-1 Index-2 MAILworksrc file Post installation (cont'd) updating after restarting MailWorks, 3-3 installation, 3-1 running msrset, 3-2 Manual setting Internet domain audience, v name, 3-2 conventions, vi setting up remote MSR, related documentation, v 3-3 using the, v tasks, 3-1 Message Store Registry tutorial message store setting up remote, 3-3 location, 3-2 Motif client updating DMW-add scripts, installing on Solaris, 3-2 A-1, A-2 updating Enclosures installing on SunOS, A-1, directory, 3-1 A-2 updating Internet domain postinstallation of names, 3-2 Solaris kit, A-2 updating MAILworksrc postinstallation of SunOS file, 3-1 kit, A-2 Prerequisites prerequisites for DEC C++ Shareable Library installing on Solaris, , 1-3 A-1 Digital UNIX, 1-2 prerequisites for disk space, 1-3 installing on SunOS, hardware, 1-1 A-1 InfoBroker Server, 1-2 starting on Solaris mail transport agents, system, A-4 1-3 starting on SunOS system, software, 1-2 A-4 Problem reporting, D-1 MSR Product failures setting up remote, 3-3 reporting, D-1 msrset running after R__________________________ installation, 3-2 Related documentation, v updating Internet domain Release notes name, 3-2 location, 1-1 Removing an installation, P__________________________ C-1 PAK Removing prior MailWorks installing, 1-5 version, 1-8 Post installation Requirements alias for tutorial DEC C++ Shareable Library message store, 3-2 , 1-3 Index-3 Requirements (cont'd) Stopping the installation, Digital UNIX, 1-2 1-8 disk space, 1-3 Subsets hardware, 1-1 removing old version, 1-8 InfoBroker Server, 1-2 SunOS login privileges, 1-1 after installing Motif mail transport agents, client on, A-2 1-3 editing .forward file, software, 1-2 A-3 key editing Keys file, A-3 use in manual, vi installing Motif client on, A-1, A-2 S__________________________ prerequisites for Scripts installing Motif client saving DMW-add before on, A-1 installing, 1-7 starting Motif client on, sharedDir, B-1 A-4 sharedDir/installDir, B-2 SunOS client Software license locating MailWorks server installing, 1-5 , A-3 Software requirements System backup DEC C++ Shareable Library performing before , 1-3 installation, 1-4 Digital UNIX, 1-2 InfoBroker Server, 1-2 T__________________________ mail transport agents, Tutorial message store 1-3 providing alias after Solaris installation, 3-2 after installing Motif Typographic conventions, client on, A-2 vi editing .forward file, A-3 U__________________________ editing Keys file, A-3 UNIX installing Motif client prerequisite, 1-2 on, A-1, A-2 prerequisites for X installing Motif client ___________________________ on, A-1 X.400 starting Motif client on, installation preparation, A-4 1-4 Solaris client X.400 API client name, locating MailWorks server 1-5 , A-3 Index-4 X.400 Interconnect installation, 2-8 installed X.400 Interconnect files, B-1 X.500 database lookups defining search base, 1-5 XMR gateway installation, 2-7 Index-5