42.1 Performing Basic MTA Configuration

MTA configuration information is stored as properties of its MTA object in eDirectory. The following topics help you modify the MTA object in ConsoleOne and change MTA configuration to meet changing system configurations:

42.1.1 Creating an MTA Object in eDirectory

When you create a new domain, an MTA object is automatically created for it. If the original MTA object for a domain is accidently deleted, you can create a new one for it. Do not attempt to create more than one MTA object for a domain.

To create a new MTA object in Novell eDirectory:

  1. In ConsoleOne, browse to and right-click the Domain object for which you need to create an MTA object, then click New.

  2. Double-click GroupWise Agent to display the Create GroupWise Agent dialog box.

    Create GroupWise Agent dialog box

  3. Type a unique name for the new MTA. The name can include as many as 8 characters. Do not use any of the following invalid characters in the name:

    ASCII characters 0-31

    Comma ,

    Asterisk *

    Double quote "

    At sign @

    Extended ASCII characters that are graphical or typographical symbols; accented characters in the extended range can be used

    Backslash \

    Parentheses ( )

    Braces { }

    Period .

    Colon :

    Slash /

    The Type field is automatically set to Message Transfer.

  4. Select Define Additional Properties.

  5. Click OK.

    The MTA object is automatically placed within the Domain object.

  6. Review the information displayed for the first four fields on the Identification page to ensure that you are creating the correct type of Agent object in the correct location.

    MTA Identification property page

  7. In the Description field, type one or more lines of text describing the MTA. This description displays on the MTA server console as the MTA runs.

    If multiple administrators work at the server where the MTA will run, the description includes a note about who to contact before stopping the MTA. When running multiple MTAs on the same server, the description should uniquely identify each one. See Section 43.0, Monitoring the MTA.

  8. In the Platform field, select the platform (Linux or Windows) where the MTA will run.

  9. Continue with Section 42.1.2, Configuring the MTA in ConsoleOne.

42.1.2 Configuring the MTA in ConsoleOne

The advantage to configuring the MTA in ConsoleOne, as opposed to using startup switches in an MTA startup file, is that the MTA configuration settings are stored in eDirectory.

  1. In ConsoleOne, expand the eDirectory container where the Domain object is located.

  2. Expand the Domain object.

  3. Right-click the MTA object, then click Properties.

    MTA properties page

The table below summarizes the MTA configuration settings in the MTA object properties pages and how they correspond to MTA startup switches (as described in Section 45.0, Using MTA Startup Switches):

ConsoleOne Properties Pages and Settings

Corresponding Tasks and Startup Switches

Information Page

 
  • Domain
  • Distinguished Name
  • Name
  • Agent Type
  • Description
  • Platform

See Section 42.1.1, Creating an MTA Object in eDirectory.

Agent Settings Page

 
  • Scan Cycle
  • Scan High

See Section 44.2.2, Adjusting MTA Polling of Input Queues in the Domain, Post Offices, and Gateways.

See also ‑‑cyhi and ‑‑cylo.

  • Attach Retry

See Section 44.4, Adjusting MTA Polling of Closed Locations.
  • Enable Automatic Database Recovery

See ‑‑norecover.
  • Use 2nd High Priority Scanner
  • Use 2nd Mail Priority Scanner

See Section 44.2.3, Adjusting the Number of MTA Scanner Threads for the Domain and Post Offices.

See also ‑‑fast0 and ‑‑fast4.

  • SNMP Community "Get" String

See Section 43.6, Using an SNMP Management Console.
  • HTTP User Name
  • HTTP Password

See Section 43.2.1, Setting Up the MTA Web Console.

See also ‑‑httpuser and ‑‑httppassword.

Network Address Page

 
  • TCP/IP Address

See Using TCP/IP Links between Domains and Using TCP/IP Links between a Domain and its Post Offices.

See also ‑‑ip and ‑‑tcpport.
  • Bind Exclusively to TCP/IP Address

