Novell GROUPWISE 7 - MESSAGE TRANSFERT AGENT User manual

Message Transfer Agent
X
novdocx (en) 11 December 2007
603
X
Message Transfer Agent
Chapter 40, “Understanding Message Transfer between Domains and Post Offices,” on
page 605
Chapter 41, “Configuring the MTA,” on page 613
Chapter 42, “Monitoring the MTA,” on page 645
Chapter 43, “Optimizing the MTA,” on page 675
Chapter 44, “Using MTA Startup Switches,” on page 683

604 GroupWise 7 Administration Guide
novdocx (en) 11 December 2007

Understanding Message Transfer between Domains and Post Offices
40
novdocx (en) 11 December 2007
605
40
Understanding Message Transfer
between Domains and Post
Offices
A domain organizes post offices into a logical grouping for addressing, routing, and administration
purposes in your GroupWise®system. Messages are transferred between post offices and domains
by the Message Transfer Agent (MTA). The following topics help you understand domains and the
functions of the MTA:
Section 40.1, “Domain Representation in ConsoleOne,” on page 605
Section 40.2, “Domain Directory Structure,” on page 606
Section 40.3, “Information Stored in the Domain,” on page 606
Section 40.4, “Role of the Message Transfer Agent,” on page 608
Section 40.5, “Link Configuration between Domains and Post Offices,” on page 608
Section 40.6, “Message Flow between Domains and Post Offices,” on page 608
Section 40.7, “Cross-Platform Issues between Domains and Post Offices,” on page 609
40.1 Domain Representation in ConsoleOne
In ConsoleOne®, domains are container objects that contain an MTA object, as well as other
domain-related objects, as shown below:
Figure 40-1 ConsoleOne View Showing the MTA Object
Although each post office is linked to a domain, it does not display as subordinate to the domain in
the Console View. However, using the GroupWise View, you can display post offices as subordinate
to the domains to which they are linked in your GroupWise system.

606 GroupWise 7 Administration Guide
novdocx (en) 11 December 2007
Figure 40-2 GroupWise View Showing Post Offices in Relationship to Domains
40.2 Domain Directory Structure
Physically, a domain consists of a set of directories that house all the information stored in the
domain. See “Domain Directory” in GroupWise 7 Troubleshooting 3: Message Flow and Directory
Structure.
40.3 Information Stored in the Domain
The following types of information are stored in the domain:
Section 40.3.1, “Domain Database,” on page 606
Section 40.3.2, “Agent Input/Output Queues in the Domain,” on page 607
Section 40.3.3, “Gateways,” on page 607
No messages are stored in the domain, so GroupWise client users do not need access to the domain
directory. The only person who needs file access to the domain directory is the GroupWise
administrator.
40.3.1 Domain Database
The domain database (wpdomain.db) contains all administrative information for the domain,
including:
Address information about all GroupWise objects (such as users, resources, post offices, and
gateways in the domain)
System configuration and linking information for the domain’s MTA
Address and message routing information to other domains
The first domain you create is the primary domain. In the primary domain, the wpdomain.db file
contains all administrative information for your entire GroupWise system (all its domains, post
offices, users, and so on). Because the wpdomain.db file in the primary domain is so crucial, you
should back it up regularly and keep it secure. See Section 31.1, “Backing Up a Domain,” on
page 407.

