This information describes the schema and provisioning options for Messaging Server. Because of the complexity in provisioning Messaging Server, you need to understand your options before installing the product.

The configure program prompts you to enter host IP addresses that are allowed as SMTP relay hosts. The configure program uses this information to construct the appropriate mapping entries.

By default, Messaging Server is configured to block attempted SMTP relays. That is, Messaging Server 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.

IMAP and POP clients that attempt to submit messages by using Messaging Server system's SMTP server destined for external addresses, and which do not authenticate using SMTP AUTH (SASL), find their submission attempts rejected. Which systems and subnets are recognized as internal is typically controlled by the INTERNAL_IP mapping table. In Unified Configuration, this mapping table is part of the overall configuration, and is viewed or edited by using the msconfig command. In legacy configuration, this mapping table is found in the MessagingServer_home/config/mapping file.

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:

INTERNAL_IP

  $(192.45.67.89/32) $Y
  127.0.0.1 $Y
  * $N

The initial entry, using the S (IP-pattern/significant-prefix-bits) syntax, is specifying that any IP address that matches the full 32 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 can 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 can 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:

INTERNAL_IP
$ (192.45.67.0/24) $Y
127.0.0.1 SY
* $N

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

The MessagingServer_home/bin/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 MessagingServer_home/bin/imsimta cnbuild (if you are using a compiled configuration) and the MessagingServer_home/bin/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 Messaging Server System Administrator's Guide. In addition, information on the INTERNAL_IP mapping table can be found in the Messaging Server System Administrator's Guide.

You can enable Messaging Server startup after system reboots by using the bootup script. On Linux, this script is MessagingServer_home/data/install/Sun_MsgSvr. For Solaris OS 10, you should use the Service Management Framework. That is, by default, Messaging Server is not restarted after a system reboot unless you run this script. In addition, this script can also start up your MMP, if enabled.

For information on performance and tuning considerations for Messaging Server, see "Performance Tuning Considerations for a Messaging Server Architecture".

After installing Messaging Server, its directories and files are arranged in the organization described in Table 12-3. The table shows only those directories and files of most interest for typical server administration tasks.

In the installation and initial runtime configuration programs, port numbers are chosen for various services. These port numbers can range from 1 to 65535. Select numbers that do not conflict with port numbers used by enabled system services or other third-party software. The authoritative list of registered port numbers is available at http://www.iana.org. The /ect/services also lists a subset of these numbers.

Table 12-4 lists the port numbers that are designated after installation. See Messaging Server Reference for more information on the port numbers.

Messaging Server can use Oracle GlassFish Message Queue, a standards-based messaging service, to send event notifications. Message Queue is provided as a shared component when you install Messaging Server or other Communications Suite products.

For more information, see the discussion on integrating JMQ and Messaging Server in the Messaging Server System Administrator's Guide.

Messaging Server supports client certificate authentication. For more information, see the discussion on certificate based authentication for Messaging Server in the Messaging Server Security Guide.