See Section 42.1.5, Binding the MTA to a Specific IP Address.

See also ‑‑ip.
  • Message Transfer

See Using TCP/IP Links between Domains.

See also ‑‑msgtranssl.
  • HTTP

See Section 43.2.1, Setting Up the MTA Web Console.

See also ‑‑httpssl.

Log Settings Page

 
  • Log File Path
  • Logging Level
  • Max Log File Age
  • Max Log Disk Space

See Section 43.3, Using MTA Log Files.

See also ‑‑log, ‑‑logdays, ‑‑logdiskoff, ‑‑loglevel, and ‑‑logmax.

Message Log Settings Page

 
  • Message Logging Level
  • Message Log File Path

See Section 42.4.2, Enabling MTA Message Logging.

See also ‑‑messagelogsettings, ‑‑messagelogpath, ‑‑messagelogdays, and ‑‑messagelogmaxsize.

Scheduled Events Page

 
  • eDirectory User Synchronization      Event

See Section 42.4.1, Using eDirectory User Synchronization.

See also ‑‑nondssync.

Routing Options Page

 
  • Default Routing Domain
  • Force All Messages to Default Routing Domain

See Section 42.3.1, Using Routing Domains.

See also ‑‑defaultroutingdomain.
  • Allow MTA to Send Directly to Other GroupWise Systems

See Using Dynamic Internet Links in Connecting to Other GroupWise Systems in the GroupWise 2012 Multi-System Administration Guide.

See also ‑‑nodns.

MTA SSL Settings Page

 
  • Certificate File
  • SSL Key File
  • Password

See Section 42.2.2, Securing the Domain with SSL Connections to the MTA.

See also ‑‑certfile, ‑‑keyfile and ‑‑keypassword.

After you install the MTA software, you can further configure the MTA using a startup file. To survey the many ways the MTA can be configured, see Section 45.0, Using MTA Startup Switches.

42.1.3 Changing the Link Protocol between Domains

How MTAs for different domains communicate with each other is determined by the link protocol in use between the domains. Typically, inbound and outbound links for a domain use the same link protocol, but this is not required. For a review of link protocols, see Section 10.1.3, Link Protocols for Direct Links.

If you originally set up an MTA using one link protocol and need to change to a different one, some reconfiguration of the MTA is necessary.

NOTE:The Linux MTA does not support mapped or UNC links between domains. TCP/IP links are required.

Using TCP/IP Links between Domains

To set up TCP/IP links between domains, you must perform the following two tasks:

Configuring the MTA for TCP/IP

  1. Make sure TCP/IP is properly set up on the server where the MTA is running.

  2. In ConsoleOne, browse to and right-click the MTA object, then click Properties.

  3. Click GroupWise > Network Address to display the Network Address page.

    MTA Network Address page

  4. On the Network Address page, click the pencil icon for the TCP/IP Address field to display the Edit Network Address dialog box.

    Edit Network Address dialog box

  5. Select IP Address, then provide the IP address, in dotted decimal format, of the server where the MTA is running.

    or

    Select DNS Host Name, then provide the DNS hostname of the server where the MTA is running.

    IMPORTANT:The MTA must run on a server that has a static IP address. DHCP cannot be used to dynamically assign an IP address for it.

    Specifying the DNS hostname rather than the IP address makes it easier to move the MTA from one server to another, should the need arise at a later time. You can assign a new IP address to the hostname in DNS, without changing the MTA configuration information in ConsoleOne.

  6. Click OK.

  7. To use a TCP port number other than the default port of 7100, type the port number in the Message Transfer Port field.

    If multiple MTAs will run on the same server, each MTA must have a unique TCP port number.

  8. For optimum security, select Enabled in the SSL drop-down list for the message transfer port. For more information, see Section 42.2.2, Securing the Domain with SSL Connections to the MTA.

  9. Click OK to save the network address and return to the main ConsoleOne window.

    ConsoleOne then notifies the MTA to restart enabled for TCP/IP.

