h1. Communications Suite 6 Update 2 Installation Scenario - Message Transfer Agent (MTA)
h2. Assumptions
This scenario shows how to install the Message Transfer Agent (MTA) on a separate host. It is based on the _Install MTA Relay In_ and _Install MTA Relay Out_ leaves in the [Communications Suite 6 Update 2 Installation Flowchart]. The scenario makes these assumptions:
* You are deploying Communications Suite on multiple hosts or Solaris zones.
* This MTA relay in and MTA relay out is one functional component of your multi-host deployment.
* You are installing the MTA on a separate host or Solaris zone; you are not bundling the MTA with other Communication Suite products on the same host.
* If you are distributing multiple instances of the MTA across several hosts or zones, you can follow these instructions for each host on which you install the MTA.
h2. Which Software Components and Downloads Do You Need?
* Communications Suite: for the Messaging Server MTA
Download sites: [Get the Software].
h2. Which Task Sequence Do You Follow?
h4. Before you install the MTA, take these steps:
# You must ensure DNS is running and configured properly. For details, see [DNS configuration|Communications Suite 6 Update 2 Component Products Release Notes#MessagingRequirements].
# Make sure you do not configure conflicting port numbers on a machine when various components are running on a single machine. For a list of port numbers used by Messaging Server, see [Default Port Numbers|Communications Suite 6 Update 2 Component Products Release Notes#GDWUB].
h4. Install and configure the MTA:
# [Run the Communications Suite installer|Communications Suite 6 Update 2 Installation Guide#installcommssuite].\\
\\
When the Comms Installer lists the components to install, choose the 32-bit or 64-bit version by selecting one of these components:\\
\\
Messaging Server 7 Update 2. (The Comms Installer does not explicitly label the 32-bit version as "32-bit.")\\
\\
Messaging Server (64-bit) 7 Update 2\\
\\
Make sure that the other components are not selected.\\
\\
# Use the following worksheet to gather configuration information for the MTA: [Messaging Server 7 Update 2 - Configuration Worksheet|Configuration Worksheets - Messaging Server]\\
# Run the Messaging Server initial configuration program:\\
\\
For 32-bit: {{# _INSTALLROOT_/messaging/bin/configure}}\\
\\
For 64-bit: {{# _INSTALLROOT_/messaging64/bin/configure}}\\
\\
For detailed instructions, see [Messaging Server 7 Update 2: Initial Configuration|Messaging Server 7 Update 2 Initial Configuration].\\
\\
When the Messaging Server {{configure}} program lists the components to configure, select\\
\\
Message Transfer Agent\\
\\
Make sure that the other components are not selected.\\
# Configure the relay for the kind of traffic you are dealing with and the kind of traffic shaping you need. For example, if your inbound relay needs to use LMTP, configure your deployment accordingly.
h2. Assumptions
This scenario shows how to install the Message Transfer Agent (MTA) on a separate host. It is based on the _Install MTA Relay In_ and _Install MTA Relay Out_ leaves in the [Communications Suite 6 Update 2 Installation Flowchart]. The scenario makes these assumptions:
* You are deploying Communications Suite on multiple hosts or Solaris zones.
* This MTA relay in and MTA relay out is one functional component of your multi-host deployment.
* You are installing the MTA on a separate host or Solaris zone; you are not bundling the MTA with other Communication Suite products on the same host.
* If you are distributing multiple instances of the MTA across several hosts or zones, you can follow these instructions for each host on which you install the MTA.
h2. Which Software Components and Downloads Do You Need?
* Communications Suite: for the Messaging Server MTA
Download sites: [Get the Software].
h2. Which Task Sequence Do You Follow?
h4. Before you install the MTA, take these steps:
# You must ensure DNS is running and configured properly. For details, see [DNS configuration|Communications Suite 6 Update 2 Component Products Release Notes#MessagingRequirements].
# Make sure you do not configure conflicting port numbers on a machine when various components are running on a single machine. For a list of port numbers used by Messaging Server, see [Default Port Numbers|Communications Suite 6 Update 2 Component Products Release Notes#GDWUB].
h4. Install and configure the MTA:
# [Run the Communications Suite installer|Communications Suite 6 Update 2 Installation Guide#installcommssuite].\\
\\
When the Comms Installer lists the components to install, choose the 32-bit or 64-bit version by selecting one of these components:\\
\\
Messaging Server 7 Update 2. (The Comms Installer does not explicitly label the 32-bit version as "32-bit.")\\
\\
Messaging Server (64-bit) 7 Update 2\\
\\
Make sure that the other components are not selected.\\
\\
# Use the following worksheet to gather configuration information for the MTA: [Messaging Server 7 Update 2 - Configuration Worksheet|Configuration Worksheets - Messaging Server]\\
# Run the Messaging Server initial configuration program:\\
\\
For 32-bit: {{# _INSTALLROOT_/messaging/bin/configure}}\\
\\
For 64-bit: {{# _INSTALLROOT_/messaging64/bin/configure}}\\
\\
For detailed instructions, see [Messaging Server 7 Update 2: Initial Configuration|Messaging Server 7 Update 2 Initial Configuration].\\
\\
When the Messaging Server {{configure}} program lists the components to configure, select\\
\\
Message Transfer Agent\\
\\
Make sure that the other components are not selected.\\
# Configure the relay for the kind of traffic you are dealing with and the kind of traffic shaping you need. For example, if your inbound relay needs to use LMTP, configure your deployment accordingly.