Software.com 5.1 InterMail Mx Installation Guide
Below you will find brief information for InterMail Mx 5.1. InterMail Mx 5.1 is a messaging system software for installing and running messaging infrastructure on a variable number of host machines. With InterMail Mx 5.1, you’ll be able to manage your mail servers, databases, and messaging capacity, ensuring smooth operation of email communication for your site.
Advertisement
Advertisement
I N S T A L L A T I O N G U I D E
Software Version 5.1
Document Version 1
Published March, 2000
Software.com, Inc.
www.software.com
525 Anacapa Street
Santa Barbara, CA 93101-1603
Tel: (805) 882-2470
Fax: (805) 882-2473
10 Maguire Road, Suite 400
Lexington, MA 02421-3130
Tel: (781) 274-7000
Fax: (781) 674-1080
The InterMail software is a copyrighted work of Software.com, Inc.
© 1993–2000 Software.com, Inc. All rights reserved.
InterMail includes software that is copyright © 1990, 1993, 1994, The Regents of the University of California. All rights reserved. This code is derived from software contributed to Berkeley by Mike Olson.
SmartHeap, portions copyright © 1991–1997, Compuware Corporation.
InterMail incorporates a derivative work of the SSL Plus: SSL 3.0 Integration Suite Toolkit, copyright © 1996, 1997,
Consensus Development Corporation. SSL Plus: SSL 3.0 Integration Suite is a trademark of Consensus Development
Corporation, which reserves all rights thereto.
Portions of the SSL Plus: SSL 3.0 Integration Suite Toolkit software are based on SSLRef™3.0, which is copyright
© 1996, Netscape Communications Corporation. SSLRef™ was developed by Netscape Communications Corporation and
Consensus Development Corporation.
The MD5 Message-Digest algorithm used in InterMail is a copyrighted work of RSA Data Security, Inc., copyright
© 1991–1992, RSA Data Security, Inc. All rights reserved.
InterMail incorporates a derivative work of the BSAFE cryptographic toolkit, copyright © 1992–1996, RSA Data Security,
Inc. All rights reserved.
BSAFE is a trademark of RSA Data Security, Inc.
The RSA Public Key Cryptosystem is protected by U.S. Patent #4,405,829.
The Regular Expression Routines used in InterMail are copyright © 1992–94, Henry Spencer. All rights reserved. This software is not subject to any license of the American Telephone and Telegraph Company or of the Regents of the University of California.
The InterMail LDAP code is derived from software that is copyright © 1992–1996 Regents of the University of Michigan.
All rights reserved. Redistribution and use in source and binary forms are permitted provided that this notice is preserved and that due credit is given to the University of Michigan at Ann Arbor. The name of the University may not be used to endorse or promote products derived from this software without specific prior written permission. This software is provided “as is” without express or implied warranty.
The InterMail Mx Installation Guide is a copyrighted work of Software.com, Inc.
© 1997–2000, Software.com, Inc. All rights reserved.
No part of this documentation may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying, recording, or information storage and retrieval systems, for any purpose other than personal use, without the express written permission of Software.com, Inc.
This copyrighted work contains trade secret information of Software.com, Inc. Use, transfer, disclosure, or copying without the express written permission of Software.com, Inc., is strictly forbidden. Information in this document is subject to change without notice and does not represent a commitment on the part of Software.com, Inc.
INTERMAIL, SOFTWARE.COM, and SOFTWARE.COM THE INTERNET INFRASTRUCTURE COMPANY are registered trademarks, and POST.OFFICE and WEBEDGE are trademarks, of Software.com, Inc. and are registered trademarks in various countries around the world.
OPENVIEW is a registered trademark of Hewlett-Packard Company.
WINDOWS NT is a registered trademark of Microsoft Corporation.
NETSCAPE is a registered trademark of Netscape Communications Corporation.
SQL*NET is a trademark and ORACLE is a registered trademark of Oracle Corporation.
EMANATE is a registered trademark of SNMP Research, Inc.
SUN is a registered trademark of Sun Microsystems, Inc.
VERITAS is a registered trademark of Veritas Software Corporation.
Other product, brand, and company names mentioned herein may be trademarks, registered trademarks, or service marks of their respective holders.
InterMail Mx Installation Guide, Version 5.1
Document number: MI-000310
Table of Contents
Determining the Installation Tasks for Each Database or Server................................10
Task 8: Configuring the SQLNet Parameter Files and Client.....................................23
Turning On SNMP After Installing InterMail .....................................................41
Insufficient Shared Memory or Semaphores .......................................................42
Need to Deallocate Shared Memory Segments ...................................................42
Confidential and Proprietary, © Software.com, Inc. 2000 iii
InterMail Mx Installation Guide
iv Confidential and Proprietary, © Software.com, Inc. 2000
Preface
Welcome to InterMail Mx!
The InterMail Mx Installation Guide contains information about installing InterMail
Mx 5.1.
Intended Audience
This guide assumes that you are experienced with the UNIX operating system at a system administration level, and that you have an understanding of databases as well as of networking protocols and related technology.
Organization
This manual is organized as follows:
•
Chapter 1, Preparing for the Installation, provides an overview of the preparations you need to make before you can install InterMail Mx.
•
Chapter 2, Installing InterMail Mx, contains step-by-step procedures for installing InterMail Mx.
•
Chapter 3, Post-Installation Tasks, discusses some of the tasks you will need to perform after InterMail Mx has been installed.
Confidential and Proprietary, © Software.com, Inc. 2000 v
InterMail Mx Installation Guide
Conventions
Convention
$
at the start of a string
Description
An environment variable (set at the time of installation) monospace type
• Commands
• Directory and file names
• Hostnames
• Configuration keys and their values
• Utility names
<angle brackets>
in a command
A required variable
[square brackets]
in a command
An optional parameter
|
(a vertical bar) between options in a command
Exclusive options, of which you can use only one
Example
$spoolDir imdbcontrol cron
utility
Set this key to
command true
.
imboxget <address> imctrl [-verbose] impwdhash -a [md5-po|unix]
{braces}
around options in a command
A list of options, one of which is required immsgdelete {<msgID>...|-all}
...
(an ellipsis) after an optional entry in a command
An option for which you may have multiple entries imbucketscreate [<c1...cn>]
boldface
in an example User input venus% imservctrl stop
Related Documentation
This manual is one of a set. Other manuals in this set are:
•
InterMail Mx Reference Guide, which contains background information about the
InterMail servers and databases, configuration keys, management utilities, administrative utilities, APIs, and event messages.
•
InterMail Mx Operations Guide, which provides instructions for the operation and administration of the InterMail system.
•
Integrated Services Directory User Guide, which contains conceptual information about the Integrated Services Directory (ISD) architecture, configuration keys, directory schema, directory structure, and directory management utilities, as well as procedural information to help you customize the
ISD.
vi Confidential and Proprietary, © Software.com, Inc. 2000
Preface
•
InterMail Mx Upgrade Guide, which provides instructions for upgrading from previous versions of the InterMail product.
•
InterMail Mx Migration Guide, which provides instructions for migrating to
InterMail from the Post.Office, Sendmail, and Netscape messaging products.
Questions and Comments
Your feedback is important to us! To suggest improvements or make comments on the content of this manual, please send e-mail to [email protected].
Confidential and Proprietary, © Software.com, Inc. 2000 vii
InterMail Mx Installation Guide viii Confidential and Proprietary, © Software.com, Inc. 2000
1
Preparing for the Installation
This chapter discusses the preparations you need to make before you install the
InterMail Mx product.
You typically install InterMail Mx in partnership with an installation specialist (or team of specialists) from your InterMail vendor. In addition, you typically worked with an InterMail architect before receiving the product to assess the needs of your site and to define a detailed, customized architecture for your InterMail system. This chapter discusses some of the tasks you will perform with your InterMail installation specialist to prepare for installing your system.
For information on the overall workings of an InterMail system and for details on the individual components and utilities, see the InterMail Mx Reference Guide, the
InterMail Mx Operations Guide, and the Integrated Services Directory User Guide.
If you are migrating an existing messaging system to InterMail, see also the InterMail
Mx Migration Guide.
This chapter contains information on the following topics:
•
•
Prerequisites
Before you perform the tasks described in this chapter, you should have completed the following prerequisites:
•
Site assessment
Before installing the InterMail software, you are likely to have worked with an
InterMail architect (or architecture team) to assess your business overview, direction, and strategy, and the services required to meet your goals.
Confidential and Proprietary, © Software.com, Inc. 2000 1
2
InterMail Mx Installation Guide
•
Baseline InterMail architecture specification
A baseline InterMail architecture specification provides a detailed technical plan of the InterMail system to be deployed at your site, including such information as the number of host machines, the hardware and software required for the hosts, the InterMail configuration (for example, which servers and databases reside on which hosts), the messaging capacity, the storage requirements, the reliability features, the security features, and so forth.
Pre-Installation Tasks
This section discusses tasks you should perform before you install the InterMail software. The information in this section is not exhaustive, but it provides directions and suggestions to help you prepare for a smooth installation and for smooth operation of your InterMail system once it is running. You should work with your InterMail installation specialist to define the exact list of tasks that are appropriate for your site.
The tasks discussed in this section are organized into the following categories:
•
•
•
Preparing the Hardware and Software
•
•
Preparing for Software Development
•
Preparing for Customer Support
You should define the experts as soon as possible, but you can perform the other tasks in any order (and you will probably perform some of them in parallel).
Identifying Experts
To ensure smooth installation and operation of your InterMail system you should identify individuals at your site who are experts in, or can become experts in, particular technologies. A single individual may be responsible for one or more of these roles. You will need the following experts:
•
System administrator
This person understands the hardware platforms and the operating system to be used in the InterMail system.
•
Network administrator
This person knows your network resources and how to configure, maintain, and expand them.
Confidential and Proprietary, © Software.com, Inc. 2000
Preparing for the Installation
•
Backup administrator
This person is responsible for the backup software and ensuring that backup and recovery operations are performed successfully. This role may belong to the system administrator, or it may be handled by a separate person or group.
•
Messaging expert
This person understands the messaging needs of your business and understands your current messaging system (if one exists).
•
Marketing expert
This person is responsible for packaging your message products for your customers and has information that affects the configuration settings for
InterMail.
•
InterMail expert
This person understands the InterMail system, including all the components and how they interact, how messages flow through the system, and how to use
InterMail utilities.
•
Oracle database administrator (DBA)
This person is fluent in database technology and is experienced with Oracle in particular.
You will also need to identify additional personnel, such as operations staff and possibly software developers. These personnel are discussed later in this chapter.
Preparing the Site
To prepare your site to host the InterMail messaging infrastructure, ensure that the physical needs such as power, floor space, and connectivity, are met.
Preparing the Hardware and Software
To prepare your hardware and software for the InterMail installation, you will need to perform tasks such as the following:
•
Install the hardware.
Locate all the hardware, including host machines, storage devices, hubs, switches, cables, and connectors. Install the hardware, and ensure that the hardware has the correct firmware revisions.
•
Set up disk storage.
You may install and configure your storage devices, or this may be the responsibility of your storage vendor.
Confidential and Proprietary, © Software.com, Inc. 2000 3
4
InterMail Mx Installation Guide
•
Install the operating system software.
Identify the version of the operating system required for this version of InterMail, plus any required patches. Install the operating system on the host machines.
To identify the appropriate operating system version and patch level required for
InterMail, see the InterMail Mx Release Notes.
•
Ensure correct kernel parameter settings.
You will work with your InterMail installation specialist to determine the correct kernel parameter settings for your hosts.
For example, you probably need to increase the maximum shared memory segment and semaphore size before you install an Oracle database on an
InterMail host. An insufficient amount of shared memory or semaphores is the most common reason that an Oracle installation fails.
The Deployment Worksheet estimates the size of the shared memory segment that
Oracle will need. (You likely completed this Excel spreadsheet when you planned your InterMail architecture, and you will review the worksheet values just before you begin your InterMail installation.) Oracle calls the shared memory segment for a database the System Global Area (SGA). Since the worksheet can only estimate the size of the SGA, you should set the
SHMMAX
parameter generously above the size estimated by the worksheet.
There are three kernel parameters related to semaphores:
–
The kernel parameter
SEMMSL
dictates the maximum semaphore set size; set this parameter to at least 100.
–
The parameter
SEMMNI
dictates the maximum number of sets available; set this parameter to 70.
–
The parameter
SEMMNS
dictates the maximum number of semaphores available; set this parameter to a value that is significantly above 100 to ensure that Oracle and other processes do not encounter a semaphore shortage. A value of 400 is recommended.
For more information, see the “Tuning the SGA” tab of the Deployment
Worksheet.
To make these changes, do the following:
–
On Solaris systems, set the parameters in
/etc/system
.
–
On HP-UX systems, use the
/usr/sbin/sadm
GUI administration tool.
•
Install prerequisite software.
Install any supporting software, such as a journaling file system, volume manager, platform-specific high-availability software, and so forth. You do not need to install Oracle at this time; you will install it later as part of the InterMail installation.
Confidential and Proprietary, © Software.com, Inc. 2000
Preparing for the Installation
•
Prepare the network configuration.
To prepare your network, you should perform tasks such as the following:
–
Define the hostnames for all of the network interface ports for each machine, plus any aliases.
–
Identify how many IP addresses you need, and obtain those addresses.
–
Define the DNS names for your machines.
–
Assess where firewalls are needed.
–
Define load-balancing requirements.
–
Define and implement a procedure to ensure that the system time will be synchronized across the hosts in the InterMail configuration.
To ease disk space requirements, provide faster software copying, and allow parallel installation operations, you can establish one machine as a private NFS server for the InterMail installation software.
•
Define and create the required administrative accounts.
Create the UNIX accounts you will need on each machine, such as a privileged management account, a non-privileged maintenance account, a system/network operations account, and so forth.
•
Locate the InterMail software.
With your InterMail installation specialist, identify the version of InterMail that you will be installing and locate the software (on CD-ROM or on an FTP site, for example).
•
Procure hardware for load generation.
Most sites test the InterMail installation before going into production mode. For this testing you need hardware to generate a messaging load that approximates the inbound e-mail and messaging retrieval traffic seen during peak usage hours.
•
Set up a test lab.
Most sites set up a lab for testing post-production regression, product functionality, and third-party integration. It may be appropriate to set up your
InterMail test lab and staging area on the software developers’ private local area network (LAN), where it can be assigned its own test domain and Internet connectivity.
Preparing for Operations
To prepare your operations staff for the InterMail installation and deployment, you should perform tasks such as the following:
Confidential and Proprietary, © Software.com, Inc. 2000 5
6
InterMail Mx Installation Guide
•
Identify staff.
Identify people on the operations staff to learn the InterMail system and assume responsibility for InterMail operations tasks. Identify the appropriate training courses and documentation required.
•
Define monitoring and reporting procedures.
Define the monitoring that will occur on the InterMail system and the reports that will be generated. Define policies for identifying issues detected by monitoring and define policies for handling reports.
For information on InterMail monitoring tasks and tools, see the InterMail Mx
Operations Guide.
•
Define backup and recovery procedures.
Define procedures for backing up InterMail data and define procedures for recovering lost data. For further information, see the InterMail Mx Operations
Guide.
•
Define procedures for managing service attacks.
Define the policies and procedures for dealing with various attacks on your messaging system. You should address relay rules, spam filtering rules, and so forth. For information on mail filtering, connection dropping, and related topics, see the InterMail Mx Operations Guide.
•
Define security requirements and procedures.
Address security concerns in such areas as:
–
Installation: Remove non-essential servers and services from hosts that are connected to the Internet.
–
Access: Define who can access the consoles through the administrative network, through phone lines, and so forth.
–
Private namespace: Use non-routable IP addresses for internal hosts.
For more information about security planning, see the InterMail Mx Operations
Guide.
•
Define access requirements for customer service representatives.
The customer service representatives at your site might need connectivity to the
InterMail system, access to the log files, and so forth.
•
Define failover procedures (if applicable).
If your site is implementing failover features, define the policies and procedures for handling failover situations.
Confidential and Proprietary, © Software.com, Inc. 2000
Preparing for the Installation
•
Define disaster recovery procedures.
Define procedures for recovering from disasters such as power failure, hardware failure, operator error, earthquake, flood, and so forth. Also determine the priority that is assigned to the messaging service in your site’s overall disaster-recovery plan.
•
Define change control procedures.
Define procedures for making changes to the production software.
Preparing for Software Development
Depending on your InterMail configuration, you may need software development resources. For example, if you have a custom billing system, a custom provisioning system, and custom Web pages for customer service, you may want to integrate such systems with InterMail using the InterMail APIs or command-line scripts.
Depending on your site requirements, you may need to do the following to prepare for software development:
•
Identify software development resources.
Determine your needs for custom software development, and identify and train the necessary software development personnel.
•
Establish network connectivity.
You may need to establish connectivity between your software developers’ private local-area network and the InterMail system.
Preparing for Customer Support
To preparate for customer support:
•
Prepare your customer support organization.
Make sure that you have personnel in your customer support organization who are prepared to support your messaging customers. Identify the appropriate training courses and documentation required.
In addition, define problem reporting and resolution procedures, including escalation procedures.
•
Establish contact with your InterMail vendor’s support organization.
Discuss the support procedures with your InterMail vendor. For example, your
InterMail vendor might identify a customer support contact person from their company who is assigned specifically to your site. You might initiate additional steps at this point, such as establishing dial-in access to your InterMail system for the vendor’s support contact.
In addition, define problem reporting and resolution procedures, including escalation procedures.
Confidential and Proprietary, © Software.com, Inc. 2000 7
InterMail Mx Installation Guide
8 Confidential and Proprietary, © Software.com, Inc. 2000
2
Installing InterMail Mx
Before you begin the installation, you should:
•
Read and understand the information in this chapter.
•
Identify which InterMail servers will run on which host machines.
•
Complete the installation preparation tasks listed in Chapter 1.
This chapter describes how to install the InterMail Mx 5.1 messaging system. It contains the following sections:
•
•
•
Completing the Deployment Worksheet
•
•
Installation Overview
The InterMail system can be installed on a variable number of host machines (hosts).
You can install more than one component on the same host, and you can install more than one copy of some components, each on different hosts.
This section describes the order in which you must install components on hosts and describes the installation tasks themselves.
Order of Installation
Each InterMail installation is unique, and your particular circumstances will govern how and when you install InterMail on each host. However, you must perform the following operations, in the order specified:
Confidential and Proprietary, © Software.com, Inc. 2000 9
InterMail Mx Installation Guide
1. Complete the Deployment Worksheet.
See “Completing the Deployment Worksheet” on page 13.
2. Create the Integrated Services Directory (ISD) database.
This step creates an empty database, ready for data. For the specific tasks
required, see Table 1 on page 10.
3. Create one or more Message Store databases.
This step creates one or more empty databases, ready for data. For the specific
tasks required, see Table 1 on page 10.
4. Install the Configuration server, and any other components that will run on that host.
If the host that runs the Configuration server also runs other InterMail servers, install those servers on the host as well. For the specific tasks required for each
server, see Table 1 on page 10.
5. Install the Directory server, and any other components that will run on that host.
You are not required to install the Directory server right after the Configuration server, but it is suggested. If the Configuration server and the Directory server are on the same host, you will install them at the same time. The installation of the
Directory server populates the ISD database.
If the host that runs the Directory server also runs other InterMail servers, install those servers on the host as well. For the specific tasks required to install each
server, see Table 1 on page 10.
6. Install the other servers.
You can install the remaining servers on the remaining hosts in any order. For the
specific tasks for each server, see Table 1 on page 10.
The following sections provide details about what is required to perform each of the above steps.
Determining the Installation Tasks for Each Database or
Server
To install a given database or server, complete the tasks shown in Table 1. The
numbered tasks are defined after the table.
Table 1: Installation tasks for databases and servers
Component
ISD database
Tasks
1 2 3 4 6 8
1 3 7 8 Message Store database
Configuration server 2 4 5 9
10 Confidential and Proprietary, © Software.com, Inc. 2000
Installing InterMail Mx
Table 1: Installation tasks for databases and servers (continued)
Component Tasks
Directory server 2 4 5
Directory Cache server
SNMP server
2
2
4
4
5
5
Queue server
Message Transport Agent (MTA)
POP server
IMAP server
Message Store Server (MSS)
WebEdge server
1
2
2
2
2
2
2
3
4
4
4
4
4
4
5
5
5
5
5
5
8
8
9
8 9
9
9
9
9
9
9
9
10
10
10
10
10
10
The Manager server is not listed in the above table because it is required on all hosts and is installed automatically by the InterCore installation.
If you install more than one server on a host, perform the union of the tasks required for the servers. Do not perform a task more than once on a given host. For example, to install a Message Store database and an MSS on the same host, complete tasks 1, 2, 3,
4, 5, 7, 8, 9, and 10 on that host.
Each task is described in detail in its own section later in this chapter. The tasks are:
•
“Task 1: Creating an Oracle User and Group” on page 13
•
“Task 2: Creating an InterMail User and Group” on page 14
•
“Task 3: Creating the Oracle User’s Directory” on page 15
•
“Task 4: Creating the InterMail User’s Directory” on page 15
•
“Task 5: Checking Port Assignments” on page 15
•
“Task 6: Installing the ISD Database” on page 16
•
“Task 7: Installing the Message Store Database” on page 19
•
“Task 8: Configuring the SQLNet Parameter Files and Client” on page 23
•
“Task 9: Installing InterCore” on page 25
•
“Task 10: Installing InterMail” on page 34
Confidential and Proprietary, © Software.com, Inc. 2000 11
InterMail Mx Installation Guide
Note:
This guide uses imail
and oracle
for the names of the InterMail and Oracle users. You should use these default usernames and groups unless any of the following is the case:
• You have predefined site standards that require other names.
• InterMail will be used in conjunction with servers that share resources with other applications.
• You already have Oracle installed with a different user and group specification.
For a multi-host installation, you might want to modify the above installation scenario slightly by installing InterCore on all the hosts before installing InterMail on any of the hosts. This allows you to do the following before continuing with the rest of the
InterMail installation:
•
Test the connectivity of the networking hardware
•
Identify any permission problems
•
Test the connectivity of the InterMail Configuration server, Manager servers,
Directory server, and Directory Cache servers
General Installation Tips
This section contains general hints and tips for doing an InterMail Mx 5.1 installation.
•
Installation log files
If an error occurs during installation, look at the log information recorded in the following file (where
<task-name>
refers to the installation task or subcommand):
<install-directory>/tmp/<task-name>.out
The log file name will be something like imconfget.out
or checkOraclePermissions.out
. The installation typically deletes the log files if there are no errors.
•
Scrolling windows
Execute installation commands from within a terminal window that has scroll bars and scrolling buffers that are at least 5 or 6 times the length of the window.
You will also need other windows available besides the window in which you are executing the installation tasks.
•
Defaults
The installation scripts attempt to determine values for installation options and questions by looking in files such as configuration files. You typically have the option of changing the values if they are inappropriate for your installation.
12 Confidential and Proprietary, © Software.com, Inc. 2000
Installing InterMail Mx
•
Installation output
Capture the output of each installation task and store the output in a nonvolatile directory such as
/var/tmp
. Use script
or another appropriate tool to capture the output.
Completing the Deployment Worksheet
The InterMail Deployment Worksheet, deploymentworksheet.xls
, is an Excel spreadsheet consisting of a number of separate worksheets. This spreadsheet helps you determine the sizing requirements for the Oracle databases used in InterMail.
Copy the Deployment Worksheet from the Oracle directory on the InterMail product
CD-ROM.
Enter the required information in all the worksheets, including the last one, which generates the imoraparams.txt
text file that the InterMail installation procedure uses. Copy this file to each host where you will install an InterMail Oracle database
(the ISD database or a Message Store database). Also copy this file to each host that does not have a database but that will run the Directory server, a Directory Cache server, or an MSS.
The worksheet contains instructions on how to use it, including comment text for certain cells. Cells that have comment text are indicated by a red triangle in the upper right corner.
Performing Installation Tasks
This section describes how to perform each of the installation tasks. See “Order of
Installation” on page 9 for information on the order in which to perform these tasks.
Note:
These processes assume that you are using a local password-file system. This document does not cover creating a new user and home directory using
Network Information Service (NIS).
Task 1: Creating an Oracle User and Group
Before you begin, please note the following:
•
Any NIS entries you are creating must match exactly those of the local passwordfile system entries. If they do not, InterMail will not function properly.
•
The Oracle user and group names must not exist in any other groups.
•
The Oracle user and group names must be the same on every host running
InterMail.
•
If you choose an Oracle group name other than dba
, you need to relink Oracle using the Oracle installer ( orainst
).
Confidential and Proprietary, © Software.com, Inc. 2000 13
InterMail Mx Installation Guide
•
Neither the imail
nor the oracle
user should possess superuser/root privileges, as this may introduce unnecessary security risks.
To create the Oracle user and group (from an administrative account):
1. Create the new Oracle group
.
For example, use the following command: groupadd -g 101 dba
The resulting group entry in
/etc/group
will look something like this: dba::101:
2. Create the new Oracle user
.
For example, use the following command: useradd -u 1000 -g dba -d /home/oracle -s /bin/csh oracle
The resulting user entry in
/etc/passwd
will look something like this: oracle:x:1000:101:Oracle Account:/home/oracle:/bin/csh
When you create the Oracle password file entry, the default group ID for the
Oracle user should match the ID for the dba
group.
Task 2: Creating an InterMail User and Group
Before you begin, please note the following:
•
Any NIS entries you are creating must match exactly those of the local passwordfile system entries. If they do not, InterMail will not function properly.
•
The InterMail user and group names must not exist in any other groups.
•
The InterMail user and group names must be the same on every host running
InterMail.
•
Neither the imail
nor the oracle
user should possess superuser/root privileges, as this may introduce unnecessary security risks.
To create the InterMail user and group (from an administrative account):
1. Create the new InterMail group
.
For example, use the following command: groupadd -g 250 imail
The resulting group entry in
/etc/group
will look something like this: imail::250:
2. Create the new InterMail user
.
For example, use the following command: useradd -u 30000 -g imail -G dba -d/home/imail -s /bin/csh imail
The resulting user entry in
/etc/passwd
will look something like this: imail:x:30000:250:InterMail common user:/home/imail:/bin/csh
3. Add the new InterMail user to the Oracle group in
/etc/group
. The resulting user entry in
/etc/group
will look something like this: dba:101:imail
14 Confidential and Proprietary, © Software.com, Inc. 2000
Installing InterMail Mx
Task 3: Creating the Oracle User’s Directory
To create the Oracle user’s directory:
1. Set user to root: su
2. Create a new Oracle home directory and set the correct permissions and ownerships: mkdir -p /<OracleHome> chmod 775 /<OracleHome> chown <OracleUser> /<OracleHome> chgrp <OracleGroup> /<OracleHome>
For example: mkdir -p /home/oracle chmod 775 /home/oracle chown oracle /home/oracle chgrp dba /home/oracle
Task 4: Creating the InterMail User’s Directory
To create the InterMail user’s directory:
1. Set user to root: su
2. Create a new InterMail home directory, and set the correct permissions and ownerships: mkdir -p /<InterMailHome> chmod 775 /<InterMailHome> chown <ImailUser> /<InterMailHome> chgrp <ImailUser> /<InterMailHome>
For example: mkdir -p /home/imail chmod 775 /home/imail chown imail /home/imail chgrp imail /home/imail
Task 5: Checking Port Assignments
The InterMail installation procedure configures servers using numerous port numbers.
Some ports are standard and not subject to modification. Some, such as the SMTP,
POP, and IMAP ports, are well-known ports that are defined in RFC specifications and should not be changed. Other servers in InterMail do not use well-known ports.
The defaults for these ports have been specifically chosen to avoid conflict with port numbers used for common UNIX applications (such as X servers).
Although precautions have been taken to eliminate port conflicts, you should check
/etc/services
for system port assignments, then review any third-party applications running on the hosts on which InterMail will be installed to ensure that
Confidential and Proprietary, © Software.com, Inc. 2000 15
InterMail Mx Installation Guide
there are no conflicts. By default, the InterMail installation starts selecting ports at port 5000 and uses up to 20 ports on a host that is running all the servers.
SSL
If you choose to use the InterMail Secure Socket Layer (SSL) server authentication for the POP and MTA servers, the installation script will prompt you for additional port numbers for the SSL POP and SSL MTA servers. These are well-known ports, so you you should accept the port numbers as assigned by the script.
Failover Groups
If a host is identified as a member of a failover group, InterMail requires that all servers installed on the hosts in the failover group have unique port numbers. If you assign the hosts to the failover group correctly, InterMail ensures that the port numbers are unique within the failover group. Unique port numbers enable any server to fail over and run on any other machine in the failover group with no port conflicts.
Task 6: Installing the ISD Database
This task uses the imorainstall
script to install the Oracle database software and the InterMail Directory schema.
To install the ISD database:
1. Change to the Oracle user: su - oracle
2. Create a log to record this installation: script <LogName>
3. Set your directory to the location of the Oracle installation files. It is important to run the imorainstall
that shipped with this version of InterMail.
4. Do not uncompress or untar the Oracle installation files; imorainstall
will do it.
5. Define the environment variables used by the Deployment Worksheet, such as
ORA_SYSTEM
, if you are using the Deployment Worksheet. For example: source setupEnvVar
The setupEnvVar
file is a template file that is provided with InterMail in the oracle
directory. You can customize and run this file if you are using csh
.
imorainstall
and respond to the following prompts:
ISD Database Installation Prompt
Select a menu item (1 to 11): [11]
Response
2
to install a new Directory database
16 Confidential and Proprietary, © Software.com, Inc. 2000
Installing InterMail Mx
ISD Database Installation Prompt
...
Pausing... [Hit enter to continue]
...
Enter “Install Source” directory:
[<path>]
Please verify the installation configuration...
-------------------------------
...
Do you accept these settings? (Yes/No/
Quit) [Yes]
There are two ways to proceed.
...
Install using values saved from the
Deployment Worksheet? (Y/N) [yes]
Response
Read the accompanying text and then press
Return.
This prompt appears a number of times during this script.
The path of imorainstall
and the Oracle installation tar files
If you changed to this directory before running imorainstall
, as directed above, the correct path should be displayed in square brackets and you can just press Return.
• yes
if the settings are correct
• no
to change settings
• quit
to stop the installation procedure
For more information on these settings, see
“Oracle Installation Configuration Settings” on page 38.
Y
Choosing
N
installs a preconfigured ISD database that is not suitable for most production environments.
The "Output to Install" sheet in the
Deployment Worksheet is used to create a file containing data for input to the
InterMail Oracle installation.
Please enter the name of this file
[<path>/imoraparams.txt]
The location of the imoraparams.tx
t file generated by the Deployment Worksheet
...
Relink Oracle now? (Y/N) [yes]
Y
Do not answer
N
unless you are certain that
Oracle does not require relinking.
...
Checking for missing directories in any user-specified pathnames...
The directory <path> does not exist.
Create <path>? (Yes/No/Quit) [Yes]
Y
This message does not always appear. If you see this message, respond
Yes
.
Confidential and Proprietary, © Software.com, Inc. 2000 17
InterMail Mx Installation Guide
ISD Database Installation Prompt
...
Creating InterMail database; this will take a significant amount of time...
...
InterMail database creation completed.
Response
You will see a number of messages. Read the accompanying text and press Return when instructed.
Verifying schema objects...
...
Finished preparing database for hot backups.
Pausing... [Hit enter to continue]
Would you like a schema report generated? (Yes/No/Quit) [Yes]
Enter file name for report [<path>]
...
Select a menu item (1 - 11) [11]
Y
A name and location for the report file
11
to quit
If this prompt displays without preceding errors, the first part of the ISD database installation has been completed successfully.
7. Change to the Oracle home directory. For example: cd /home/oracle source .cshrc
9. Change to the Oracle
/orainst
directory. For example: cd /service/oracle/8.0.5/orainst
10. Set user to root: su
11. Set the values for the
ORACLE_HOME
and
ORACLE_SID
variables.
–
For example, in the sh
shell:
ORACLE_HOME=/service/oracle/8.0.5
ORACLE_SID=IMD510
–
For example, in the csh
shell: setenv ORACLE_HOME /service/oracle/8.0.5
setenv ORACLE_SID IMD510
18 Confidential and Proprietary, © Software.com, Inc. 2000
Installing InterMail Mx
12. Run the root.sh
script.
–
For example, in the sh
shell:
PATH=$PATH:{ORACLE_HOME}/bin export ORACLE_HOME ORACLE_SID PATH
$(ORACLE_HOME}/orainst/root.sh
–
For example, in the csh
shell:
./root.sh
13. Respond to the following prompts:
ISD Database Installation Prompt
Running Oracle8 root.sh script...
Response
•
Y
if the settings are correct
•
N
to change settings
The following environment variables are set as:
ORACLE_OWNER= oracle
ORACLE_HOME= <path>
ORACLE_SID= <SID-value>
Are these settings correct (Y/N)? [Y]:
Enter the full pathname of the local bin directory [<path>]:
The path for the Oracle bin
directory. For example:
/service/oracle/8.0.5/bin
Checking for “oracle” user id...
ORACLE_HOME does not match the home directory for oracle.
Okay to continue? [N]:
Y
This does not affect the installation. Type
Y and press Return.
Please raise the ORACLE owner’s ulimit as per the IUG.
You can ignore this message.
Leaving common section of Oracle8 root.sh.
This message indicates that the ISD directory installation has been completed.
14. Enter exit
twice, once to leave superuser and once to finish the logging script.
The installation procedure generates SQL scripts that are used to create the database.
You should keep these SQL scripts for future reference.
Task 7: Installing the Message Store Database
To install a Message Store database:
1. Change to the Oracle user: su - oracle
Confidential and Proprietary, © Software.com, Inc. 2000 19
InterMail Mx Installation Guide
2. Create a log to record this installation: script <LogName>
3. Set your directory to the location of the Oracle installation files. It is important to run the imorainstall
that shipped with this version of InterMail.
4. Do not uncompress or untar the Oracle installation files; imorainstall
will do it.
5. Define the environment variables used by the Deployment Worksheet, such as
ORA_SYSTEM
, if you are using the Deployment Worksheet. For example: source setupEnvVar
The setupEnvVar
file is a template file that is provided with InterMail in the oracle
directory. You can customize and run this file if you are using csh
.
If you installed the ISD database on this same host, you may not need to repeat this step.
imorainstall
and respond to the following prompts:
Message Store Database Installation Prompt Response
Select a menu item (1 to 11): [11]
1
to install a new Message Store database
...
Pausing... [Hit enter to continue]
Read the accompanying text and then press
Return.
This prompt appears a number of times during this script.
...
Enter “Install Source” directory:
[<path>]
Please verify the installation configuration...
--------------------------------
...
Do you accept these settings? (Yes/No/
Quit) [yes]
There are two ways to proceed.
...
Install using values saved from the
Deployment Worksheet? (Y/N) [yes]
The path of imorainstall
and the Oracle installation tar files
If you changed to this directory before running imorainstall
, as directed above, the correct path should be displayed in square brackets and you can just press Return.
• yes
if the settings are correct
• no
to change settings
• quit
to stop the installation process
For more information on these settings, see
“Oracle Installation Configuration Settings” on page 38.
Y
Choosing
N
installs a preconfigured Message
Store database that is not suitable for most production environments.
20 Confidential and Proprietary, © Software.com, Inc. 2000
Installing InterMail Mx
Message Store Database Installation Prompt Response
The "Output to Install" sheet in the
Deployment Worksheet is used to create a file containing data for input to the
InterMail Oracle installation.
Please enter the name of this file
[<path>/imoraparams.txt]
The path of the imoraparams.txt
file
Oracle has already been installed, reinstall Oracle files?
You will see this prompt if Oracle is already installed on this host because, for example, the
ISD database resides on this host. In that case, answer
No
.
...
Relink Oracle now? (Y/N) [yes]
Y
Do not answer
N
unless you are certain that
Oracle does not require relinking.
...
Checking for missing directories in any user-specified pathnames...
The directory <path> does not exist.
Create <path>? (Yes/No/Quit) [Yes]
Y
This message does not always appear. If you see this message, respond
Yes
.
...
Creating InterMail database; this will take a significant amount of time...
Running Oracle scripts to create system views for IMM510_1...
...
InterMail database creation completed.
You will see a number of messages. Read the accompanying text and press Return when instructed.
Verifying schema objects...
...
Finished preparing database for hot backups.
Pausing... [Hit enter to continue]
Would you like a schema report generated? (Yes/No/Quit) [yes]
Enter file name for report [<path>]
...
Select a menu item (1 - 11) [11]
Y
A name and location for the report file
11
to quit
If this prompt displays without preceding errors, the first part of the Message Store database installation has been completed successfully.
Confidential and Proprietary, © Software.com, Inc. 2000 21
InterMail Mx Installation Guide
7. Change to the Oracle home directory. For example: cd /home/oracle source .cshrc
9. Change to the Oracle / orainst
directory. For example: cd /service/oracle/8.0.5/orainst
10. Set user to root: su
11. Set the values for the
ORACLE_HOME
and
ORACLE_SID
variables.
–
For example, in the sh
shell:
ORACLE_HOME=/service/oracle/8.0.5
ORACLE_SID=IMD510
–
For example, in the csh
shell: setenv ORACLE_HOME /service/oracle/8.0.5
setenv ORACLE_SID IMM510_1
12. Run the root.sh
script.
–
For example, in the sh
shell:
PATH=$PATH:{ORACLE_HOME}/bin export ORACLE_HOME ORACLE_SID PATH
$(ORACLE_HOME}/orainst/root.sh
–
For example, in the csh
shell:
./root.sh
13. Respond to the following prompts:
Message Store Database Installation Prompt Response
Running Oracle8 root.sh script...
•
Y
if the settings are correct
•
N
to change settings
The following environment variables are set as:
ORACLE_OWNER= oracle
ORACLE_HOME= <path>
ORACLE_SID= <SID-value>
Are these settings correct (Y/N)? [Y]:
Enter the full pathname of the local bin directory.
The path for the Oracle bin
directory. For example:
/service/oracle/8.0.5/bin
22 Confidential and Proprietary, © Software.com, Inc. 2000
Installing InterMail Mx
Message Store Database Installation Prompt Response
Checking for “oracle” user id...
ORACLE_HOME does not match the home directory for oracle.
Okay to continue? [N]:
Y
This does not affect the installation.
Please raise the ORACLE owner’s ulimit as per the IUG.
You can ignore this message.
Leaving common section of Oracle8 root.sh.
This message indicates that the Message Store database installation has been completed.
14. Enter exit
twice to leave superuser and to finish the logging script.
The installation procedure generates SQL scripts that are used to create the database.
You should keep these SQL scripts for future reference.
Task 8: Configuring the SQLNet Parameter Files and Client
There are two methods of configuring the SQLNet parameter files or client:
•
Using the Deployment Worksheet. This is the preferred method.
•
Using the command line. This is an alternative method.
This section describes both methods.
Note:
In Oracle 8, SQLNet is called Net 8.
Typically, the Directory server ( imdirserv
) runs on the host where the Directory database is installed, and you install the SQLNet parameter files on this host
( imorainstall
option 3). If the database and the server are on separate hosts, install the SQLNet parameter files on the host with the Directory database ( imorainstall option 3), and install the SQLNet client on the host with the Directory server
( imorasintall
option 7).
Similarly, if an MSS runs on a host with a Message Store database, you install the
SQLNet parameter files on this host. If the database and the server are on separate hosts, install the SQLNet parameter files on the host with the database and install the
SQLNet client on the host with the server.
Using the Deployment Worksheet
This procedure installs a subset of Oracle that lets InterMail servers connect to an
Oracle database.
To configure the SQLNet parameter files or client:
1. Change to the Oracle user: su - oracle
Confidential and Proprietary, © Software.com, Inc. 2000 23
InterMail Mx Installation Guide
2. Create a log to record this installation: script <LogName>
3. Define the environment variables used by the Deployment Worksheet, such as
ORA_SYSTEM
. For example: source setupEnvVar
The setupEnvVar
file is a template file that is provided with InterMail in the oracle
directory. You can customize and run this file if you are using csh
.
If you installed the ISD database or a Message Store database on this host, you may not need to repeat this step.
4. Locate and run imorainstall.
Note:
imorainstall
must be run from the directory that contains the Oracle
.tar
files.
5. Respond to the following prompts:
SQLNet Configuration Prompt
Select a menu item (1 - 11) [11]
Response
3
to configure the SQLNet parameter files on a host that contains a Message Store database or a Directory database
7
to configure the SQLNet client on a host that does not contain a Message Store database or a Directory database
...
Pausing... [Hit enter to continue]
Read the accompanying text and then press
Return.
This prompt appears a number of times during this script.
The path of imorainstall
and the Oracle installation tar files
...
Enter “Install Source” directory:
[<path>]
Please verify the installation configuration...
...
Do you accept these settings? (Yes/No/
Quit) [yes]
•
•
• yes no
if the settings are correct
to change settings quit
to stop the installation process
The "Output to Install" sheet in the
Deployment Worksheet is used to create a file containing data for input to the
InterMail Oracle installation.
Please enter the name of this file
[<path>/imoraparams.txt]
The name and location of the imoraparams.txt
file
24 Confidential and Proprietary, © Software.com, Inc. 2000
Installing InterMail Mx
SQLNet Configuration Prompt
...
Identify this host by its number (1 to
<n>) from the list above: [1]
Response
The number that identifies the current host
Is this host named <HostName>? (Yes/No/
Quit) [Yes]
Y
, unless the host has a different name
Do you wish to configure tnsnames.ora now via method (1)?
Y
, unless you do not have or do not want to use the values in the imoraparams.txt
file. For
help on using the other method, see “Using the
...
The command completed successfully
Started Oracle Sql*Net listener LISTENER successfully.
...
Select a menu item (1 - 11) [11]
11
to quit exit
to finish the logging script.
Using the Command Line
If some difficulty prevents SQLNet from being configured through the Deployment
Worksheet, you can configure it manually as follows:
1. Change to the Oracle user: su - oracle
2. Create a SQLNet Listener, specifying the Oracle home directory, database instance, and fully qualified hostname with domain. For example: createListenerConfig /service/oracle/8.0.5 IMD510 sea.software.com
3. Create a SQLNet instance, specifying the Oracle home directory, database instance, and fully qualified hostname with domain. For example: createSqlNetInstance /service/oracle/8.0.5 IMD510 sea.software.com
4. Start the Listener by entering lsnrctl start
.
Task 9: Installing InterCore
The InterCore installation package installs the following servers:
•
Configuration server
•
Directory server
•
Directory Cache server
Confidential and Proprietary, © Software.com, Inc. 2000 25
InterMail Mx Installation Guide
•
Manager server
•
SNMP server
To install InterCore:
1. Create a log to record the InterCore installation: script /<temp_directory>/<file_name.log>
For example: script /var/tmp/InterCoreInstall.log
2. Create a temporary directory on the local host, and copy the
InterCore.tar.Z
file from the installation medium to this temporary directory. Change your working directory to the temporary directory.
3. Uncompress and untar the
InterCore.tar
file:
–
On a Solaris host: tar xvf InterCore.tar
–
On a non-Solaris host: tar xvf InterCore.tar iminstall
4. Set the user to root: su
5. Do one of the following:
–
On a Solaris host, run pkgadd
: pkgadd -d . InterCore
–
On a non-Solaris host, run iminstall
:
./iminstall
On a non-Solaris host, you will be prompted for a temporary directory into which the tar file can be expanded.
26 Confidential and Proprietary, © Software.com, Inc. 2000
Installing InterMail Mx
6. Respond to the following prompts:
InterCore Installation Prompt
InterCore will be installed with the following settings:
Logical Host Name <host-name>
This host’s DNS Domain Name software.com
InterCore Unix username <username>
InterCore Unix groupname <group>
InterCore install directory <path>
InterCore home directory <path>
Response
• Press Return to accept the settings.
• Enter no
to change one or more of the settings.
• Enter quit
to stop the installation process.
If your InterMail username is not imail
, you may be prompted for information before you see this display.
Do you accept these settings? (Yes/No/
Quit) [yes]
The Configuration server (imconfserv) must be installed on the first InterMail system, and only there. The
Configuration server must be running before subsequent installations are performed.
Will the imconfserv run here? (Yes/No)
[no]
•
Yes
if the Configuration server will run on this host
•
No
if the Configuration server is running on another host
Confidential and Proprietary, © Software.com, Inc. 2000 27
InterMail Mx Installation Guide
InterCore Installation Prompt Response
What is the imconfserv port on <host>?
[<port>]
What is the imconfserv administrative port on <host>? [<port>]
Where would you like to start searching for available port numbers? [<port>]
Would you like the config server running after the installation is complete?
(Yes/No) [yes]
On the first host, which runs the Configuration server, you answered
Yes
to the previous question and therefore will see these prompts.
Enter the port numbers as requested.
You should leave the Configuration server running after the installation is complete.
Config Server Configuration
===========================
Config Server will run on this host? yes
Config Server Port: <port#>
Config Server Administration-Port:
<port#>
Port search starting port number:
<port#>
Leave Config Server running postinstall: yes
Do you accept these settings? (Yes/No/
Quit) [yes]
What is the name of the InterCore host running imconfserv?
What is the imconfserv port on <host>?
[<port>]
What is the imconfserv administrative port on <host>? [<port>]
Where would you like to start searching for available port numbers? [<port>]
On the second through last hosts, which do not run the Configuration server, you will see these prompts.
Enter the name of the host running the
Configuration server and the port numbers, as requested.
Config Server Configuration
===========================
Config Server will run on this host? no
Config Server runs on host: <host>
Config Server Port: <port#>
Config Server Administration-Port:
<port#>
Port search starting port number:
<port#>
Do you accept these settings? (Yes/No/
Quit) [yes]
28 Confidential and Proprietary, © Software.com, Inc. 2000
Installing InterMail Mx
InterCore Installation Prompt
Do you want to set up Failover Groups?
(Yes/No) [no]
The installation will be set up to run the following servers on <currenthost>:
The Manager server... required
The Configuration server...
<running/remote>
The SNMP server... <yes/no>
The Master Directory Server...
<yes/no>
The DirCache Server... <yes/no>
Do you accept these settings? (Yes/No/
Quit) [yes]
Response
• yes
to set up failover groups for your system
• no
if you are not using failover groups
• yes
if the settings are correct
• no
to change settings
• quit
to stop the installation process
If you enter no
, the procedure asks individually whether each server will run on this host.
...
The servers which you have selected to be run will be set up as follows:
Manager server ...
================================= immgrserv port is <port#> immgrserv administrative port is
<port#>
Do you accept these settings? (Yes/No/
Quit) [yes]
For each server that will run on this host, the script asks you to confirm the settings.
For each server, enter:
• yes
if the settings are correct
• no
to change settings
SNMP configuration
==================
SNMP monitoring is enabled for
InterCore servers on this host:
<yes or no>
Do you accept these settings? (Yes/No/
Quit) [yes]
Master Directory Server (imdirserv) ...
======================================
What is the imdirserv RME port?
[<port#>]
• yes
if the settings are correct
• no
to change settings
If you want SNMP monitoring enabled on this host, the monitoring setting should be yes
.
You will see this prompt on the Directory
server host.
(If the Directory server does not run on this host, skip ahead to the prompts for the Directory
Cache server ( imdircacheserv
) configuration.)
In reponse to this prompt, enter the RME port number. Take the default port number, or specify an appropriate port of your choosing.
Confidential and Proprietary, © Software.com, Inc. 2000 29
InterMail Mx Installation Guide
InterCore Installation Prompt
What is the imdirserv LDAP port?
[<port#>]
Response
The LDAP port number
This is typically the main provisioning port, the port through which the Directory server fields
LDAP requests.
What is the imdirserv administrative port? [<port#>]
What is the Root DN for the directory?
[cn=root]
The administrative port number
This port is used to shut down the server or query the server for status.
The LDAP root distinguished name (DN)
This is the root of the directory tree.
What is the LDAP Root Password for the directory? [<string>]
What is the Oracle Database username that InterCore will use? [<username>]
What is the Oracle Database password that InterCore will use? [<string>]
The LDAP root password
This password allows master administrative access to the LDAP tree. It is a randomly generated string that will be stored in the
Configuration database. You may want to change this password and make note of it. (You can find this password later in the Configuration database, if necessary.)
The InterMail username and password for connecting to the Directory database
What is the Oracle Database connection string that InterCore will use?
[IMD510]
Initialize the Master Directory in the
Oracle DB? (Yes/No) [yes]
Create the Administration (postmaster, mail-daemon, etc.) Accounts? (Yes/No)
[yes]
Deliver mail for the Admin Accounts to which host? [<current-host>]
The TNS name of the Directory database
The default is IMD510. You can specify a different string, but the limit is 8 characters.
•
Yes
to direct the installation to initialize the
Oracle database with a new LDAP tree
•
No
if this is not necessary
•
Yes
to direct the installation to create the postmaster
, imail
, and mailer-daemon accounts
•
No
if this is not necessary
The name of a host that will run an MSS
You see this prompt only if you answered
Yes
to the question about initializing the Directory database.
30 Confidential and Proprietary, © Software.com, Inc. 2000
Installing InterMail Mx
InterCore Installation Prompt
NOTE: For more information about allocations, see the InterMail documentation for the Directory. Also note that the default, or a custom, allocation scheme may be loaded at a later time.
Load Default Allocation Scheme? (Yes/
No) [no]
Response
•
Yes
to load the default allocation scheme
•
No
otherwise
What is your Organization/Company Name?
The name of your company. For example:
Acme Messaging, Inc.
You see this prompt only if you answered
Yes
to the question about initializing the Directory database.
... Master Directory Server ...
=============================== imdirserv RME port: <port#> imdirserv LDAP port: <port#> imdirserv Administrative port: <#>
LDAP Root DN: <string>
LDAP Root Password: <string> default BindDN: <string> default BindPassword: <string>
Oracle Database Userinfo: <string>
Oracle Connection String: <SID>
Initialize Oracle Directory DB: <y/n>
Create Administrative Accounts: <y/n>
Delivery Host for Admin Accounts:
<host-name>
Do you accept these settings? (Yes/No/
Quit) [yes]
• yes
if the settings are correct
• no
to change settings
The default
BindDN
and
BindPassword settings are the same as for root initially but can be modified later. The indicated server or component (such as imdircacheserv
, C API, imdbcontrol
) uses these LDAP credentials by default. Before the administrative infrastructure is installed, non-root values for these settings are meaningless.
Confidential and Proprietary, © Software.com, Inc. 2000 31
InterMail Mx Installation Guide
InterCore Installation Prompt
Configuration of Local Directory
Cache server (imdircacheserv)
================================ imdircacheserv RME port <port#> imdircacheserv LDAP port is <port#> imdircacheserv administrative port is <port#>
Create imdircacheserv DB file
<yes or no>
Response
You will see this information on hosts that run
a Directory Cache server. Enter:
• yes
if the settings are correct
• no
to change settings
If you want to specify additional Directory
Cache servers for this host, enter
No
and specify the additional servers when prompted.
...Dir Cache Servers for this host
================================== imdircacheserv host(s) <hostnames>
Do you accept these settings? (Yes/No/
Quit) [yes]
Directory Cache server (imdircacheserv) configuration
=======================================
What is the name of this host’s primary
Directory Cache server?
Is there an additional Directory Cache server for this host? (Yes/No) [no]
Configuration of Directory Cache servers for this host
================================ imdircacheserv host(s) <hosts>
You will see this information on hosts that do
not run a Directory Cache server.
Enter the name of the host with a Directory
Cache server that will be the primary imdircacheserv
for this host.
If you are configuring additional Directory
Cache servers for this host, list them as well.
Then enter:
• yes
if the settings are correct
• no
to change settings
Do you accept these settings? (Yes/
No/Quit) [yes]
Directory Oracle configuration
==============================
$ORACLE_HOME <path>
$TNS_ADMIN <path>
Do you accept these settings? (Yes/No/
Quit) [yes]
You will see this prompt on hosts that run the
Directory server or a Directory Cache server.
Enter:
•
• yes no
if the settings are correct
to change settings
For more information, see “Oracle Installation
Configuration Settings” on page 38.
32 Confidential and Proprietary, © Software.com, Inc. 2000
Installing InterMail Mx
InterCore Installation Prompt Response
Directory Oracle configuration
==============================
Oracle information is not configured for this host.
NOTE: Based on which servers are configured to run on this host,
Oracle is not required to be configured.
However, if Oracle or the Oracle
SQLNet client is installed on this host you may configure the Oracle information at this time to provide convient access to your Oracle database from this host.
Do you accept these settings? (Yes/
No/Quit) [yes]
You will see this information on hosts that do
not run the Directory server or a Directory
Cache server.
The first message indicates that Oracle information for the Directory database is not configured on this host. Since neither the
Directory server nor a Directory Cache server is configured to run on this host, Oracle does not need to be configured for the Directory database.
If you have Oracle installed on this host for a
Message Store database, you will configure those Oracle settings later, during the InterMail portion of the installation.
In response to the prompt, enter:
•
Yes
if you do not need to configure Oracle at this time, based on the information above
•
No
to change the settings
The following files are already installed on the system and are being used by another package:
<list-of-files>
Do you want to install these conflicting files [y,n,?,q]
You should see this message only during an upgrade installation.
If you see this message, InterMail was previously installed on this host. Press Return until the file list is done and then enter
Y
in response to the follow-on prompt.
The following files are being installed with setuid and/or setgid permissions:
<list-of-files>
Do you want to install these setuid/ setgid files [y,n,?,q]
Y
This prompt appears only on Solaris platforms.
This package contains scripts which will be executed with super-user permission during the process of installing this package.
Do you want to continue with the installation of <InterCore> [y,n,?]
Y
This prompt appears only on Solaris platforms.
Confidential and Proprietary, © Software.com, Inc. 2000 33
InterMail Mx Installation Guide
7. The installation script displays various messages as it finishes installing
InterCore. When installation is complete, the script displays the following message:
To run this installation of InterCore software, login as
"imail" and make sure that either:
’<imail-path>/.cshrc’, or
’<imail-path>/.profile’ is used to initialize your shell’s environment. This sets the
InterCore environment variable and appends /<imail-path>/bin to the command PATH.
Installation of <InterCore> was successful.
exit
twice to leave superuser and to finish the logging script.
Task 10:
Installing InterMail
The InterMail installation package installs one or more of the following servers on a host:
•
Queue server
•
MTA
•
POP server
•
IMAP server
•
Message Store Server (MSS)
•
WebEdge server
To install InterMail:
1. Create a log to record the InterMail installation: script /<temp_directory>/<file_name.log>
For example: script /var/tmp/InterMailInstall.log
2. Create a temporary directory on the local host, and copy the
InterMail.tar.Z
file from the installation medium to this temporary directory. Uncompress the file. Change your working directory to the temporary directory.
3. Untar the
InterMail.tar
file:
–
On a Solaris host: tar xvf InterMail.tar
–
On a non-Solaris host: tar xvf InterMail.tar iminstall
4. Set the user to root: su
34 Confidential and Proprietary, © Software.com, Inc. 2000
Installing InterMail Mx
5. On a non-Solaris host, clear the JAVA_HOME environment variable, to prevent conflicts. For example, in csh
: unsetenv JAVA_HOME
Or, from sh
: unset JAVA_HOME
6. Start the InterMail installation:
–
On a Solaris host, run pkgadd
: pkgadd -d . InterMail
–
On a non-Solaris host:
Run iminstall
:
./iminstall
You will be prompted for a temporary directory into which the tar file can be expanded.
7. Respond to the following prompts:
InterMail Installation Prompt Response
What is the Unix username that InterMail will use? [imail]
The InterMail username
If you installed InterCore with the default username, the script does not display this prompt.
InterMail will be installed with the following settings:
InterMail Unix username <user-name>
InterMail Unix groupname <group-name>
Logical Host Name <host-name>
InterMail install directory <path>
InterMail home directory <path>
Do you accept these settings (Yes/No/
Quit) [yes]?
• yes
if the settings are correct
• quit
to stop the installation process
These values were taken from the config.db file that was created during the InterCore installation. If any of these values are incorrect, follow the instructions that the script displayed before it listed the settings.
The installation will be set up to run the following servers on “<host-name>”:
The Queue Server... <yes/no>
The Message Transport Agent... <yes/ no>
The POP Server... <yes/no>
The IMAP Server... <yes/no>
The Message Store Server... <yes/no>
The WebEdge Server... <yes/no>
Do you accept these settings (Yes/No/
Quit) [yes]?
• yes
if the settings are correct
• no
to change the settings
If you enter no
, the procedure asks individually whether each server will run on this host.
If none of these servers will run on this host, you still need to continue with the InterMail installation. The installation performs other actions besides installing these servers.
Confidential and Proprietary, © Software.com, Inc. 2000 35
InterMail Mx Installation Guide
InterMail Installation Prompt Response
...
The servers which you have selected to run will be set up as follows:
MTA configuration
=================
MTA spool directory is <path>
MTA SMTP port is (normally 25) <port>
MTA administrative port is <port#>
MTA Default Domain <domain-name>
SSL Operation supported <yes-or-no>
SSL SMTP port is (normally 465) 465
Certificate file: <file-with-path>
Queue server host(s): <host-list>
Do you accept these settings? (Yes/No/
Quit) [yes]
The script displays settings for each server that you requested to have run on this host. Typically, only a subset of the servers will run on a given host.
For each server, enter:
• yes
if the settings are correct
• no
to change the settings queue server configuration
========================== queue server port is <port#> queue server administrative port is
<port#> queue server journal directory <path>
Do you accept these settings? (Yes/No/
Quit) [yes]
• yes
if the settings are correct
• no
to change settings
• yes
if the settings are correct
• no
to change settings
POP configuration
=================
POP3 port is (normally 110) <port#>
POP administrative port is <port#>
SSL Operation supported <yes/no>
SSL POP3 port is (normally 995)
<port#>
Certificate file: <file-with-path>
Do you accept these settings? (Yes/No/
Quit) [yes]
IMAP configuration
=================
IMAP4 port is (normally 143) <port#>
IMAP administrative port is <port#>
SSL Operation supported <yes/no>
SSL IMAP port is (normally 993)
<port#>
Certificate file: <file-with-path>
Do you accept these settings? (Yes/No/
Quit) [yes]
• yes
if the settings are correct
• no
to change settings
Typically, you should not change the port settings.
36 Confidential and Proprietary, © Software.com, Inc. 2000
Installing InterMail Mx
InterMail Installation Prompt
WebEdge configuration
=====================
On which port will WebEdge run? [80]
Response
Press Return to accept the default.
What is the administrative port for the
WebEdge server? [8080]
Press Return to accept the default.
What is the administrative password
WebEdge will use?
Enter a password. Make note of this password, because it is not stored in the Configuration database (so you cannot look it up there later).
WebEdge configuration
=====================
WebEdge server port is (normally 80)
<port#>
WebEdge administrative port is
<port#>
WebEdge administrative password
<string>
Do you accept these settings? (Yes/No/
Quit) [yes]
• yes
if the settings are correct
• no
to change settings
MSS configuration
=================
MSS message files directory <path>
Number of message file directories on level 1 <default-is-10>
Number of message file directories on level 2 <default-is-10>
Number of message file directories on level 3 <default-is-10>
MSS journal directory <path>
MSS uses SQL*Net to connect to Oracle
<yes/no>
MSS port configurations:
==================================
No. of ports <num>
Base port <port#>
Base Admin port <port#>
==================================
MSS Oracle user/password <user/pswd>
MSS Oracle connection string
<IMM510_1>
MSS Oracle SQL context count <count>
Do you accept these settings? (Yes/No/
Quit) [yes]
• yes
if the settings are correct
• no
to change settings
If the MSS runs on the same host as the Message
Store database, do not use SQL*Net to connect to Oracle. If the MSS is on a different host from the Message Store database, you must use
SQL*Net.
Confidential and Proprietary, © Software.com, Inc. 2000 37
InterMail Mx Installation Guide
InterMail Installation Prompt
Mail Store Server Oracle configuration
==============================
$ORACLE_HOME <path>
$TNS_ADMIN <path>
Response
• yes
if the settings are correct
• no
to change settings
Do you accept these settings? (Yes/
No/Quit) [yes]
The following files are already installed on the system and are being used by another package:
<list-of-files>
Do you want to install these conflicting files [y,n,?,q]
You should see this message only during an upgrade installation.
If you see this message, InterMail was previously installed on this host. Press Return until the file list is done, and then enter
Y in response to the follow-on prompt.
This package contains scripts which will be executed with super-user permission during the process of installing this package.
Do you want to continue with the installation of <InterMail> [y,n,?]
Y
This prompt only appears on Solaris platforms.
8. At the end of the installation, the script displays the following information:
To run InterMail software, login as “<username>” and make sure that either /<imail-path>/.cshrc or /<imail-path>/.profile is used to initialize your shell’s environment. This sets the INTERMAIL environment variable and appends /<imail-path>/bin to the command
PATH.
Creating directory: ...
...
Installation of <InterMail> was successful.
exit
twice to leave superuser and to finish the logging script.
Continue installing on other host machines. When you have completed your
installations on all your hosts, see Chapter 3 for post-installation tasks.
Oracle Installation Configuration Settings
This section provides further information on the installation configuration settings that the imorainstall
script displays when you install the ISD database or a Message
Store database
38 Confidential and Proprietary, © Software.com, Inc. 2000
.
Setting
InterMail Oracle username
Oracle SYSTEM password
Oracle SYS password
Base installation directory
ORACLE_HOME
TNS_ADMIN
Installation source directory
Installing InterMail Mx
Explanation
The InterMail username (not the Oracle username).
Every Oracle database has its own usernames and passwords that are independent of the usernames and passwords of the operating system. This is the username that InterMail uses to log in to the database.
An administrative password used independently of InterMail’s support for
Oracle. Any name can be chosen for this password, but be sure to remember it.
InterMail usually does not need this password.
The Oracle system administrator password.
The directory in which the Oracle databasecreation SQL scripts and installation log files are stored. For example:
/service/oracle
The directory where the Oracle files, binaries, and libraries are installed. For example:
/service/oracle/8.0.5
An environment variable required when
SQL*Net is used to connect to an Oracle database. For example:
/service/oracle/8.0.5/network/ admin
This variable controls where Oracle looks for configuration files for connecting through SQL*Net.
The source directory of the installation media. For example:
/service/oracle
Confidential and Proprietary, © Software.com, Inc. 2000 39
InterMail Mx Installation Guide
Setting
Scratch directory for temporary installation files
Explanation
The location to which the installation procedure should write temporary files.
These files are removed after the installation procedure is complete.
The installation procedure requires a minimum of 40 MB of scratch space to untar the Oracle files.
“oracle” user home directory
Service instance
The directory in which the Oracle installation creates or replaces
.cshrc
and
.profile
files that set up the environment for the new database. For example:
/home/oracle
The number of the Message Store database you are installing.
The installation procedure uses this number when it creates the Message Store database name (also known as the System ID or
ORACLE_SID
).
When you install the ISD database, the installation procedure automatically supplies an appropriate service instance.
Database instance name (
ORACLE_SID
) The name of an Oracle database, also called the System ID or SID. This name is also the connection string used for Oracle.
Because this name is recorded in each of the database’s files, changing it after installation requires significant effort.
You can choose your own instance names.
By default, the ISD database name is
IMD510
and a Message Store database name is
IMM510_<#>
, where
<#>
is the service instance.
Note: This value is limited to 8 characters.
40 Confidential and Proprietary, © Software.com, Inc. 2000
Installing InterMail Mx
Troubleshooting
This section describes some problems that can occur during an InterMail installation and provides information to help solve these problems.
The problems discussed in this section include the following:
•
•
•
Need to Restart InterCore or InterMail Installation
If an error occurs during installation, look at the log information recorded in the following file:
<install-directory>/tmp/<task-name>.out
You should capture the output of your installation tasks using a tool like script
.
Such output files are very helpful for tracking down installation problems.
SNMP Installation Problems
This section describes potential SNMP installation problems.
Solaris 2.6 Port Conflict
An SNMP agent is included in the Solaris 2.6 operating system. It uses port 161, which is one of the ports the InterMail SNMP server defaults to. If you intend to use the InterMail SNMP server, you’ll need to change either the InterMail or the Solaris
SNMP port settings.
The InterMail SNMP ports can be changed in the config.db
through the snmpRequestPort
and snmpTrapPort
settings.
Turning On SNMP After Installing InterMail
If you choose not to activate the InterMail SNMP server during the installation but decide to activate it afterwards, you’ll need to manually set the
/*/common/ masterAgentHost configuration key.
Failed Database Installation
This section describes how to handle the following problems with database installation:
•
Insufficient Shared Memory or Semaphores
•
Need to Deallocate Shared Memory Segments
•
When it detects a failure, the imorainstall
utility typically shuts down the database before terminating. You must ensure that the database is shut down before you delete any of the files created during the failed installation.
Confidential and Proprietary, © Software.com, Inc. 2000 41
InterMail Mx Installation Guide
To check whether the database is shut down, enter the following command (where
<oracle-SID>
represents the Oracle ID for the database such as IMD510): ps -ef | grep <oracle-SID> | grep -v grep
If any processes are listed, the database is not shut down. Shut down the database by running:
$ORACLE_HOME/bin/shutdownDB <oracle-SID>
Insufficient Shared Memory or Semaphores
A common reason that Oracle installations fail is because the operating system kernel configuration does not provide sufficient shared memory or semaphores.
The following errors indicate insufficient shared memory:
ORA-02814, "Unable to get shared memory"
ORA-02815, "Unable to attach shared memory"
ORA-09877, "sstascre: shmget error, unable to get a shared memory segment."
ORA-09878, "sstascre/sstasat: shmat error, unable to attach tas write page"
The following errors indicate insufficient semaphores:
ORA-02721, "osnseminit: cannot create semaphore set"
ORA-07250, "spcre: semget error, unable to get first semaphore set."
ORA-07251, "spcre: semget error, could not allocate any semaphores."
ORA-07252, "spcre: semget error, could not allocate semaphores."
ORA-07279, "spcre: semget error, unable to get first semaphore set."
ORA-07339, "spcre: maximum number of semaphore sets exceeded."
For information on setting appropriate values for the kernel parameters related to
shared memory and semaphores, see “Preparing the Hardware and Software” on page 3.
Need to Deallocate Shared Memory Segments
If installation of either the ISD database or Message Store database is aborted, you may not be able to install the Oracle database correctly until shared memory segments have been deallocated.
This section describes two methods for deallocating shared memory. If the first one fails, try the second one.
To deallocate shared memory using
ShutdownDB:
1. Shut down the Oracle instance, and make sure that no other Oracle instances are running.
shutdownDB <instance> from the Oracle directory, where
<instance> is the offending Oracle instance. For example: cd $ORACLE_HOME/bin shutdownDB IMD510
42 Confidential and Proprietary, © Software.com, Inc. 2000
Installing InterMail Mx
If this is not successful, enter the following commands: cd $ORACLE_HOME/bin svrmgrl connect internal shutdown immediate ( or,
shutdown abort)
You are now ready to reinstall the ISD database or Message Store database.
To deallocate shared memory by killing Oracle processes and shared memory segments:
1. Shut down the Oracle instance, and make sure that no other Oracle instances are running.
2. As the Oracle user, check to see which Oracle processes are running: cd - oracle ps -aef | grep oracle
3.
kill-9
to kill all of the processes listed in the ps
output.
root
, display the Oracle shared memory segments ( m
) and semaphores ( s
) in use by issuing a UNIX ipcs
command: su - root ipcs
The output might look something like this:
IPC status from <running system> as of Tue Apr 7 12:16:26 1998
Message Queue facility not in system.
Shared Memory m 0 0x0ddd0251 --rw-r----- oracle dba m 1 0x0ddd0248 --rw r----- oracle dba m 1002 00000000 --rw-rw---- imail imail
Semaphores: s s
0 00000000 --ra-r----- oracle dba
1 00000000 --ra-r----- oracle dba
5. Change to the user indicated in the code above, and use ipcrm -m and ipcrm -s to remove the shared memory segments and semaphores. For example: su - oracle ipcrm -m 0 ipcrm -m 1 ipcrm -s 0 ipcrm -s 1 su - imail ipcrm -m 1002
You are now ready to reinstall the ISD database or Message Store database.
Omission of Reserved Accounts
During the InterCore and/or InterMail installation scripts, if the reserved accounts— imail
, root
, mailer-daemon
, and postmaster
—have not been created, the
Confidential and Proprietary, © Software.com, Inc. 2000 43
InterMail Mx Installation Guide
imservctrl start
or imctrl start
command may report an error that Oracle has failed to update account information. This is because InterMail tried to synchronize the local account information with the Directory Cache database, but no account information existed. This is typical, and will be corrected as soon as accounts are provisioned.
Need to Restart InterCore or InterMail Installation
If you need to restart the installation of InterCore or InterMail, you must first delete the previous package files. Execute these commands: su cd /var/sadm/pkg rm -rf InterCore rm -rf InterMail
On Solaris platforms, it is recommended that you use the above commands and that you not use pkgrm
to remove the package files.
44 Confidential and Proprietary, © Software.com, Inc. 2000
3
Post-Installation Tasks
This chapter discusses tasks that you should perform after you install InterMail but before you launch your production environment.
This chapter does not discuss InterMail configuration or system maintenance. For information on these subjects, see the InterMail Mx Operations Guide.
If the commands and syntax in this chapter are unfamiliar to you, see the command syntax, usage, and options descriptions in the InterMail Mx Reference Guide.
This chapter contains the following sections:
•
•
Checking the InterMail Environment
•
•
•
Pinging Servers and Checking Processes
•
•
Sending Mail from a Non-MTA Host
•
Using the EMANATE Utilities in SNMP
Logging On to the System
The first task in testing the InterMail installation is to log on to the system as the
InterMail user. On each host in the system, follow these steps:
1. Change to the InterMail user you created during the installation. For example: su - imail
2. Check the home directory by issuing a pwd
command. The directory indicated should be the InterMail directory you created during the installation.
Confidential and Proprietary, © Software.com, Inc. 2000 45
InterMail Mx Installation Guide
3. Check the Oracle installation directory and user by becoming the Oracle user and repeating steps 1 and 2. The home directory indicated should be the Oracle directory you created during the installation.
Checking the InterMail Environment
After logging on, you are ready to check the InterMail environment. In the installation process, InterMail created
.cshrc
(C shell profile) and
.profile
(Bourne shell profile) resource files. These files provide InterMail with basic information about environment variables such as the path to the InterMail home directory, InterMail binaries, shared library files, the Oracle home directory, and Oracle binaries. When you log on to the system, InterMail reads the environment variables contained in one of these files.
You can use the cat .cshrc
command in the InterMail home directory to view these variables. Following is an example of a
.cshrc
file:
46 Confidential and Proprietary, © Software.com, Inc. 2000
Post-Installation Tasks
setenv INTERMAIL /vol1/imail setenv PERLHOME /vol1/imail/perl setenv SR_LOG_DIR /vol1/imail/log setenv SR_AGT_CONF_DIR /vol1/imail/snmp setenv SR_MGR_CONF_DIR /vol1/imail/snmp setenv EMANATE_HOME /vol1/imail/bin setenv SR_SNMP_TEST_PORT 40161 setenv SR_TRAP_TEST_PORT 40162 setenv NLSPATH $INTERMAIL/lib/nlslib/%L/%N.cat
setenv ORACLE_HOME /vol1/oracle/8.0.5
setenv TNS_ADMIN /vol1/oracle/8.0.5/network/admin setenv ORACLE_USERINFO imail/imail setenv PATH ${INTERMAIL}/bin:${INTERMAIL}/lib:${ORACLE_HOME}/ bin:${INTERMAIL}/pe rl/bin:/sbin:/usr/sbin:/usr/bin:/usr/sadm/install/bin:.
setenv SR_LOG_DIR /vol1/imail/log setenv SR_AGT_CONF_DIR /vol1/imail/config setenv SR_MGR_CONF_DIR /vol1/imail/config setenv TCL_LIBRARY $INTERMAIL/lib/tcl setenv NLSPATH $INTERMAIL/lib/nlslib/%L/%N.cat
setenv PERL5LIB /vol1/imail/perl/lib/perl5/sun4-solaris/5.003:/vol1/imail/ perl/l ib/perl5:/vol1/imail/perl/lib/perl5/site_perl/sun4-solaris:/vol1/imail/ perl/lib/ perl5/site_perl:.
setenv ORACLE_USERINFO imail/imail setenv ORACLE_DB_SERVICE IMD510 setenv ORACLE_SID IMD510 setenv EPC_DISABLED TRUE setenv PATH
${INTERMAIL}/bin:${ORACLE_HOME}/bin:${PERLHOME}/bin:/usr/bin:/sbin:/usr/ sbin
:/usr/bin:/usr/sadm/install/bin:.
setenv LD_LIBRARY_PATH
/opt/SUNWspro/lib:$(ORACLE_HOMOE)/lib:$(INTERMAIL)/lib: setenv MANPATH /usr/share/catman:/usr/share/man:/usr/catman:/usr/ man:${INTERMAIL}/man:${PERLHOME}/man umask 007 if( $?prompt ) then set filec=true set history=50 stty erase \_ intr \^c kill \^u eof \^d susp \^z echoe echok set prompt=
’ saturn:imail5_1_0%
’ endif
Taking Directory Snapshots
After installing InterMail, create a record of all directories and associated permissions as they were installed. For this operation, use the following command to create a list of all files in “long” format so that the structure and file permissions for all InterMail directories will be shown: ls -lR > <filename>
Confidential and Proprietary, © Software.com, Inc. 2000 47
InterMail Mx Installation Guide
Repeat this step on all host machines in the system, as well as in the
$ORACLE_HOME directory.
Taking snapshots of InterMail directories has two important benefits:
•
It helps with troubleshooting, should permissions on files change due to unforeseen circumstances or operator error.
•
It reveals the exact structure of the Message File system. This is important, because if the Message File system is lost or corrupted, you will need to re-create it exactly.
Note:
With few exceptions, the permissions for all directories and files in the
InterMail system should be imail
for user and group.
Starting and Stopping Servers
After logging on to the InterMail system and checking the environment, you are ready to start the InterMail servers. This can be accomplished in one of two ways: through imservctrl
for a local host, or through imctrl
for local and remote hosts. This section describes the use of imservctrl
on a local host.
•
To start InterMail servers on the local host, enter:
$INTERMAIL/lib
/imservctrl start
You will see messages about servers being started. Watch for any failures.
To confirm that the servers are running, you can issue a ps -aef | grep imail
command.
•
To stop InterMail servers on the local host, enter:
$INTERMAIL/lib
/imservctrl stop
When you run the imservctrl stop
command, InterMail stops each server process on the local host, lists the process ID for each, and removes all information in the
$INTERMAIL/tmp
directory that is specific to the running session that was just stopped.
To confirm running processes, issue a ps -aef | grep imail
command to ensure that no processes are remaining after InterMail has been stopped: venus% ps -aef | grep imail imail 5062 5060 0 14:36:43 pts/3 0:01 -csh imail 4879 4877 0 10:00:09 pts/1 0:01 -csh
For more information on the imservctrl
and imctrl
commands, see the InterMail
Mx Operations Guide and the InterMail Mx Reference Guide.
When you have finished testing how to start and stop servers, start all the servers and continue with the tasks in the rest of this chapter.
48 Confidential and Proprietary, © Software.com, Inc. 2000
Post-Installation Tasks
Pinging Servers and Checking Processes
The imservctrl
command starts all servers on the local host in the required order. It also reports the status of all servers that have been started. If you need a more detailed view of server status, use imservdisplay
, ping the servers, or check the InterMail processes. These tasks are described below.
Using imservdisplay
Use the imservdisplay
command to display the status of servers and any log entries that have been written since the server was started. For example: venus% imservdisplay
Monitoring InterMail modules: imapserv imconfserv imdircacheserv imdirserv immgrserv imqueueserv mss mta popserv webedge
MessageStore Report:
--------------------
Oracle Version: InterMail 4.1.0
Number of Messages: 0
Number of Mailboxes: 1 imapserv Report:
----------------
Note: ProcFound: imapserv process Found as PID: 4735.
Note: ServerPing: imapserv responded to version query ...
...
imconfserv Report:
------------------
Note: ProcFound: imconfserv process Found as PID: 4524.
...
Pinging Servers
In addition to using imservdisplay
to see whether servers are running, it is helpful to ping InterMail servers to see their response times. You can specify parameters to ping specific servers, or you can ping all the servers by issuing the command with no parameters.
Confidential and Proprietary, © Software.com, Inc. 2000 49
InterMail Mx Installation Guide
For example: venus% imservping 1 5 mss
Thu Feb 17 10:03:18 2000. imservping: (Info) mss.1 responded
Thu Feb 17 10:03:18 2000. imservping: (Info) mss.2 responded
Thu Feb 17 10:03:18 2000. imservping: (Info) mss.3 responded
...
venus% imservping
Thu Feb 17 12:11:53 2000. imservping: (Info) webedge responded
Thu Feb 17 12:11:53 2000. imservping: (Info) mss.1 responded
Thu Feb 17 12:11:53 2000. imservping: (Info) mss.2 responded
Thu Feb 17 12:11:53 2000. imservping: (Info) mss.3 responded
Thu Feb 17 12:11:53 2000. imservping: (Info) mss.4 responded
Thu Feb 17 12:11:53 2000. imservping: (Info) imapserv responded
Thu Feb 17 12:11:53 2000. imservping: (Info) imconfserv responded
Thu Feb 17 12:11:53 2000. imservping: (Info) immgrserv responded
...
Note:
It is recommended that you check server response times by modifying the time intervals that imservping
uses to check the server.
Checking InterMail Processes
After pinging servers, check the time/date stamp of InterMail server processes by issuing a ps -aef | grep imail
command: venus% ps -aef | grep imail
imail 446 1 0 Mar 18 ? 0:44 /vol1/imail/lib/mss.1 -db
imail 629 1 0 Mar 18 ? 0:19 /vol1/imail/lib/imapserv
imail 5042 4879 0 13:41:38 pts/1 0:00 grep im
imail 354 1 0 Mar 18 ? 1:01 /vol1/imail/lib/imconfserv
imail 4879 4877 0 10:00:09 pts/1 0:01 -csh
imail 523 1 0 Mar 18 ? 3:47 /vol1/imail/lib/mta
imail 499 1 0 Mar 18 ? 1:19 /vol1/imail/lib/imqueueserv
imail 413 1 0 Mar 18 ? 2:36 /vol1/imail/lib/ imdircacheserv
imail 392 1 0 Mar 18 ? 0:09 /vol1/imail/lib/immgrserv
root 369 1 0 Mar 18 ? 0:01 /vol1/imail/lib/snmpdm aperror
imail 581 1 0 Mar 18 ? 0:23 /vol1/imail/lib/popserv
If the time/date stamp does not reflect the latest time servers were started, this may indicate that a process ID remains, in which case it needs to be manually removed
(with kill -9 <pid>
). Once the process has been removed, restart the affected server using the imservctrl start <server>
command.
Checking the Databases
At this point, assuming that all servers are running and can be contacted, you are ready to check the operation of the Integrated Services Directory (ISD) and Message Store databases.
50 Confidential and Proprietary, © Software.com, Inc. 2000
Post-Installation Tasks
To check the operation of each database, use the following procedure:
1. Set user to Oracle.
su - oracle
2. Run the following command, where
<OracleSID>
is the Oracle system ID for the database: showDB <OracleSID>
For example: showDB IMD510
The default SID for the ISD database is IMD510 and the default SID for the first
Message Store database is IMM510_1. Your SIDs will be different if you specified custom SIDs during installation.
3. To confirm that the database is running and that the Listener is running and configured correctly, enter: tnsping <OracleSID>
For example: venus% tnsping IMM510_1
TNS Ping Utility for Solaris: Version 8.0.5.0.0 - Production on
08-MAR-00 16:30:08
(c) Copyright 1997 Oracle Corporation. All rights reserved.
Attempting to contact
(ADDRESS=(PROTOCOL=TCP)(Host=venus)(Port=1521))
OK (90 msec)
Testing Message Flow
To ensure that the InterMail message flow is working properly, follow these steps:
1. Create test accounts.
2. Synchronize the ISD and the Directory cache.
3. Check message delivery.
4. Check message storage.
5. Check message retrieval.
This section describes these steps in detail.
Confidential and Proprietary, © Software.com, Inc. 2000 51
InterMail Mx Installation Guide
Creating Test Accounts
Create two test accounts using the imdbcontrol CreateAccount
command. For example: testuser01
: imdbcontrol CreateAccount testuser01 venus 12345 testuser01 testuser01 clear software.com A S testuser02
: imdbcontrol CreateAccount testuser02 venus 23456 testuser02 testuser02 clear software.com A S
Synchronizing the ISD and Directory Cache
To make sure that the Directory cache has up-to-date information about the accounts you just created, do the following:
1. Shut down the Directory Cache server:
$INTERMAIL/lib/imservctrl stop imdircacheserv imdirsync
:
$INTERMAIL/lib/imdirsync
3. Restart the Directory Cache server:
$INTERMAIL/lib/imservctrl start imdircacheserv
Repeat these steps on each host in your system that runs a Directory Cache server.
Checking Message Delivery
To check message delivery, telnet
to port 25 on the Message Transport Agent
(MTA), log in as testuser01
, and send a message to testuser02
as follows: venus% telnet 0 25
Trying 0.0.0.0...
Connected to 0.
Escape character is ’^]’.
220 venus.software.com ESMTP server (InterMail vM5.01.00.00 201-246) ready
Thu, 17 Feb 2000 12:29:33 -0800
MAIL FROM: [email protected]
250 Sender <[email protected]> Ok
RCPT TO: [email protected]
250 Recipient <[email protected]> Ok
DATA
354 Ok Send data ending with <CRLF>.<CRLF>
This is a test.
.
250 Message received: [email protected]
quit
In the telnet
command,
0
indicates the current host. If you are connecting to a remote host, specify the hostname instead of
0
.
52 Confidential and Proprietary, © Software.com, Inc. 2000
Post-Installation Tasks
After the message has been created and sent, you can check the mta.log
file to view events related to this test transaction.
Checking Message Storage
After a message has been successfully delivered to testuser02
, check to make sure that message storage is functioning properly by listing the contents of testuser02
’s
INBOX. For example: venus% imfolderlist [email protected] -all
Account [email protected], Message Store -2,
Folder /INBOX contains 1 message(s):
0:From: <[email protected]>
0:Date: Thu, 17 Feb 2000 18:34:57 -0800
0:Message-Id: <[email protected] >
Checking Message Retrieval
After confirming that a test message has been successfully delivered and stored, check message retrieval. You can do this from a POP client, from an IMAP client, or from any host using Telnet, whichever is appropriate for your configuration.
To test retrieval using Telnet on the POP port, telnet to the POP port and log in as testuser02
: venus% telnet 0 110
Trying 0.0.0.0...
Connected to 0.
Escape character is ’^]’.
+OK InterMail POP3 server ready.
user testuser02
+OK please send PASS command
pass testuser02
+OK testuser02 is welcome here
retr
... <message is displayed> ...
Confidential and Proprietary, © Software.com, Inc. 2000 53
InterMail Mx Installation Guide
To test retrieval using Telnet on the IMAP port, telnet to the IMAP port and log in as testuser02
: venus% telnet 0 143
Trying 0.0.0.0...
Connected to 0.
Escape character is ’^]’.
* OK IMAP4 server (InterMail vM.5.01.00.00 201-249) ready Thu, 17 Feb 2000
16:33:19 -0800 (PST)
1 login testuser02 testuser02
1 OK LOGIN completed
2 select inbox
* 1 EXISTS
* OK [UIDVALIDITY 952561915] UIDs valid
* FLAGS (\Answered \Flagged \Deleted \Draft \Seen)
* OK [PERMANENTFLAGS (\* \Answered \Flagged \Deleted \Draft \Seen)]
Permanent flags
* 1 RECENT
2 OK [READ-WRITE] SELECT completed
3 fetch 1:* rfc822.header
* 1 FETCH (RFC822.HEADER {432}
Return-Path: <[email protected]>
Received: from [127.0.0.1] by venus.software.com
(InterMail vM.5.01.00.00 201-249) with SMTP id <20000309003145.AAA1867.venus.software.com@[127.0.0.1]> for <[email protected]>; Thu, 17 Feb 2000 16:31:45 -0800
Message-Id: <20000309003145.AAA1867.venus.software.com@[127.0.0.1]>
Date: Thu, 17 Feb 2000 16:31:54 -0800
From: <[email protected]>
)
3 OK FETCH completed
4 list "" *
* LIST () "/" "INBOX"
* LIST () "/" "SentMail"
* LIST () "/" "Trash"
4 OK LIST completed
5 fetch 1:1 rfc822
... <message is displayed> ...
6 logout
* BYE IMAP4 server terminating connection
6 OK LOGOUT completed
When you telnet to the IMAP port, each command you enter must be preceded by a sequence number or character. You can use the same number or character for each command, but it is useful to use different numbers to associate responses with commands because the responses from this port are asynchronous.
In the above example:
•
The first command logs in to the testuser02
account. The first occurrence of testuser02
in the command is the e-mail name, and the second occurrence is the password you created for that account.
•
The second command selects the INBOX folder.
•
The third command lists all the headers in the current folder.
54 Confidential and Proprietary, © Software.com, Inc. 2000
Post-Installation Tasks
•
The fourth command lists all the folder names.
•
The fifth command fetches the first message in the current folder.
Sending Mail from a Non-MTA Host
To send mail from a host that is not running an MTA server, install and configure the
InterMail sendmail
program as follows (replace the text in angle brackets with the appropriate site-specific information): su cd /usr/lib mv sendmail sendmail.original
cd $INTERMAIL/bin cp sendmail /usr/lib cat > /etc/sendmail.conf <<EOF
SmartHost=<mta-host>
DomainName=<domain-name>
EOF
Note:
The above example assumes that the original sendmail
program is in
/usr/lib
.
Using the EMANATE Utilities in SNMP
To use the EMANATE utilities, such as getbulk
, in SNMP mode you must create a
~imail/snmp/mgr.cnf
file for your installation. This file is customer-specific and does not affect third-party SNMP clients. Enter the man mgrcnf
command from your
InterMail user account to view a man page for this file.
Confidential and Proprietary, © Software.com, Inc. 2000 55
InterMail Mx Installation Guide
56 Confidential and Proprietary, © Software.com, Inc. 2000
A
License Information
This appendix contains license information related to InterMail Mx.
InterMail Licensing Agreement
THIS SOFTWARE IS PROVIDED “AS IS” AND ANY EXPRESS OR IMPLIED WARRANTIES,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY
AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL
SOFTWARE.COM BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEM-
PLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCURE-
MENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR
BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
EMANATE
InterMail incorporates the EMANATE server as part of its monitoring functionality. Software.com licenses EMANATE pursuant to a license agreement with SNMP Research International, Incorporated.
The copying and distribution of EMANATE is with the permission of SNMP Research International,
Incorporated.
GNU General Public License
Version 2, June 1991
Copyright (C) 1991 Free Software Foundation, Inc.
59 Temple Place - Suite 330, Boston, MA 02111-1307, USA
Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.
[This is the first released version of the library GPL. It is numbered 2 because it goes with version 2 of the ordinary GPL.]
Preamble
The licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU General Public Licenses are intended to guarantee your freedom to share and change free software--to make sure the software is free for all its users.
Confidential and Proprietary, © Software.com, Inc. 2000 57
InterMail Mx Installation Guide
This license, the Library General Public License, applies to some specially designated Free Software
Foundation software, and to any other libraries whose authors decide to use it. You can use it for your libraries, too.
When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for this service if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs; and that you know you can do these things.
To protect your rights, we need to make restrictions that forbid anyone to deny you these rights or to ask you to surrender the rights. These restrictions translate to certain responsibilities for you if you distribute copies of the library, or if you modify it.
For example, if you distribute copies of the library, whether gratis or for a fee, you must give the recipients all the rights that we gave you. You must make sure that they, too, receive or can get the source code.
If you link a program with the library, you must provide complete object files to the recipients so that they can relink them with the library, after making changes to the library and recompiling it. And you must show them these terms so they know their rights.
Our method of protecting your rights has two steps: (1) copyright the library, and (2) offer you this license which gives you legal permission to copy, distribute and/or modify the library.
Also, for each distributor’s protection, we want to make certain that everyone understands that there is no warranty for this free library. If the library is modified by someone else and passed on, we want its recipients to know that what they have is not the original version, so that any problems introduced by others will not reflect on the original authors’ reputations.
Finally, any free program is threatened constantly by software patents. We wish to avoid the danger that companies distributing free software will individually obtain patent licenses, thus in effect transforming the program into proprietary software. To prevent this, we have made it clear that any patent must be licensed for everyone’s free use or not licensed at all.
Most GNU software, including some libraries, is covered by the ordinary GNU General Public License, which was designed for utility programs. This license, the GNU Library General Public License, applies to certain designated libraries. This license is quite different from the ordinary one; be sure to read it in full, and don’t assume that anything in it is the same as in the ordinary license.
The reason we have a separate public license for some libraries is that they blur the distinction we usually make between modifying or adding to a program and simply using it. Linking a program with a library, without changing the library, is in some sense simply using the library, and is analogous to running a utility program or application program. However, in a textual and legal sense, the linked executable is a combined work, a derivative of the original library, and the ordinary General Public License treats it as such.
Because of this blurred distinction, using the ordinary General Public License for libraries did not effectively promote software sharing, because most developers did not use the libraries. We concluded that weaker conditions might promote sharing better.
However, unrestricted linking of non-free programs would deprive the users of those programs of all benefit from the free status of the libraries themselves. This Library General Public License is intended to permit developers of non-free programs to use free libraries, while preserving your freedom as a user of such programs to change the free libraries that are incorporated in them. (We have not seen how to achieve this as regards changes in header files, but we have achieved it as regards changes in the actual functions of the Library.) The hope is that this will lead to faster development of free libraries.
The precise terms and conditions for copying, distribution and modification follow. Pay close attention to the difference between a “work based on the library” and a “work that uses the library”. The former contains code derived from the library, while the latter only works together with the library.
Note that it is possible for a library to be covered by the ordinary General Public License rather than by this special one.
58 Confidential and Proprietary, © Software.com, Inc. 2000
License Information
GNU LIBRARY GENERAL PUBLIC LICENSE
TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
This License Agreement applies to any software library which contains a notice placed by the copyright holder or other authorized party saying it may be distributed under the terms of this Library General Public License (also called “this License”). Each licensee is addressed as “you”.
A “library” means a collection of software functions and/or data prepared so as to be conveniently linked with application programs (which use some of those functions and data) to form executables.
The “Library”, below, refers to any such software library or work which has been distributed under these terms. A “work based on the Library” means either the Library or any derivative work under copyright law: that is to say, a work containing the Library or a portion of it, either verbatim or with modifications and/or translated straightforwardly into another language. (Hereinafter, translation is included without limitation in the term “modification”.)
“Source code” for a work means the preferred form of the work for making modifications to it. For a library, complete source code means all the source code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compilation and installation of the library.
Activities other than copying, distribution and modification are not covered by this License; they are outside its scope. The act of running a program using the Library is not restricted, and output from such a program is covered only if its contents constitute a work based on the Library (independent of the use of the Library in a tool for writing it). Whether that is true depends on what the Library does and what the program that uses the Library does.
1. You may copy and distribute verbatim copies of the Library's complete source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice and disclaimer of warranty; keep intact all the notices that refer to this
License and to the absence of any warranty; and distribute a copy of this License along with the
Library.
You may charge a fee for the physical act of transferring a copy, and you may at your option offer warranty protection in exchange for a fee.
2. You may modify your copy or copies of the Library or any portion of it, thus forming a work based on the Library, and copy and distribute such modifications or work under the terms of Section 1 above, provided that you also meet all of these conditions: a) The modified work must itself be a software library.
b) You must cause the files modified to carry prominent notices stating that you changed the files and the date of any change.
c) You must cause the whole of the work to be licensed at no charge to all third parties under the terms of this License.
d) If a facility in the modified Library refers to a function or a table of data to be supplied by an application program that uses the facility, other than as an argument passed when the facility is invoked, then you must make a good faith effort to ensure that, in the event an application does not supply such function or table, the facility still operates, and performs whatever part of its purpose remains meaningful.
(For example, a function in a library to compute square roots has a purpose that is entirely welldefined independent of the application. Therefore, Subsection 2d requires that any application-supplied function or table used by this function must be optional: if the application does not supply it, the square root function must still compute square roots.)
These requirements apply to the modified work as a whole. If identifiable sections of that work are not derived from the Library, and can be reasonably considered independent and separate works in themselves, then this License, and its terms, do not apply to those sections when you distribute them as separate works. But when you distribute the same sections as part of a whole which is a work based on the Library, the distribution of the whole must be on the terms of this License, whose permissions for other licensees extend to the entire whole, and thus to each and every part regardless of who wrote it.
Confidential and Proprietary, © Software.com, Inc. 2000 59
InterMail Mx Installation Guide
Thus, it is not the intent of this section to claim rights or contest your rights to work written entirely by you; rather, the intent is to exercise the right to control the distribution of derivative or collective works based on the Library.
In addition, mere aggregation of another work not based on the Library with the Library (or with a work based on the Library) on a volume of a storage or distribution medium does not bring the other work under the scope of this License.
3. You may opt to apply the terms of the ordinary GNU General Public License instead of this License to a given copy of the Library. To do this, you must alter all the notices that refer to this License, so that they refer to the ordinary GNU General Public License, version 2, instead of to this License. (If a newer version than version 2 of the ordinary GNU General Public License has appeared, then you can specify that version instead if you wish.) Do not make any other change in these notices.
Once this change is made in a given copy, it is irreversible for that copy, so the ordinary GNU General Public License applies to all subsequent copies and derivative works made from that copy.
This option is useful when you wish to copy part of the code of the Library into a program that is not a library.
4. You may copy and distribute the Library (or a portion or derivative of it, under Section 2) in object code or executable form under the terms of Sections 1 and 2 above provided that you accompany it with the complete corresponding machine-readable source code, which must be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange.
If distribution of object code is made by offering access to copy from a designated place, then offering equivalent access to copy the source code from the same place satisfies the requirement to distribute the source code, even though third parties are not compelled to copy the source along with the object code.
5. A program that contains no derivative of any portion of the Library, but is designed to work with the
Library by being compiled or linked with it, is called a “work that uses the Library”. Such a work, in isolation, is not a derivative work of the Library, and therefore falls outside the scope of this
License.
However, linking a “work that uses the Library” with the Library creates an executable that is a derivative of the Library (because it contains portions of the Library), rather than a “work that uses the library”. The executable is therefore covered by this License. Section 6 states terms for distribution of such executables.
When a “work that uses the Library” uses material from a header file that is part of the Library, the object code for the work may be a derivative work of the Library even though the source code is not. Whether this is true is especially significant if the work can be linked without the Library, or if the work is itself a library. The threshold for this to be true is not precisely defined by law.
If such an object file uses only numerical parameters, data structure layouts and accessors, and small macros and small inline functions (ten lines or less in length), then the use of the object file is unrestricted, regardless of whether it is legally a derivative work. (Executables containing this object code plus portions of the Library will still fall under Section 6.)
Otherwise, if the work is a derivative of the Library, you may distribute the object code for the work under the terms of Section 6. Any executables containing that work also fall under Section 6, whether or not they are linked directly with the Library itself.
6. As an exception to the Sections above, you may also compile or link a “work that uses the Library” with the Library to produce a work containing portions of the Library, and distribute that work under terms of your choice, provided that the terms permit modification of the work for the customer's own use and reverse engineering for debugging such modifications.
You must give prominent notice with each copy of the work that the Library is used in it and that the
Library and its use are covered by this License. You must supply a copy of this License. If the work during execution displays copyright notices, you must include the copyright notice for the
Library among them, as well as a reference directing the user to the copy of this License. Also, you must do one of these things:
60 Confidential and Proprietary, © Software.com, Inc. 2000
License Information
a) Accompany the work with the complete corresponding machine-readable source code for the
Library including whatever changes were used in the work (which must be distributed under
Sections 1 and 2 above); and, if the work is an executable linked with the Library, with the complete machine-readable “work that uses the Library”, as object code and/or source code, so that the user can modify the Library and then relink to produce a modified executable containing the modified Library. (It is understood that the user who changes the contents of definitions files in the Library will not necessarily be able to recompile the application to use the modified definitions.) b) Accompany the work with a written offer, valid for at least three years, to give the same user the materials specified in Subsection 6a, above, for a charge no more than the cost of performing this distribution.
c) If distribution of the work is made by offering access to copy from a designated place, offer equivalent access to copy the above specified materials from the same place.
d) Verify that the user has already received a copy of these materials or that you have already sent this user a copy.
For an executable, the required form of the “work that uses the Library” must include any data and utility programs needed for reproducing the executable from it. However, as a special exception, the source code distributed need not include anything that is normally distributed (in either source or binary form) with the major components (compiler, kernel, and so on) of the operating system on which the executable runs, unless that component itself accompanies the executable.
It may happen that this requirement contradicts the license restrictions of other proprietary libraries that do not normally accompany the operating system. Such a contradiction means you cannot use both them and the Library together in an executable that you distribute.
7. You may place library facilities that are a work based on the Library side-by-side in a single library together with other library facilities not covered by this License, and distribute such a combined library, provided that the separate distribution of the work based on the Library and of the other library facilities is otherwise permitted, and provided that you do these two things: a) Accompany the combined library with a copy of the same work based on the Library, uncombined with any other library facilities. This must be distributed under the terms of the Sections above.
b) Give prominent notice with the combined library of the fact that part of it is a work based on the Library, and explaining where to find the accompanying uncombined form of the same work.
8. You may not copy, modify, sublicense, link with, or distribute the Library except as expressly provided under this License. Any attempt otherwise to copy, modify, sublicense, link with, or distribute the Library is void, and will automatically terminate your rights under this License. However, parties who have received copies, or rights, from you under this License will not have their licenses terminated so long as such parties remain in full compliance.
9. You are not required to accept this License, since you have not signed it. However, nothing else grants you permission to modify or distribute the Library or its derivative works. These actions are prohibited by law if you do not accept this License. Therefore, by modifying or distributing the
Library (or any work based on the Library), you indicate your acceptance of this License to do so, and all its terms and conditions for copying, distributing or modifying the Library or works based on it.
10. Each time you redistribute the Library (or any work based on the Library), the recipient automatically receives a license from the original licensor to copy, distribute, link with or modify the Library subject to these terms and conditions. You may not impose any further restrictions on the recipients' exercise of the rights granted herein.
You are not responsible for enforcing compliance by third parties to this License.
11. If, as a consequence of a court judgment or allegation of patent infringement or for any other reason
(not limited to patent issues), conditions are imposed on you (whether by court order, agreement or
Confidential and Proprietary, © Software.com, Inc. 2000 61
InterMail Mx Installation Guide
otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot distribute so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not distribute the
Library at all. For example, if a patent license would not permit royalty-free redistribution of the
Library by all those who receive copies directly or indirectly through you, then the only way you could satisfy both it and this License would be to refrain entirely from distribution of the Library.
If any portion of this section is held invalid or unenforceable under any particular circumstance, the balance of the section is intended to apply, and the section as a whole is intended to apply in other circumstances.
It is not the purpose of this section to induce you to infringe any patents or other property right claims or to contest validity of any such claims; this section has the sole purpose of protecting the integrity of the free software distribution system which is implemented by public license practices.
Many people have made generous contributions to the wide range of software distributed through that system in reliance on consistent application of that system; it is up to the author/donor to decide if he or she is willing to distribute software through any other system and a licensee cannot impose that choice.
This section is intended to make thoroughly clear what is believed to be a consequence of the rest of this License.
12. If the distribution and/or use of the Library is restricted in certain countries either by patents or by copyrighted interfaces, the original copyright holder who places the Library under this License may add an explicit geographical distribution limitation excluding those countries, so that distribution is permitted only in or among countries not thus excluded. In such case, this License incorporates the limitation as if written in the body of this License.
13. The Free Software Foundation may publish revised and/or new versions of the Library General
Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns.
Each version is given a distinguishing version number. If the Library specifies a version number of this License which applies to it and “any later version”, you have the option of following the terms and conditions either of that version or of any later version published by the Free Software Foundation. If the Library does not specify a license version number, you may choose any version ever published by the Free Software Foundation.
14. If you wish to incorporate parts of the Library into other free programs whose distribution conditions are incompatible with these, write to the author to ask for permission. For software which is copyrighted by the Free Software Foundation, write to the Free Software Foundation; we sometimes make exceptions for this. Our decision will be guided by the two goals of preserving the free status of all derivatives of our free software and of promoting the sharing and reuse of software generally.
NO WARRANTY
BECAUSE THE LIBRARY IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR
THE LIBRARY, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHER-
WISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE
THE LIBRARY “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR
IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANT-
ABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE
QUALITY AND PERFORMANCE OF THE LIBRARY IS WITH YOU. SHOULD THE LIBRARY
PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR
CORRECTION.
IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL
ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDIS-
TRIBUTE THE LIBRARY AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARIS-
62 Confidential and Proprietary, © Software.com, Inc. 2000
License Information
ING OUT OF THE USE OR INABILITY TO USE THE LIBRARY (INCLUDING BUT NOT LIM-
ITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED
BY YOU OR THIRD PARTIES OR A FAILURE OF THE LIBRARY TO OPERATE WITH ANY
OTHER SOFTWARE), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF
THE POSSIBILITY OF SUCH DAMAGES.
Oracle
Oracle Programs are the proprietary products of Oracle and are protected by copyright and other intellectual property laws. Customer acquires only the right to use Oracle Programs and does not acquire any rights, express or implied, in Oracle Programs or media containing Oracle Programs other than those specified by License. Oracle, or its licensor, shall at all times retain all rights, title, interest, including intellectual property rights, in Oracle Programs and media.
The Regents of the University of California Copyright
InterMail includes software that is copyright © 1990, 1993, 1994, The Regents of the University of California. All rights reserved.
This code is derived from software contributed to Berkeley by Mike Olson.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
1. Re-distributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
2. Re-distributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
3. All advertising materials mentioning features or use of this software must display the following acknowledgment: This product includes software developed by the University of California, Berkeley and its contributors.
4. Neither the name of the University nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS’’ AND ANY
EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE FOR
ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAM-
AGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABIL-
ITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF
THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
The Regular Expression Routines
1. Permission is granted to anyone to use this software for any purpose on any computer system, and to alter it and redistribute it, subject to the following restrictions:
2. The author is not responsible for the consequences of use of this software, no matter how awful, even if they arise from flaws in it.
3. The origin of this software must not be misrepresented, either by explicit claim or by omission.
Since few users ever read sources, credits must appear in the documentation.
Confidential and Proprietary, © Software.com, Inc. 2000 63
InterMail Mx Installation Guide
4. Altered versions must be plainly marked as such, and must not be misrepresented as being the original software. Since few users ever read sources, credits must appear in the documentation.
5. This notice may not be removed or altered.
RSA Data Security, Inc. MD5 Message-Digest Algorithm
License to copy and use this software is granted provided that it is identified as the “RSA Data Security,
Inc. MD5 Message-Digest Algorithm” in all material mentioning or referencing this software or this function.
License is also granted to make and use derivative works provided that such works are identified as
“derived from the RSA Data Security, Inc. MD5 Message-Digest Algorithm” in all material mentioning or referencing the derived work.
RSA Data Security, Inc. makes no representations concerning either the merchantability of this software or the suitability of this software for any particular purpose. It is provided “as is” without express or implied warranty of any kind.
These notices must be retained in any copies of any part of this documentation and/or software.
64 Confidential and Proprietary, © Software.com, Inc. 2000
Index
A
access requirements, defining, 6
accounts
administrative accounts, creating, 5
B
backup and recovery procedures, defining, 6
C
change control procedures, defining, 7
Configuration server
InterCore installation and, 25
customer service representatives, defining access for, 6
customer support, preparing for, 7
D
database installation, troubleshooting problems with, 41
databases
Deployment Worksheet
environment variables in, defining, 16, 20, 24
directories, taking snapshots of, 47
Directory Cache server
InterCore installation and, 25
synchronizing with the ISD, 52
Directory server
InterCore installation and, 25
disaster recovery procedures, defining, 7
E
F
failover procedures, defining, 6
H
hosts
installing multiple servers on, 11
non-MTA, sending mail from, 55
I
IMAP server
imorainstall utility, 16, 20, 41
installation commands, windows for, 12
installation output, storing, 13
Confidential and Proprietary, © Software.com, Inc. 2000 65
InterMail Mx Installation Guide
installation problems, troubleshooting, 41
installation tasks
InterCore
in multi-host installations, 12
and Manager server installation, 11
InterMail
creating user’s directory for, 15
creating users and groups for, 14
restarting the installation of, 44
InterMail architecture specification, 2
InterMail environment, checking, 46
InterMail sendmail program, 55
InterMail system, permissions in, 48
ISD (Integrated Services Directory) database
creating, 10 installation tasks for, 10
ISD (Integrated Services Directory), synchronizing the Directory Cache server with,
K
kernel parameters, checking, 4
L
M
Manager server
InterCore installation and, 26
Master Directory Server. See Directory server
message delivery, checking, 52
Message File system, structure of, 48
message retrieval, checking, 53 message storage, checking, 53
Message Store database
creating, order of, 10 installation tasks for, 10
messages, sending from a non-MTA host, 55
monitoring and reporting procedures, defining, 6
MSS (Message Store Server)
MTA (Message Transport Agent)
N
network connectivity, testing, 12
O
operating system, installing, 4
operations staff, identifying, 6
Oracle
creating user’s directory for, 15
creating users and groups for, 13
installation configuration settings for, 38
Oracle database administrator, 3
P
password-file system, local, 13
problems with, identifying, 12
POP server
ports
pre-installation tasks, 1 prerequisites, 1
66 Confidential and Proprietary, © Software.com, Inc. 2000
Q
Queue server
R
reserved accounts, omission of, 43
RFCs, and port assignments, 15
S
semaphores
servers
installing multiple on one host, 11
testing the connectivity of, 12
service attacks, procedures addressing, 6
shared memory
site
SNMP
installation problems with, 41 port conflicts with, 41
Index
SNMP server
InterCore installation and, 26
software development, preparing for, 7
Solaris, port conflicts on, 41
using the Deployment Worksheet, 23
SSL (Secure Socket Layer ) server authentication,
storage devices, setting up, 3
system testing
T
U
W
WebEdge server
Confidential and Proprietary, © Software.com, Inc. 2000 67
Download
Public link updated
The public link to your chat has been updated. You may view and manage your chat links after registration here.
Document public link
Advertisement
Key features
Multiple host installation
Variable number of servers per host
Integrated Services Directory (ISD) database
Message Store database
Configuration server
Directory server
Directory Cache server
SNMP server
Queue server
Message Transport Agent (MTA)
Frequently asked questions
The number of hosts needed for InterMail Mx 5.1 installation is variable, depending on your specific messaging requirements and network architecture.
Before starting the installation, ensure that you have completed the site assessment, defined an InterMail architecture specification, and identified the necessary experts and resources.
You should consult the InterMail Mx Release Notes for specific recommendations, but generally, you might need to increase the maximum shared memory segment and semaphore size.
The installation order includes: completing the Deployment Worksheet, creating the ISD database, creating Message Store databases, installing the Configuration server, then the Directory server, and finally, installing other servers in any order.
When encountering errors, check the installation log files for details, use terminal windows with scrolling capabilities, and capture the output of each installation task for future reference.