Understanding Message Transfer between Domains and Post Offices 607
novdocx (en) 11 December 2007
You can re-create your entire GroupWise system from the primary domain wpdomain.db file;
however, if the primary domain wpdomain.db file becomes unusable, you can no longer make
administrative updates to your GroupWise system.
Secondary domains are automatically synchronized to match the primary domain.
40.3.2 Agent Input/Output Queues in the Domain
Each domain contains agent input/output queues where messages are deposited and picked up for
processing by the MTA.
For a mapped or UNC link between domains, the MTA requires read/write access rights to its input/
output queues in the other domains. For a TCP/IP link, no access rights are required because
messages are communicated by way of TCP/IP.
For illustrations of the processes presented below, see Section 40.6, “Message Flow between
Domains and Post Offices,” on page 608.
MTA Input Queue in the Domain
The MTA input queue in the local domain (domain\wpcsin) is where MTAs for other domains
deposit user messages for the local MTA to route to local post offices or to route to other domains.
Thus the MTA input queue in the local domain is the output queue for the MTAs in many other
domains.
The MTA does not have an output queue for user messages in the local domain. Because its primary
task is routing messages, the local MTA has output queues in all post offices in the domain. See
“POA Input Queue in the Post Office” on page 467. The local MTA also has output queues in all
domains to which it is directly linked.
MTA Output Queue in the Domain
The MTA output queue in the local domain (domain\wpcsout\ads) is where the MTA deposits
administrative messages from other domains for the MTA admin thread to pick up.
MTA Admin Thread Input Queue in the Domain
The MTA admin thread input queue (domain\wpcsout\ads) is, of course, the same as the MTA
output queue in the local domain. The MTA admin thread picks up administrative messages
deposited in the queue by the MTA and updates the domain database.
MTA Admin Thread Output Queue in the Domain
The MTA admin thread output queue (domain\wpcsin) is the same as the MTA input queue in
the local domain. The MTA admin thread deposits administrative messages in the queue for
replication to other domains.
40.3.3 Gateways
Gateways are installed and configured at the domain level of your GroupWise system. For a list of
gateways, see the GroupWise Gateways Documentation Web site (http://www.novell.com/
documentation/gwgateways).

608 GroupWise 7 Administration Guide
novdocx (en) 11 December 2007
40.4 Role of the Message Transfer Agent
You must run an MTA for each domain. The MTA:
Routes messages between post offices in the local domain.
Routes messages between domains.
Routes messages to and from gateways installed in the local domain.
Routes messages between GroupWise systems across the Internet if appropriate DNS lookup
capabilities have been set up. See “Using Dynamic Internet Links” in “Connecting to
GroupWise 5.x, 6.x, and 7.x Systems” in the GroupWise 7 Multi-System Administration Guide.
Schedules routing of messages across expensive links. See Section 41.3.2, “Scheduling Direct
Domain Links,” on page 633.
Controls the size of messages that can pass across links. See Section 41.2.1, “Restricting
Message Size between Domains,” on page 628.
Updates the domain database (wpdomain.db) whenever GroupWise users, resources, post
offices, or other GroupWise objects are added, modified, or deleted.
Replicates updates to all domains and post offices throughout your GroupWise system. This
keeps the Address Book up to date for all GroupWise users.
Synchronizes GroupWise user information with Novell®eDirectoryTM user information. This
handles updates made in ConsoleOne without the GroupWise Administrator snap-in running.
See Section 41.4.1, “Using eDirectory User Synchronization,” on page 638.
Synchronizes GroupWise object information throughout your GroupWise system as needed.
Detects and repairs invalid information in the domain database (wpdomain.db).
Provides improved performance for GroupWise Remote client users. See Section 41.2.2,
“Enabling Live Remote,” on page 629.
Provides logging and statistics about GroupWise message flow. See Section 41.4.2, “Enabling
MTA Message Logging,” on page 643.
40.5 Link Configuration between Domains and
Post Offices
In GroupWise, a link is defined as the information required to route messages between domains,
post offices, and gateways in a GroupWise system. Links are created and configured when new
domains, post offices, and gateways are created.
For more specific information about how domains are linked to each other, and about how domains
and post offices are linked, see Chapter 10, “Managing the Links between Domains and Post
Offices,” on page 137.
40.6 Message Flow between Domains and Post
Offices
Section 40.6.1, “Message Flow between Post Offices in the Same Domain,” on page 609
Section 40.6.2, “Message Flow between Different Domains,” on page 609

