Managing the Links between Domains and Post Offices
10
145
n
ov
do
cx (e
n)
22
Ju
n
e 20
09
10
Managing the Links between
Domains and Post Offices
When you create a new secondary domain in your GroupWise
®
system or a new post office in a
domain, you configure one direct link to connect the new domain or post office to a domain in your
GroupWise system. For simple configurations, this initial link might be adequate. For more complex
configurations, you must modify link types and protocols to achieve optimum message flow
throughout your GroupWise system.
The following topics help you manage links between domains and post offices:
Section 10.1, “Understanding Link Configuration,” on page 145
Section 10.2, “Using the Link Configuration Tool,” on page 151
Section 10.3, “Interpreting Link Symbols,” on page 158
Section 10.4, “Modifying Links,” on page 159
10.1 Understanding Link Configuration
In GroupWise, a link is defined as the information required to route messages between domains,
post offices, and gateways in a GroupWise system. Initial links are created when domains, post
offices, and gateways are created. The following topics help you understand link configuration:
Section 10.1.1, “Domain-to-Domain Links,” on page 145
Section 10.1.2, “Domain-to-Post Office Links,” on page 148
Section 10.1.3, “Link Protocols for Direct Links,” on page 149
10.1.1 Domain-to-Domain Links
The primary role of the MTA is to route messages from one domain to another. Domain links tell the
MTA how to route messages between domains. Domain links are stored in the domain database
(
wpdomain.db
). There are three types of links between source and destination domains:
“Direct Links” on page 145
“Indirect Links” on page 146
“Gateway Links” on page 148
As an alternative to configuring individual links between individual domains throughout your
GroupWise system, you can establish a system of one or more routing domains. See
Section 41.3.1,
“Using Routing Domains,” on page 646
.
Direct Links
In a direct link between domains, the source domain’s MTA communicates directly with the
destination domain’s MTA. If it is using a TCP/IP link, the source domain MTA communicates
messages to the destination domain MTA by way of TCP/IP, which does not require disk access by
the source MTA in the destination domain. If it is using a mapped or UNC link, the source domain