Corresponding Startup Switches: You can also use the ‑‑ip and ‑‑tcpport switches in the MTA startup file to provide the IP address and the message transfer port number.

MTA Web Console: You can view the MTA TCP/IP information on the Configuration page under the TCP/IP Settings heading.

Changing the Link Protocol between Domains to TCP/IP

Make sure you have configured the MTA for TCP/IP at both ends of each link.

To change the link between the domains from mapped or UNC to TCP/IP:

  1. In ConsoleOne, click Tools > GroupWise Utilities > Link Configuration.

  2. Click View > Domain Links to display domain links.

    Link Configuration tool window

  3. Select the MTA’s local domain in the drop-down list.

    Outbound and inbound links for the selected domain are listed.

  4. Double-click a domain in the Outbound Links list.

    Edit Domain Links dialog box

  5. Set Link Type to Direct.

  6. Set Protocol to TCP/IP.

    Make sure the information displayed in the IP Address and MT Port fields matches the information for the MTA for the domain to which you are linking.

  7. Click OK.

  8. Repeat Step 4 through Step 7 for each domain in the Outbound Links list where you want the MTA to use a TCP/IP link.

    Selecting multiple domains is also allowed.

  9. Double-click a domain in the Inbound Links list.

  10. Set Link Type to Direct.

  11. Set Protocol to TCP/IP.

    Make sure the information displayed in the IP Address and MT Port fields matches the information you supplied in Configuring the MTA for TCP/IP.

  12. Click OK.

  13. Repeat Step 9 through Step 12 for each domain in the Inbound Links list where you want the MTA to use a TCP/IP link.

    Selecting multiple domains is also allowed.

  14. Click File > Exit > Yes to save the link changes.

    ConsoleOne then notifies the MTA to restart with the new link configuration.

For a sample message flow for this configuration, see TCP/IP Link Open: Transfer between Domains Successful in Message Delivery to a Different Domain in GroupWise 2012 Troubleshooting 3: Message Flow and Directory Structure.

Using Mapped or UNC Links between Domains

To change to a mapped or UNC link between domains:

  1. In ConsoleOne, click Tools > GroupWise Utilities > Link Configuration.

  2. Click View > Domain Links to display domain links.

  3. Select the MTA’s local domain in the drop-down list.

    Outbound and inbound links for the selected domain are listed.

  4. Double-click a domain in the Outbound Links list.

  5. Set Link Type to Direct.

  6. Set Protocol to Mapped or UNC.

  7. Enter the full path, in the appropriate format, of the directory where the other domain is located.

  8. Click OK.

  9. Repeat Step 4 through Step 8 for each domain in the Outbound Links list where you want the MTA to use a mapped or UNC link.

    Selecting multiple domains is also allowed.

  10. Double-click a domain in the Inbound Links list.

  11. Set Link Type to Direct.

  12. Set Protocol to Mapped or UNC.

  13. Enter the full path, in the appropriate format, of the directory where the local domain is located.

  14. Click OK.

  15. Repeat Step 10 through Step 14 for each domain in the Inbound Links list where you want the MTA to use a mapped link.

    Selecting multiple domains is also allowed.

  16. Click File > Exit > Yes to save the link changes.

    ConsoleOne then notifies the MTA to restart with the new link configuration.

Using Gateway Links between Domains

You can use GroupWise gateways to link domains within your GroupWise system.

Using the Async Gateway to Link Domains

You can use the Async Gateway to link a domain into your GroupWise system using a modem. For setup instructions, see the Async Gateway documentation at the GroupWise Gateway Documentation Web site.

NOTE:GroupWise gateways such as the Async Gateway are legacy products that are not supported with the current GroupWise version.

Using the Internet Agent to Link Domains

You can use the Internet Agent (GWIA) to link a domain into your GroupWise system across the Internet. When you use the GWIA as the transport mechanism between domains, it encapsulates GroupWise messages (both email messages and administrative messages) within SMTP messages in order to transport them across the Internet. For setup instructions, see Section 58.2, Linking Domains