Understanding Message Transfer between Domains and Post Offices 609
novdocx (en) 11 December 2007
40.6.1 Message Flow between Post Offices in the Same
Domain
To see what happens to message flow within the domain when the domain is closed, view the
following message flow diagrams:
“TCP/IP Link Open: Transfer between Post Offices Successful”
“TCP/IP Link Closed: Transfer between Post Offices Delayed”
These diagrams are found in “Message Delivery to a Different Post Office” in GroupWise 7
Troubleshooting 3: Message Flow and Directory Structure. If you are using mapped/UNC links,
refer to GroupWise 6.5 Troubleshooting 3: Message Flow and Directory Structure.
40.6.2 Message Flow between Different Domains
To see what happens to message flow when the destination domain is closed, view the following
message flow diagrams:
“TCP/IP Link Open: Transfer between Domains Successful”
“TCP/IP Link Closed: Transfer between Domains Delayed”
These diagrams are found in “Message Delivery to a Different Domain” in GroupWise 7
Troubleshooting 3: Message Flow and Directory Structure. If you are using mapped/UNC links,
refer to GroupWise 6.5 Troubleshooting 3: Message Flow and Directory Structure.
40.7 Cross-Platform Issues between Domains
and Post Offices
Domains can be located on the following platforms:
Novell NetWare®
Windows Server
Linux
The GroupWise agents can run on the following platforms:
Novell NetWare
Windows Server
Linux
In general, GroupWise is most efficient if you match the agent platform with the network operating
system. Ideally, the MTA as well as the domain and post offices should be on the same platform.
However, those with mixed networks may wonder what combinations are possible. You have several
alternatives.
Section 40.7.1, “MTA Platform Dependencies Because of Direct Access Requirements to Post
Offices,” on page 610
Section 40.7.2, “MTA/Post Office Platform Independence through TCP/IP Links,” on page 610
Section 40.7.3, “MTA Platform Dependencies Because of Direct Access Requirements to the
Domain,” on page 610

610 GroupWise 7 Administration Guide
novdocx (en) 11 December 2007
Section 40.7.4, “MTA/Domain Platform Independence through TCP/IP Links,” on page 611
Section 40.7.5, “MTA/Domain Platform Independence through the Transfer Pull
Configuration,” on page 611
40.7.1 MTA Platform Dependencies Because of Direct Access
Requirements to Post Offices
The MTA must always have direct access to the domain directory. In addition, if using mapped or
UNC links to post offices, the MTA must have direct access to each post office directory as well. If
the MTA is installed on a remote server, it must be able to log in to servers where the post offices are
located.
The table below summarizes the various combinations of MTA and post office platforms, and
indicates which combinations work for direct access and which ones do not:
Table 40-1 MTA Platforms and Post Office Platforms
1TCP/IP links are required between the MTA and the POA on Linux. Direct access to post offices is
not available.
2The NetWare MTA cannot service a domain or post office on a Windows server because Windows
does not support the required cross-platform connection.
3Domains and post offices cannot be created on Macintosh computers.
40.7.2 MTA/Post Office Platform Independence through TCP/IP
Links
To overcome platform dependencies for post offices, create a TCP/IP link for any post office located
on a platform where the domain MTA cannot gain direct access. See “Using TCP/IP Links between
a Domain and its Post Offices” on page 623.
40.7.3 MTA Platform Dependencies Because of Direct Access
Requirements to the Domain
If using mapped or UNC links between domains, the source domain MTA must have direct access to
its input queues in the destination domain directory. If the MTA is installed on a remote server, it
must be able to log in to the server where its domain located.
NetWare MTA Linux MTA Windows MTA
Post Office on NetWare Yes No1Yes
Post Office on Linux No1No1No1
Post Office on Windows No2No1Yes
Post Office on
Macintosh
No3No3No3

