Sun ONE Messaging Server 6.0 Installation Guide for Solaris Operating Systems |
Chapter 5
Performing Post-Installation ProceduresThis chapter describes post-installation procedures you need to perform prior to starting Messaging Server. The following topics are described:
Post-Installation File Directory LayoutAfter you install Sun ONE Messaging Server, its directories and files are arranged in the organization depicted in Table 5-1. The table is not exhaustive; it shows only those directories and files of most interest for typical server administration tasks.
Modifying Your ConfigurationAfter the Messaging Server installation and initial runtime configuration, you may choose to make some additional modifications to your configuration. For detailed information, see the Sun ONE Messaging Server Administrator’s Guide.
Passwords
Because you set up a number of administrators with the same password in Step 10 Password for administrator accounts (See Create the Initial Messaging Server Runtime Configuration), you might want to change the passwords of those administrators.
Refer to Table 5-2, which shows the parameters where default passwords are set up during initial runtime configuration and the utilities you can use to change them. For those parameters that use the configutil utility to change passwords, see the Sun ONE Messaging Server Reference Manual for complete syntax and usage.
The following example uses the local.enduseradmincred configutil parameter to change the password of the end user administrator.
Port Numbers
In the installation and initial runtime configuration programs, port numbers will be chosen for various services. These port numbers can be any number from 1 to 65535.
Table 5-3 lists the port numbers that are designated after installation:
If certain products are installed on the same machine, you will encounter port number conflicts. Table 5-4 shows potential port number conflicts:
If possible, it is recommended that you install products with conflicting port numbers on separate machines. If you are unable to do so, then you will need to change the port number of one of conflicting products.
To change port numbers, use the configutil utility. See the Sun ONE Messaging Server Reference Manual for complete syntax and usage.
The following example uses the service.http.port configutil parameter to change the Messenger Express HTTP port number to 8080.
Managing Messaging Server with Sun ONE ConsoleWhen the messaging server installation process and initial runtime configuration program completes, you can start your Messaging server through the Sun ONE Console. If your directory and messaging server reside on a single machine, you can use the Console interface to manage both servers.
To invoke the console, run the /usr/sbin/mpsconsole command.
For more information on running Messaging Server through the Console, see the Sun ONE Messaging Server Administrator’s Guide and the Sun ONE Messaging Server Administrator’s Online Help which can be invoked through the Console.
SMTP BlockingBy default, Messaging Server is configured to block attempted SMTP relays; that is, it rejects attempted message submissions to external addresses from unauthenticated external sources (external systems are any other system than the host on which the server itself resides). This default configuration is quite aggressive in blocking SMTP relaying in that it considers all other systems to be external systems.
After installation, it is important to manually modify your configuration to match the needs of your site. Specifically, your messaging server should recognize its own internal systems and subnets from which SMTP relaying should always be accepted. If you do not update this configuration, you might encounter problems when testing your MTA configuration.
IMAP and POP clients that attempt to submit messages via the Messaging Server system’s SMTP server destined for external addresses, and who do not authenticate using SMTP AUTH (SASL), will find their submission attempts rejected. Which systems and subnets are recognized as internal is typically controlled by the INTERNAL_IP mapping table, which may be found in the file msg_svr_base/config/mappings.
For instance, on a Messaging Server system whose IP address is 192.45.67.89, the default INTERNAL_IP mapping table would appear as follows:
The initial entry, using the $(IP-pattern/significant-prefix-bits) syntax, is specifying that any IP address that matches the first 24 bits of 192.45.67.89 should match and be considered internal. The second entry recognizes the loopback IP address 127.0.0.1 as internal. The final entry specifies that all other IP addresses should not be considered internal.
You may add additional entries by specifying additional IP addresses or subnets before the final $N entry. These entries must specify an IP address or subnet (using the $(.../...) syntax to specify a subnet) on the left side and $Y on the right side. Or you may modify the existing $(.../...) entry to accept a more general subnet.
For instance, if this same sample site has a class-C network, that is, it owns all of the 192.45.67.0 subnet, then the site would want to modify the initial entry so that the mapping table appears as follows:
Or if the site owns only those IP addresses in the range 192.45.67.80-192.45.67.99, then the site would want to use:
INTERNAL_IP
! Match IP addresses in the range 192.45.67.80-192.45.67.95
$(192.45.67.80/28) $Y
! Match IP addresses in the range 192.45.67.96-192.45.67.99
$(192.45.67.96/30) $Y
127.0.0.1 $Y
* $N
Note that the msg_svr_base/sbin/imsimta test -match utility can be useful for checking whether an IP address matches a particular $(.../...) test condition. The imsimta test -mapping utility can be more generally useful in checking that your INTERNAL_IP mapping table returns the desired results for various IP address inputs.
After modifying your INTERNAL_IP mapping table, be sure to issue the msg_svr_base/sbin/imsimta cnbuild and the msg_svr_base/sbin/imsimta restart utilities so that the changes take effect.
Further information on the mapping file and general mapping table format, as well as information on imsimta command line utilities, can be found in the Sun ONE Messaging Server Reference Manual. In addition, information on the INTERNAL_IP mapping table can be found in the Sun ONE Messaging Server Administrator’s Guide.
Enabling Start-up Across RebootsYou can enable Messaging Server start-up across system reboots by using the bootup script: msg_svr_base/lib/SunONE_MsgSvr. In addition, this script can start up your MMP, if enabled.
To enable SunONE_MsgSvr:
Handling sendmail ClientsIf end users send messages through sendmail clients, you can configure Messaging Server to work with those clients over protocol. Users can continue to use the UNIX sendmail client.
To create compatibility between sendmail clients and Messaging Server, you can create and modify a sendmail configuration file.
Note
Each time a new sendmail patch is applied to your system, you will need to modify the submit.cf file as described in the following instructions for Solaris 8 and Solaris 9.
Solaris 8
On Solaris 8 operating systems, follow these steps:
- Find the file main-v7sun.mc file in directory /usr/lib/mail/cf and create a copy of this file.
In the example in this section, a copy called sunone-msg.mc is created.
- In the sunone-msg.mc file, add the following lines before the MAILER macros:
FEATURE(‘nullclient’, ‘smtp:rhino.west.sesta.com’)dnl
MASQUERADE_AS(‘west.sesta.com’)dnl
define(‘confDOMAIN_NAME’, ‘west.sesta.com’)dnl
Note that rhino.west.sesta.com is the localhost name and west.sesta.com is the default email domain as described in Step 11 Default Email Domain in Create the Initial Messaging Server Runtime Configuration. In an HA environment, use the logical host name. See Chapter 3, "Configuring High Availability Solutions" for more information about logical host names for High Availability.
The sunone-msg.mc will output sunone-msg.cf.
- Make a backup copy of the existing sendmail.cf file located in the /etc/mail directory.
Solaris 9
On Solaris 9 platforms, sendmail is no longer a setuid program. Instead, it is a a setgid program.
To create the sendmail configuration file on Solaris 9 platforms:
- Find the file submit.mc file in directory /usr/lib/mail/cf and create a copy of this file.
In the example in this section, a copy called sunone-submit.mc is created.
to
where rhino.west.sesta.com is the localhost name.
Note that rhino.west.sesta.com is the localhost name and west.sesta.com is the default email domain as described in Step 11 Default Email Domain in Create the Initial Messaging Server Runtime Configuration. In an HA environment, use the logical host name. See Chapter 3, "Configuring High Availability Solutions" for more information about logical host names for High Availability.
The sunone-submit.mc will output sunone-submit.cf.
- Make a backup copy of the existing submit.cf file in /etc/mail directory.
Configuring Messenger Express Mail FiltersTo install the mail filters, follow these steps:
- When you installed Messaging Server (using the directions in Chapter 2, "Installing Messaging Server"), the mail filter package (SUNWmsgmf) was one of many Messaging Server packages that you installed.
Verify that the MailFilter.war file, which implements management of sieve filters, is in the msg_svr_base/SUNWmsgmf directory.
- Be sure that Sun ONE Web Server 6.1 is already installed and configured through the Java Enterprise System installer.
- Set the environment variable IWS_SERVER_HOME to the Web Server installation root directory. For example:
- Issue the following Web Server command:
where web_svr_base is the web server root directory, vs_id is the virtual server ID of the web server, and msg_svr_base is the messaging root directory.
Refer to the Web Server documentation for detailed information on the wdeploy command.
When you have completed installing the mail filters, a MailFilter directory will be placed in the Web Server’s docs directory.
- Use the configutil utility to set the following option:
local.webmail.sieve.port = port
where port is the Web Server port number.
- Stop and restart the HTTP daemon:
Refer to the Sun ONE Messenger Express Customization Guide for mail filter usage information.
- If you want to delete the *.war file in order to install a new version of it, use the following command:
where web_svr_base is the web server root directory and vs_id is the virtual server ID of the web server.
Refer to the Web Server documentation for detailed information on the wdeploy command.