Changing The Link Protocol Between Domains - Novell GROUPWISE 7 - MESSAGE TRANSFERT AGENT Manual

ConsoleOne Properties Pages and
Settings
Certificate File
SSL Key File
Password
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
on page

41.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
for Direct Links," on page
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.
618 GroupWise 7 Administration Guide
683.
141.
"Using TCP/IP Links between Domains" on page 618
"Using Mapped or UNC Links between Domains" on page 621
"Using Gateway Links between Domains" on page 622
"Configuring the MTA for TCP/IP" on page 618
"Changing the Link Protocol between Domains to TCP/IP" on page 620
Corresponding Tasks and Startup Switches
See Section 41.2.3, "Securing the Domain with SSL Connections
to the MTA," on page 629.
See also /certfile, /keyfile
Chapter 44, "Using MTA Startup Switches,"
and /keypassword.
Section 10.1.3, "Link Protocols