NOTE:A simpler alternative to a gateway link for spanning the Internet is to use MTA to MTA links, as described for linking separate GroupWise systems in Using Dynamic Internet Links in the GroupWise 2012 Multi-System Administration Guide. The same configuration that can link two separate GroupWise systems can be employed to link a domain within the same GroupWise system.

42.1.4 Changing the Link Protocol between a Domain and Its Post Offices

How messages are transferred between the MTA for the domain and the POA for each post office is determined by the link protocol in use between the domain and each post office. For a review of link protocols, see Section 10.1.3, Link Protocols for Direct Links.

If you need to change from one link protocol to another, some reconfiguration of the MTA and its link to each post office is necessary.

NOTE:The Linux MTA requires TCP/IP links between a domain and its post offices.

Using TCP/IP Links between a Domain and its Post Offices

To change from mapped or UNC links to TCP/IP links between a domain and its post offices, you must perform the following two tasks:

Configuring the Agents for TCP/IP

  1. If the MTA for the domain is not yet set up for TCP/IP communication, see Configuring the MTA for TCP/IP.

  2. If any post offices do not yet have a POA set up for TCP/IP communication, see Section 36.2.1, Using Client/Server Access to the Post Office to set up the initial TCP/IP information.

  3. In ConsoleOne, expand the Post Office object to display the POA object(s) in the post office.

    Only one POA per post office needs to communicate with the MTA. If the post office has multiple POAs, have a POA that performs message file processing communicate with the MTA for best performance. For information about message file processing, see Section 35.5, Role of the Post Office Agent.

  4. Right-click the POA object, then click Properties.

  5. Click GroupWise > Network Address to display the Network Address page.

    POA Network Address property page

  6. On the Network Address page, click the pencil icon for the TCP/IP Address field to display the Edit Network Address dialog box.

    Edit Network Address dialog box

  7. In the Message Transfer Port field, specify a unique TCP port on which the POA will listen for incoming messages from the MTA.

    The default is 7101.

  8. For optimum security, select Enabled in the SSL drop-down list for the message transfer port. For more information, see Section 42.2.2, Securing the Domain with SSL Connections to the MTA.

  9. Click OK to save the TCP/IP information and return to the main ConsoleOne window.

    ConsoleOne then notifies the POA to restart with message transfer processing enabled.

Changing the Link Protocol between a Domain and its Post Offices to TCP/IP

  1. In ConsoleOne, click Tools > GroupWise Utilities > Link Configuration.

    Link Configuration tool window

  2. In the drop-down list, select the domain where you want TCP/IP links to post offices.

  3. Click View > Post Office Links to display post office links.

    Link Configuration tool with post office links displayed

  4. Double-click a Post Office object.

  5. In the Protocol field, select TCP/IP.

    Edit Post Office Link dialog box

  6. Make sure the information displayed in the Edit Post Office Link dialog box matches the information provided in the Edit Network Address dialog box in Configuring the Agents for TCP/IP.

  7. Click OK.

  8. Repeat Step 4 through Step 7 for each post office in the domain where you want to use TCP/IP links.

  9. To exit the Link Configuration tool and save your changes, click File > Exit > Yes.

    ConsoleOne then notifies the MTA and POAs to restart using the new link protocol.

For a sample message flow for this configuration, see TCP/IP Link Open: Transfer between Post Offices Successful in Message Delivery to a Different Post Office in GroupWise 2012 Troubleshooting 3: Message Flow and Directory Structure.

Using Mapped or UNC Links between a Domain and its Post Offices

To change from a TCP/IP link to a mapped or UNC link between a domain and its post offices:

  1. In ConsoleOne, click Tools > GroupWise Utilities > Link Configuration.

  2. In the drop-down list, select the domain where the post offices reside.

  3. Click View Post Office Links to display post office links.

  4. Double-click a Post Office object.

  5. In the Protocol field, select Mapped or UNC.

  6. Provide the location of the post office in the format appropriate to the selected protocol.

  7. Click OK.

  8. Repeat Step 4 through Step 7 for each post office in the domain.

  9. To exit the Link Configuration tool and save your changes, click File > Exit > Yes.

    ConsoleOne then notifies the POA and MTA to restart using the new link protocol.

