MTA configuration information is stored as properties of its MTA object. The following topics help you modify the MTA object in the GroupWise Admin console and change MTA configuration to meet changing system configurations:
The initial MTA object is automatically created when you create a new domain. You can have only one MTA for a domain. You cannot create an MTA object in the GroupWise Admin console unless the original MTA object is accidentally deleted.
The advantage to configuring the MTA in the GroupWise Admin console, as opposed to using startup switches in an MTA startup file, is that the settings can be easily edited from any location where the Admin console is available.
In the GroupWise Admin console, browse to and click the MTA.
For information about each tab and field, click Help.
The context-sensitive help topics link to the related sections of this guide, where you can determine which MTA startup switch corresponds to each MTA setting in the GroupWise Admin console. Some MTA configuration can be done only using a startup file. For more information, see in Section 26.0, Using MTA Startup Switches.
If the MTA runs on a server that has multiple IP addresses, you can cause the MTA to bind to a specific IP address. The specified IP address is associated with all ports used by the MTA. Without an exclusive bind, the MTA binds to all IP addresses available on the server.
IMPORTANT:If you bind the MTA (or POA) to a specific IP address, the Admin Service is also bound to that IP address.
In the GroupWise Admin console, browse to and click the MTA.
Click the Agent Settings tab, and locate the Network Address section.
Select Bind Exclusively to TCP/IP Address.
Click Save, then click Close to return to the main Admin console window.
HINT:To determine from the command line whether an MTA is bound to a specific IP address, use the following command:
gwadminutil dbinfo /path_to_domain
If an IP address is listed, the MTA is bound to that address. If 0.0.0.0 displays, the MTA is not bound to any IP address.
Corresponding Startup Switches: You can also use the ‑‑ip switch in the MTA startup file to bind the MTA to a specific IP address.
Message logging is turned off by default, because it causes the MTA to use additional CPU and disk resources. However, gathering information about message traffic on your GroupWise system lets you perform many valuable tasks, including:
Tracking messages
Gathering statistics to help optimize your GroupWise system
Billing customers for messages delivered
Tracking messages from the MTA console and from GroupWise Monitor
When you enable MTA message logging, the MTA stores data about GroupWise message traffic as it processes messages. The stored data is then available for use by the MTA console Message Tracking option and by the GroupWise Monitor Message Tracking Report option. In addition, third-party programs can produce customized billing, tracking, and statistical reports based on the information stored in the database.
To enable MTA message logging:
In the GroupWise Admin console, browse to and click the MTA.
Click the Log Settings tab.
In the Message Logging field, select a logging level to turn message logging on.
In the Message Log Path field, specify the full path of the file where the MTA will record the logging information.
Select the types of information you want to track:
Correlate Delivery Status Reports: Select this option to maintain the relationship between user messages and their corresponding delivery status reports in the logged information.
Collect Delivery Status Reports: Select this option to log delivery status reports as well as user messages.
Collect Other Status Reports: Select this option to log user-requested information about messages sent, such as indicating that messages have been opened or deleted by the recipients.
Track Administrative Messages: Select this option to log administrative messages such as database updates.
In the Delete Reports After field, specify the number of days to retain reports on disk. Reports are automatically deleted after the specified time has passed.
Click Save, then click Close to return to the main Admin console window.
For instructions about using the data that the MTA collects, see Tracking Messages and Section 85.3.7, Message Tracking Report.
Corresponding Startup Switches: You can also use the ‑‑messagelogsettings, ‑‑messagelogpath, ‑‑messagelogdays, and ‑‑messagelogmaxsize switches in the MTA startup file to configure MTA message logging.