Understanding Message Transfer between Domains and Post Offices 611
novdocx (en) 11 December 2007
The table below summarizes the various combinations of the platform of MTA for the source
domain and the platform where the destination domain is located, and indicates which combinations
work for direct access and which ones do not:
Table 40-2 MTA Platforms and Domain Platforms
1TCP/IP links are required between MTAs in GroupWise 7. Direct access to other domains is not
available.
2The NetWare MTA cannot write message files into its output queue in a destination domain on a
Windows server because Windows does not support the required cross-platform connection.
3Domains cannot be created on Macintosh computers.
40.7.4 MTA/Domain Platform Independence through TCP/IP
Links
To overcome platform dependencies between domains, use TCP/IP links between domains. See
Section , “Using TCP/IP Links between Domains,” on page 618.
40.7.5 MTA/Domain Platform Independence through the
Transfer Pull Configuration
If TCP/IP is not available, another alternative for overcoming platform dependencies is a transfer
pull configuration.
By default the MTA “pushes” message files out to destination domains by writing them into its
output queue in each destination domain. One situation where this method does not work is for the
NetWare MTA on a NetWare server to write message files to its input queue in a destination domain
located on a Windows server.
As an alternative, you can have the Windows MTA for the destination domain “pull” the message
files from the source domain on the NetWare server. This is called a transfer pull configuration. See
Section 41.3.3, “Using a Transfer Pull Configuration,” on page 636 for setup instructions.
NetWare MTA for
Source Domain
Linux MTA for Source
Domain
Windows MTA for Source
Domain
Destination Domain on
NetWare
Yes No1Yes
Destination Domain on
Linux
No1No1No3
Destination Domain on
Windows
No2No1Yes
Destination Domain on
Macintosh
No3No3No3

612 GroupWise 7 Administration Guide
novdocx (en) 11 December 2007

Configuring the MTA
41
novdocx (en) 11 December 2007
613
41
Configuring the MTA
For detailed instructions about installing and starting the MTA for the first time, see “Installing
GroupWise Agents” in the GroupWise 7 Installation Guide.
As your GroupWise®system grows and evolves, you will probably need to modify MTA
configuration to meet changing system needs. The following topics help you configure the MTA:
41.1 Performing Basic MTA Configuration
MTA configuration information is stored as properties of its MTA object in eDirectoryTM. The
following topics help you modify the MTA object in ConsoleOne®and change MTA configuration
to meet changing system configurations:
Section 41.1.1, “Creating an MTA Object in eDirectory,” on page 614
Section 41.1.2, “Configuring the MTA in ConsoleOne,” on page 615
Section 41.1.3, “Changing the Link Protocol between Domains,” on page 618
Section 41.1.4, “Changing the Link Protocol between a Domain and Its Post Offices,” on
page 622
Section 41.1.5, “Binding the MTA to a Specific IP Address,” on page 625
Section 41.1.6, “Moving the MTA to a Different Server,” on page 626
Section 41.1.7, “Adjusting the MTA for a New Location of a Domain or Post Office,” on
page 626
Section 41.1.8, “Adjusting the MTA Logging Level and Other Log Settings,” on page 627
Section 41.1, “Performing
Basic MTA Configuration,”
on page 613
Creating an MTA Object in eDirectory
Configuring the MTA in ConsoleOne
Changing the Link Protocol between Domains
Changing the Link Protocol between a Domain and Its Post Offices
Binding the MTA to a Specific IP Address
Moving the MTA to a Different Server
Adjusting the MTA for a New Location of a Domain or Post Office
Adjusting the MTA Logging Level and Other Log Settings
Section 41.2, “Configuring
User Access through the
Domain,” on page 628
Restricting Message Size between Domains
Enabling Live Remote
Securing the Domain with SSL Connections to the MTA
Section 41.3, “Configuring
Specialized Routing,” on
page 631
Using Routing Domains
Scheduling Direct Domain Links
Using a Transfer Pull Configuration
Section 41.4, “Configuring
Domain Maintenance,” on
page 638
Using eDirectory User Synchronization
Enabling MTA Message Logging