42.1.5 Binding the MTA to a Specific IP Address

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.

  1. In ConsoleOne, expand the Domain object to display the MTA object in the post office.

  2. Right-click the MTA object, then click Properties.

  3. Click GroupWise > Network Address to display the Network Address page.

  4. If the TCP/IP Address field does not yet display the IP address you want the MTA to use:

    1. Click the pencil icon for the TCP/IP Address field to display the Edit Network Address dialog box.

    2. Specify the IP address for the MTA, then click OK.

  5. Select Bind Exclusively to TCP/IP Address, then click OK to save the IP address setting.

Corresponding Startup Switches: You can also use the ‑‑ip switch in the MTA startup file to bind the MTA to a specific IP address.

42.1.6 Moving the MTA to a Different Server

As your GroupWise system grows and evolves, you might need to move an MTA from one server to another. For example, you might decide to run the MTA on a different platform, or perhaps you want to move it to a server that has more disk space for the mslocal directory.

  1. Stop the existing MTA.

  2. Copy the entire mslocal subdirectory structure to wherever you want it on the new server. It might contain messages that have not yet been delivered.

  3. When moving the MTA, pay special attention to the following details:

    • In the MTA startup file, set the ‑‑work switch to the location of the mslocal directory on the new server.

    • If the original MTA was configured for TCP/IP links between domains, you must reconfigure the MTA object with the IP address and port number for the MTA on the new server. See Using TCP/IP Links between Domains.

  4. Install the MTA on the new server. See Installing GroupWise Agents in the GroupWise 2012 Installation Guide.

  5. Start the new MTA, as described in the following sections in the GroupWise 2012 Installation Guide:

  6. Observe the new MTA to see that it is running smoothly. See Section 43.0, Monitoring the MTA.

  7. If you are no longer using the old server for any GroupWise agents, you can remove the agents to reclaim the disk space, as described in the following sections in the GroupWise 2012 Installation Guide:

42.1.7 Adjusting the MTA for a New Location of a Domain or Post Office

The MTA configuration must be adjusted if you make the following changes to your GroupWise system configuration:

New Domain Location

If you move a domain from one server to another, you need to edit the MTA startup file to provide the new location of the domain directory.

  1. Stop the MTA for the old domain location if it is still running.

  2. Use an ASCII text editor to edit the MTA startup file.

    Windows:

    Only the first 8 characters of the domain name are used in the file name. The startup file is typically located in the directory where the MTA software is installed.

    Linux:

    The full domain name is used in the file name. However, all letters are lowercase and any spaces in the domain name are removed. The startup file is located in the /opt/novell/groupwise/agents/share directory.

  3. Adjust the setting of the ‑‑home switch to point to the new location of the domain directory.

  4. Save the MTA startup file.

  5. Start the MTA for the new domain location, as described in the following sections in the GroupWise 2012 Installation Guide:

New Post Office Location

If you move a post office, you need to adjust the link information for that post office.

  1. Click Tools > GroupWise Utilities > Link Configuration.

  2. In the drop-down list, select the domain where a post office has moved.

  3. Click View > Post Office Links to display post office links.

  4. Double-click the post office that has been moved.

  5. Provide its new location in the appropriate format.

  6. Click OK.

  7. Click File > Exit > Yes to save the link changes.

    ConsoleOne then notifies the MTA to restart with the new link configuration.

42.1.8 Adjusting the MTA Logging Level and Other Log Settings

When you are installing or troubleshooting the MTA, a logging level of Verbose can be useful. However, when the MTA is running smoothly, you can set the logging level down to Normal to conserve disk space occupied by log files. See Section 43.3, Using MTA Log Files.