614 GroupWise 7 Administration Guide
novdocx (en) 11 December 2007
41.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 gets 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:
1In ConsoleOne, browse to and right-click the Domain object for which you need to create an
MTA object, then click New.
2Double-click GroupWise Agent to display the Create GroupWise Agent dialog box.
3Type 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:
The Type field is automatically set to Message Transfer.
4Select Define Additional Properties.
5Click OK.
The MTA object is automatically placed within the Domain object.
6Review 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.
ASCII characters 0-13 Comma ,
Asterisk * Double quote "
At sign @ Extended ASCII characters that are graphical or typographical
symbols; accented characters in the extended range can be used
Braces { } Parentheses ( )
Colon : Period .

Configuring the MTA 615
novdocx (en) 11 December 2007
7In 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 Chapter 42, “Monitoring the
MTA,” on page 645.
8In the Platform field, select the platform (NetWare, Linux, or Windows) where the MTA will
run.
9Continue with Section 41.1.2, “Configuring the MTA in ConsoleOne,” on page 615.
41.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.
1In ConsoleOne, expand the eDirectory container where the Domain object is located.
2Expand the Domain object.
3Right-click the MTA object, then click Properties.

616 GroupWise 7 Administration Guide
novdocx (en) 11 December 2007
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 Chapter 44, “Using MTA Startup
Switches,” on page 683):
Table 41-1 MTA Configuration Settings
ConsoleOne Properties Pages and
Settings Corresponding Tasks and Startup Switches
Information Page
Domain
Distinguished Name
Name
Agent Type
Description
Platform
See Section 41.1.1, “Creating an MTA Object in eDirectory,” on
page 614.
Agent Settings Page
Scan Cycle
Scan High
See Section 43.2.2, “Adjusting MTA Polling of Input Queues in the
Domain, Post Offices, and Gateways,” on page 676.
See also /cyhi and /cylo.
Attach Retry See Section 43.4, “Adjusting MTA Polling of Closed Locations,” on
page 680.
Enable Automatic Database
Recovery
See /norecover.
Use 2nd High Priority Scanner
Use 2nd Mail Priority Scanner
See Section 43.2.3, “Adjusting the Number of MTA Scanner
Threads for the Domain and Post Offices,” on page 678.
See also /fast0 and /fast4.
SNMP Community "Get" String See Section 42.6, “Using an SNMP Management Console,” on
page 667.

Configuring the MTA 617
novdocx (en) 11 December 2007
HTTP User Name
HTTP Password
See Section 42.2.1, “Setting Up the MTA Web Console,” on
page 657.
See also /httpuser and /httppassword.
Network Address Page
TCP/IP Address
IPX/SPX Address
See Section , “Using TCP/IP Links between Domains,” on
page 618 and Section , “Using TCP/IP Links between a Domain
and its Post Offices,” on page 623.
See also /ip and /tcpport.
Bind Exclusively to TCP/IP Address See Section 41.1.5, “Binding the MTA to a Specific IP Address,” on
page 625.
See also /ip.
Message Transfer See Section , “Using TCP/IP Links between Domains,” on
page 618.
See also /msgtranssl.
HTTP See Section 42.2.1, “Setting Up the MTA Web Console,” on
page 657.
See also /httpssl.
Log Settings Page
Log File Path
Logging Level
Max Log File Age
Max Log Disk Space
See Section 42.3, “Using MTA Log Files,” on page 665.
See also /log, /logdays, /logdiskoff, /loglevel, and /logmax.
Message Log Settings Page
Message Logging Level
Message Log File Path
See Section 41.4.2, “Enabling MTA Message Logging,” on
page 643.
See also /messagelogsettings, /messagelogpath,/
messagelogdays, and /messagelogmaxsize.
Scheduled Events Page
eDirectory User Synchronization
Event
See Section 41.4.1, “Using eDirectory User Synchronization,” on
page 638.
See also /nondssync.
Routing Options Page
Default Routing Domain
Force All Messages to Default
Routing Domain
See Section 41.3.1, “Using Routing Domains,” on page 631.
See also /defaultroutingdomain.
Allow MTA to Send Directly to
Other GroupWise Systems
See “Using Dynamic Internet Links” in “Connecting to GroupWise
5.x, 6.x, and 7.x Systems” in the GroupWise 7 Multi-System
Administration Guide.
See also /nodns.
MTA SSL Settings Page
ConsoleOne Properties Pages and
Settings Corresponding Tasks and Startup Switches

618 GroupWise 7 Administration Guide
novdocx (en) 11 December 2007
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 Chapter 44, “Using MTA Startup Switches,”
on page 683.
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 Section 10.1.3, “Link Protocols
for Direct Links,” on page 141.
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.
“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
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” on page 618
“Changing the Link Protocol between Domains to TCP/IP” on page 620
Configuring the MTA for TCP/IP
1Make sure TCP/IP is properly set up on the server where the MTA is running.
2In ConsoleOne, browse to and right-click the MTA object, then click Properties.
3Click GroupWise > Network Address to display the Network Address page.
Certificate File
SSL Key File
Password
See Section 41.2.3, “Securing the Domain with SSL Connections
to the MTA,” on page 629.
See also /certfile, /keyfile and /keypassword.
ConsoleOne Properties Pages and
Settings Corresponding Tasks and Startup Switches

Configuring the MTA 619
novdocx (en) 11 December 2007
4On the Network Address page, click the pencil icon for the TCP/IP Address field to display the
Edit Network Address dialog box.
5Select 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.
6Click OK.
7To 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.
8For optimum security, select Enabled in the SSL drop-down list for the message transfer port.
For more information, see Section 41.2.3, “Securing the Domain with SSL Connections to the
MTA,” on page 629.
9Click OK to save the network address and return to the main ConsoleOne window.
ConsoleOne then notifies the MTA to restart enabled for TCP/IP.

620 GroupWise 7 Administration Guide
novdocx (en) 11 December 2007
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:
1In ConsoleOne, click Tools > GroupWise Utilities > Link Configuration.
2Click View > Domain Links to display domain links.
3Select the MTA’s local domain in the drop-down list.
Outbound and inbound links for the selected domain are listed.
4Double-click a domain in the Outbound Links list.
5Set Link Type to Direct.
6Set 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.

Configuring the MTA 621
novdocx (en) 11 December 2007
7Click OK.
8Repeat 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.
9Double-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” on page 618.
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 7
Troubleshooting 3: Message Flow and Directory Structure.
Using Mapped or UNC Links between Domains
To change to a mapped or UNC link between domains:
1In ConsoleOne, click Tools > GroupWise Utilities > Link Configuration.
2Click View > Domain Links to display domain links.
3Select the MTA’s local domain in the drop-down list.
Outbound and inbound links for the selected domain are listed.
4Double-click a domain in the Outbound Links list.
5Set Link Type to Direct.
6Set Protocol to Mapped or UNC.
7Enter the full path, in the appropriate format, of the directory where the other domain is
located.
8Click OK.
9Repeat 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.

622 GroupWise 7 Administration Guide
novdocx (en) 11 December 2007
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” on page 622
“Using the Internet Agent to Link Domains” on page 622
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 (http://www.novell.com/documentation/gwgateways).
Using the Internet Agent to Link Domains
You can use the Internet Agent to link a domain into your GroupWise system across the Internet.
When you use the Internet Agent as the transport mechanism between domains, it encapsulates
GroupWise messages (both e-mail messages and administrative messages) within SMTP messages
in order to transport them across the Internet. For setup instructions, see Section 51.2, “Linking
Domains,” on page 810
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 7 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.
41.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,” on page 141.
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.
“Using TCP/IP Links between a Domain and its Post Offices” on page 623
“Using Mapped or UNC Links between a Domain and its Post Offices” on page 625
NOTE: The Linux MTA requires TCP/IP links between a domain and its post offices.