Novell
GroupWise®
7
September 29, 2006
www.novell.com
MULTI-SYSTEM ADMINISTRATION
GUIDE
Legal Notices
Novell, Inc. makes no representations or warranties with respect to the contents or use of this documentation, and
specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose.
Further, Novell, Inc. reserves the right to revise this publication and to make changes to its content, at any time,
without obligation to notify any person or entity of such revisions or changes.
Further, Novell, Inc. makes no representations or warranties with respect to any software, and specifically disclaims
any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc.
reserves the right to make changes to any and all parts of Novell software, at any time, without any obligation to
notify any person or entity of such changes.
Any products or technical information provided under this Agreement may be subject to U.S. export controls and the
trade laws of other countries. You agree to comply with all export control regulations and to obtain any required
licenses or classification to export, re-export, or import deliverables. You agree not to export or re-export to entities
on the current U.S. export exclusion lists or to any embargoed or terrorist countries as specified in the U.S. export
laws. You agree to not use deliverables for prohibited nuclear, missile, or chemical biological weaponry end uses.
See the Novell International Trade Services Web page (http://www.novell.com/info/exports/) for more information
on exporting Novell software. Novell assumes no responsibility for your failure to obtain any necessary export
approvals.
Copyright © 2003-2006 Novell, Inc. All rights reserved. No part of this publication may be reproduced, photocopied,
stored on a retrieval system, or transmitted without the express written consent of the publisher.
Novell, Inc. has intellectual property rights relating to technology embodied in the product that is described in this
document. In particular, and without limitation, these intellectual property rights may include one or more of the U.S.
patents listed on the Novell Legal Patents Web page (http://www.novell.com/company/legal/patents/) and one or
more additional patents or pending patent applications in the U.S. and in other countries.
Novell, Inc.
404 Wyman Street, Suite 500
Waltham, MA 02451
U.S.A.
www.novell.com
Online Documentation: To access the online documentation for this and other Novell products, and to get
updates, see the Novell Documentation Web site (http://www.novell.com/documentation).
Novell Trademarks
For Novell trademarks, see the Novell Trademark and Service Mark list (http://www.novell.com/company/legal/
trademarks/tmlist.html).
Third-Party Materials
All third-party trademarks are the property of their respective owners.
Contents
About This Guide 9
Part I Connecting to GroupWise 5.x, 6.x, and 7.x Systems 11
1 Understanding Connection Options 13
1.1 Connection Methods Supported by the Various GroupWise Versions . . . . . . . . . . . . . . . . . . 13
1.2 Dynamic Internet Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
1.3 Direct Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
1.4 Gateway Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
2 Using Dynamic Internet Links 17
2.1 MTA Version Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
2.2 Installing the GroupWise Internet Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
2.3 Setting Up Internet-Style Addressing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
2.4 Adding MTA Resource Records to DNS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
2.4.1 Creating the Address ("A") Record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
2.4.2 Creating the Service ("SRV") or Text ("TXT") Record. . . . . . . . . . . . . . . . . . . . . . . . 19
2.5 Configuring the MTA’s Server for DNS Lookups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
2.5.1 Configuring a NetWare 6.x or 5.1 Server for DNS Lookups . . . . . . . . . . . . . . . . . . . 20
2.5.2 Configuring a Windows 2000 Server for DNS Lookups. . . . . . . . . . . . . . . . . . . . . . . 20
2.6 Enabling MTAs to Perform DNS Lookups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
2.6.1 Enabling DNS Lookups for All MTAs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
2.6.2 Enabling/Disabling DNS Lookups for Individual MTAs . . . . . . . . . . . . . . . . . . . . . . . 22
2.7 Understanding Dynamic Internet Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
2.7.1 Stage 1: GroupWise Client in the Sending System . . . . . . . . . . . . . . . . . . . . . . . . . . 23
2.7.2 Stage 2: GroupWise Client in the Sending System . . . . . . . . . . . . . . . . . . . . . . . . . . 23
2.7.3 Stage 3: GroupWise MTA in the Sending System . . . . . . . . . . . . . . . . . . . . . . . . . . 24
2.7.4 Stage 4: GroupWise MTA in the Sending System . . . . . . . . . . . . . . . . . . . . . . . . . . 24
2.7.5 Stage 5: GroupWise MTA in the Sending System . . . . . . . . . . . . . . . . . . . . . . . . . . 24
2.7.6 Stage 6: GroupWise MTA in the Sending System . . . . . . . . . . . . . . . . . . . . . . . . . . 24
2.7.7 Stage 7: GroupWise Internet Agent in the Sending System . . . . . . . . . . . . . . . . . . . 24
2.7.8 Stage 8: GroupWise Internet Agent in the Sending System . . . . . . . . . . . . . . . . . . . 25
2.7.9 Stage 9: GroupWise MTA in the Sending System . . . . . . . . . . . . . . . . . . . . . . . . . . 25
2.7.10 Stage 10: GroupWise MTA in the Sending System . . . . . . . . . . . . . . . . . . . . . . . . . 25
2.7.11 Stage 11: GroupWise MTA in the Receiving System . . . . . . . . . . . . . . . . . . . . . . . . 25
2.7.12 Stage 12: Both GroupWise MTAs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
3 Using Direct Links 27
3.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
3.2 Creating an External Domain. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
3.3 Linking to the External Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
3.4 Checking the Link Status of the External Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
3.5 Sending Messages Between Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
3.6 Exchanging Information Between Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
3.7 Message Flow Between External Domains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Contents 5
4 Using Gateway Links 33
4.1 Connecting Systems Through the Internet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
4.2 Connecting Systems Through an Asynchronous Phone Line . . . . . . . . . . . . . . . . . . . . . . . . . 34
4.3 Connecting Systems Through an X.25 Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
4.4 Connecting GroupWise Systems Through Other E-Mail Systems . . . . . . . . . . . . . . . . . . . . . . 34
5 Synchronizing External GroupWise Systems 37
Part II Connecting to Non-GroupWise Messaging Systems 41
6 GroupWise Internet Agent 43
7 GroupWise Gateways 45
Part III Merging with GroupWise 5.x, 6.x, and 7.x Systems 47
8 Why Merge GroupWise Systems? 49
9 Planning the Merge 51
9.1 Understanding the Merge Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
9.2 Planning Administrator Rights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
9.3 Determining Which GroupWise Objects Are No Longer In Use . . . . . . . . . . . . . . . . . . . . . . . . 53
9.4 Planning the Location of the Domain Database Backup Directories . . . . . . . . . . . . . . . . . . . . 54
9.5 Planning GroupWise System Connections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
9.5.1 External Domains. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
9.5.2 Linking the Domains. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
9.5.3 Releasing the Secondary Domains in Site #2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
9.6 Planning to Merge Additional GroupWise Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
9.6.1 Merging in One Session. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
9.6.2 Merging at Different Times. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
9.7 Merge Planning Worksheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
10 Preparing for the Merge 65
10.1 Setting Up Administrator Rights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
10.2 Deleting Unused GroupWise Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
10.3 Verifying That UNC Paths Are Correct . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
10.4 Resolving Pending Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
11 Merging the GroupWise Systems 67
11.1 Creating External Domains for Both Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
11.1.1 Creating Site #1 External Domains in Site #2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
11.1.2 Creating Site #2 External Domains in Site #1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
11.2 Configuring Links Between Site #2 Domains and Site #1 Secondary Domains . . . . . . . . . . . . 69
11.3 Checking Links to External Domains for Both Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
11.3.1 Checking Links to Site #1 External Domains in Site #2 . . . . . . . . . . . . . . . . . . . . . . . 70
11.3.2 Checking Links to Site #2 External Domains in Site #1 . . . . . . . . . . . . . . . . . . . . . . . 70
11.4 Creating Temporary Holding Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
11.5 Releasing Site #2 Secondary Domains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
6 GroupWise 7 Multi-System Administration Guide
11.6 Sending Site #2 Databases to the Site #1 Administrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
11.7 Receiving Site #2 Databases at Site #1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
11.8 Merging a Site #2 Domain into Site #1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
11.9 Merging the Next GroupWise System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
11.10 Sending the Merged Site #2 Databases to Site #2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
11.11 Restarting the GroupWise Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
11.12 Testing the Merged System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
A Documentation Updates 75
A.1 September 29, 2006 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
A.2 June 15, 2006 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Contents 7
8 GroupWise 7 Multi-System Administration Guide
About This Guide
This Novell® GroupWise® 7 Multi-System Administration Guide helps you connect your
GroupWise system to other GroupWise systems or non-GroupWise messaging systems, and helps
you merge your GroupWise system with another GroupWise system to create one system. The guide
is divided into the following sections:
“Connecting to GroupWise 5.x, 6.x, and 7.x Systems” on page 11
“Connecting to Non-GroupWise Messaging Systems” on page 41
“Merging with GroupWise 5.x, 6.x, and 7.x Systems” on page 47
Audience
This guide is intended for network administrators who install and administer GroupWise.
Feedback
We want to hear your comments and suggestions about this manual and the other documentation
included with this product. Please use the User Comment feature at the bottom of each page of the
online documentation, or go to www.novell.com/documentation/feedback.html and enter your
comments there.
Documentation Updates
For the most recent version of the GroupWise 7 Multi-System Administration Guide, visit the Novell
GroupWise 7 Documentation Web site (http://www.novell.com/documentation/gw7).
Additional Documentation
For additional GroupWise documentation, see the following guides at the Novell GroupWise 7
documentation Web site (http://www.novell.com/documentation/gw7):
Installation Guide
Administration Guide
Interoperability Guide
Troubleshooting Guides
GroupWise Client User Guides
GroupWise Client Frequently Asked Questions (FAQ)
Documentation Conventions
In Novell documentation, a greater-than symbol (>) is used to separate actions within a step and
items in a cross-reference path.
A trademark symbol (
trademark.
®
, TM, etc.) denotes a Novell trademark. An asterisk (*) denotes a third-party
About This Guide
9
When a single pathname can be written with a backslash for some platforms or a forward slash for
other platforms, the pathname is presented with a backslash. Users of platforms that require a
forward slash, such as Linux*, should use forward slashes as required by your software.
When a startup switch can be written with a forward slash for some platforms or a double hyphen for
other platforms, the startup switch is presented with a forward slash. Users of platforms that require
a double hyphen, such as Linux, should use double hyphens as required by your software.
10 GroupWise 7 Multi-System Administration Guide
I
Connecting to GroupWise 5.x, 6.x,
and 7.x Systems
Chapter 1, “Understanding Connection Options,” on page 13
Chapter 2, “Using Dynamic Internet Links,” on page 17
Chapter 3, “Using Direct Links,” on page 27
Chapter 4, “Using Gateway Links,” on page 33
Chapter 5, “Synchronizing External GroupWise Systems,” on page 37
Connecting to GroupWise 5.x, 6.x, and 7.x SystemsI11
12 GroupWise 7 Multi-System Administration Guide
1
Understanding Connection
Options
When connecting your GroupWise® 7.x system with another GroupWise 5.x, 6.x, or 7.x system, you
can choose from several connection methods. To help you choose the best method for your system,
the following sections provide brief summaries:
Section 1.1, “Connection Methods Supported by the Various GroupWise Versions,” on
page 13
Section 1.2, “Dynamic Internet Links,” on page 14
Section 1.3, “Direct Links,” on page 14
Section 1.4, “Gateway Links,” on page 14
Depending on the versions of the two GroupWise systems you are trying to connect, some of the
methods might not be available. For information about methods available for the two systems you
are connecting, see Section 1.1, “Connection Methods Supported by the Various GroupWise
Versions,” on page 13.
1.1 Connection Methods Supported by the
Various GroupWise Versions
1
The following chart lists the GroupWise 5.x, 6.x, and 7.x versions and the methods that can be used
when connecting systems that are these versions:
KEY
D = Direct Link
G = Gateway Link
I = Dynamic Internet Link
5.0 5.1 5.2 5.5 5.5 EP 6.x 7.x
5.0 D G D G D G D G D G D G D G
5.1 D G D G D G D G D G D G D G
5.2 D G D G D G D G D G D G D G
5.5 D G D G D G D G I DGI D GI D GI
5.5 EP D G D G D G D G I D G I D G I D G I
6.x D G D G D G D G I D G I D G I D G I
7.x D G D G D G D G I D G I D G I D G I
To use the chart, locate your system’s version in the first column, then read across the row until you
reach the version of the system you are connecting to. The methods listed are the methods supported
when connecting the two systems.
Understanding Connection Options
13
IMPORTANT: A GroupWise system’s version is determined by the version of the Message
Transfer Agent (MTA) running in the system. If your system includes multiple versions of the
MTA, determine which MTA will be used when connecting to the other system and use that MTA’s
version when reading the table.
1.2 Dynamic Internet Links
The dynamic Internet link capability of the GroupWise Message Transfer Agent (MTA) enables it to
use Domain Name Service (DNS) to associate the domain name in an Internet-style address (for
example, jsmith@novell.com) to an MTA assigned to receive messages for that domain name. After
the address has been resolved, the sending MTA uses the GroupWise Message Transfer Protocol
(GWMTP) to connect with and transfer messages to the destination MTA.
Because messages are transferred directly from one MTA to another, no GroupWise client
functionality is lost. Users can perform Busy Searches, retract sent messages, and see the status of
their outgoing messages, just as if the recipient were in the same GroupWise system. In addition,
users are able to use well-known Internet-style address syntax (for example, jsmith@novell.com).
Administratively, using dynamic Internet links enables you to avoid defining users from other
GroupWise systems in your GroupWise system. As long as the sender knows the recipient’s
Internet-style address, and the recipient’s domain name is registered in DNS and associated with an
MTA, the message is properly routed to the recipient.
For information about connecting GroupWise systems via dynamic Internet links, see Chapter 2,
“Using Dynamic Internet Links,” on page 17.
1.3 Direct Links
The direct link capability of the MTA enables it to use a mapped or UNC path to access a domain
directory in another GroupWise system or to use TCP/IP to connect to the domain’s MTA. This is
the same functionality that enables two domains in the same GroupWise system to be connected.
Because messages are transferred directly from one MTA to another, no GroupWise client
functionality is lost.
Administratively, you can use the External System Synchronization feature to exchange information
between the two systems and enable users to select addresses from the Address Book, or you can
choose to not exchange information and require users to enter a fully-qualified address
(userID.post_office.domain or user@host).
For information about connecting GroupWise systems via direct links, see Chapter 3, “Using Direct
Links,” on page 27.
1.4 Gateway Links
If you can’t establish a direct link (mapped path, UNC path, or TCP/IP connection) between
domains in two systems, you can use a GroupWise gateway to link the two systems. Depending on
the gateway used, some GroupWise functionality might not be available when sending messages
between systems.
For information about connecting GroupWise systems via gateways, see Chapter 4, “Using Gateway
Links,” on page 33.
14 GroupWise 7 Multi-System Administration Guide
Understanding Connection Options 15
16 GroupWise 7 Multi-System Administration Guide
2
Using Dynamic Internet Links
You can connect two GroupWise® systems through dynamic Internet links. Dynamic Internet links
enable a GroupWise Message Transfer Agent (MTA) to use Domain Name Service (DNS) and
GroupWise Message Transfer Protocol (GWMTP) to send messages from one system to anther. For
an overview of dynamic Internet links, see Chapter 1, “Understanding Connection Options,” on
page 13.
To use dynamic Internet links, complete the tasks in the following sections:
Section 2.1, “MTA Version Requirements,” on page 17
Section 2.2, “Installing the GroupWise Internet Agent,” on page 17
Section 2.3, “Setting Up Internet-Style Addressing,” on page 18
Section 2.4, “Adding MTA Resource Records to DNS,” on page 18
Section 2.5, “Configuring the MTA’s Server for DNS Lookups,” on page 20
Section 2.6, “Enabling MTAs to Perform DNS Lookups,” on page 21
Section 2.7, “Understanding Dynamic Internet Links,” on page 23
For a general explanation of how dynamic Internet links work, see Section 2.7, “Understanding
Dynamic Internet Links,” on page 23.
2
2.1 MTA Version Requirements
To use dynamic Internet links to connect your GroupWise system with another GroupWise system,
both GroupWise systems must have at least one domain that is running one of the following versions
of the GroupWise MTA:
GroupWise 5.5
GroupWise 5.5 Enhancement Pack
GroupWise 6.x
GroupWIse 7.x
Versions of the MTA prior to version 5.5 do not support dynamic Internet links.
2.2 Installing the GroupWise Internet Agent
Before configuring your GroupWise system to use dynamic Internet links, you need to make sure
that the GroupWise Internet Agent has been installed. Dynamic Internet links require your
GroupWise system to use Internet-style addressing, which is only available if you’ve installed the
Internet Agent and created one or more Internet domains for your GroupWise system.
The only requirement is that the Internet Agent be installed so that an Internet Agent object is
created in Novell
correctly or running. However, if there are GroupWise systems that you need to connect to but
cannot do so through dynamic Internet links, you can use the Internet Agent to connect to those
systems while using dynamic Internet links to connect to supported GroupWise systems.
®
eDirectoryTM. The Internet Agent does not actually need to be configured
Using Dynamic Internet Links
17
For information about installing the Internet Agent, see “Installing the GroupWise Internet Agent”
in the GroupWise 7 Installation Guide.
2.3 Setting Up Internet-Style Addressing
Dynamic Internet links require your GroupWise system to be configured to use Internet-style
addressing (user@hostname) rather than standard GroupWise addressing
(userID.post_office.domain). If you have not enabled Internet-style addressing and defined at least
one Internet domain for your GroupWise system, see “Configuring Internet Addressing” in the
GroupWise 7 Administration Guide.
The Internet domains you establish when setting up Internet-style addressing (for example,
novell.com, groupwise.novell.com, and support.novell.com) are the key to enabling dynamic
Internet links. Each MTA that will receive messages must be defined in DNS and associated with
the Internet domain (or domains) that it will receive messages for. This allows MTAs in other
GroupWise systems to route messages that contain your Internet domain names to the appropriate
MTAs in your system.
2.4 Adding MTA Resource Records to DNS
In order for your GroupWise system to receive messages from another GroupWise system via a
dynamic Internet link, you need to create a DNS resource record for at least one of your MTAs. The
resource record enables the MTA’s address, along with the Internet domain names associated with
it, to be broadcast throughout the Internet.
You need to create the following resource records in DNS:
An address ("A") record that maps the MTA server’s host name to its IP address.
A service ("SRV") record or a text ("TXT") record that maps the Internet domain name to the
host name or IP address assigned to the MTA’s server.
You can use your tool of choice to modify DNS. The following sections explain the information
required and provide sample records.
Section 2.4.1, “Creating the Address ("A") Record,” on page 18
Section 2.4.2, “Creating the Service ("SRV") or Text ("TXT") Record,” on page 19
2.4.1 Creating the Address ("A") Record
You can create an "A" record to map your MTA server’s fully-qualified host name to its IP address.
Doing so enables you to use the server’s fully-qualified host name in the service ("SRV") or text
("TXT") record rather than the IP address. The "A" record is required if you plan to use a "SRV"
record.
The following text shows sample "A" records.
;
; Address ("A") records
;
localhost IN A 172.0.0.1
corp.serv.novl IN A 172.16.5.18
gwdev.serv.novl IN A 172.16.5.19
gwsup.serv.novl IN A 172.16.5.20
18 GroupWise 7 Multi-System Administration Guide
Host Name (column 1): Use the host name assigned to the MTA’s server. In the above example,
corp, gwdev, and gwsupport are the host names assigned to three MTA servers.
Class (column 2): Use IN to represent the Internet.
Type (column 3): Use A to specify an address record.
IP Address (column 4): Use the IP address assigned to the MTA’s server.
2.4.2 Creating the Service ("SRV") or Text ("TXT") Record
You can use either service records or text records to map your Internet domain names to MTAs. The
following text shows sample "SRV" and "TXT" records:
;
; Service ("SRV") records
;
gwmtp.tcp.novell.com 172800 IN SRV 1 0 7100 corp.serv.novl
gwmtp.tcp.groupwise IN SRV 1 1 7100 corp.serv.novl
gwmtp.tcp.groupwise IN SRV 1 2 7100 gwdev.serv.novl
gwmtp.tcp.support 172800 IN SRV 1 0 7100 gwsup.serv.novl
gwmtp.tcp.support 172800 IN SRV 2 0 7100 corp.serv.novl
;
; Text ("TXT") records
;
gwmtp.tcp.novell.com 172800 IN TXT "1 0 7100 corp.serv.novl"
gwmtp.tcp.groupwise IN TXT "1 1 7100 corp.serv.novl"
gwmtp.tcp.groupwise IN TXT "1 2 7100 gwdev.serv.novl"
gwmtp.tcp.support 172800 IN TXT "1 0 7100 gwsup.serv.novl"
gwmtp.tcp.support 172800 IN TXT "2 0 7100 corp.serv.novl"
Service.Protocol.Name (column 1): The service must be specified as gwmtp. The protocol must
be specified as tcp. The name corresponds to the Internet domain name you want associated with
the MTA. In the above sample, novell.com, groupwise.novell.com, and support.novell.com are the
Internet domain names defined in GroupWise.
Time to Live (column 2): TTL (time to live) is the amount of time the record is cached in memory
so it doesn’t need to be looked up again. TTL is specified in seconds. In the above sample, 172800
represents 2 days. If you don’t specify a TTL, the record is not cached.
Class (column 3): Enter IN to represent the Internet.
Type (column 4): Enter SRV to specify a service record. Enter TXT to specify a text record.
Priority (column 5): If an Internet domain name is associated with two different MTAs, the host
with the lowest value is always contacted first. For example, a host with priority 1 is contacted
before a host with priority 2. If two records with the same Internet domain name have the same
priority, the weight number is used. In the above example, the two groupwise.novell.com records
have the same priority, so the weight would be used.
Weight (column 6): The weight number specifies how to allocate connections among hosts with
equal priorities. In the groupwise.novell.com record above, the corp.serv.novl host and the
gwdev.serv.novl host have equal priorities, but the corp.serv.novl host has a weight of 1
and the gwdev.serv.novl host has a weight of 2. This means that 1 out of 3 times the
Using Dynamic Internet Links 19
corp.serv.novl host would be contacted first, and 2 out of 3 times, the gwdev.serv.novl
host would be contacted first.
Port (column 7): The port number specifies the TCP port on which the MTA listens for incoming
messages. The default port number for the MTA is 7100.
Host (column 8): The host specifies the fully-qualified host name or IP address of the MTA’s
server. For a service record, you must specify the host name. For a text record, you can specify
either the server’s host name or IP address. If you use a host name, it must be mapped to an IP
address through an DNS "A" record. In the above example, corp.serv.novl,
gwdev.serv.novl, and gwsup.serv.novl are all host names that are mapped to IP
addresses through "A" records in DNS.
2.5 Configuring the MTA’s Server for DNS
Lookups
In order for an MTA in your GroupWise system to use dynamic Internet links to send messages, you
must make sure the MTA’s server is properly configured for DNS lookups. Basic configuration
information is provided below. Consult your DNS documentation for more detailed information
about configuring a server for DNS lookups.
Section 2.5.1, “Configuring a NetWare 6.x or 5.1 Server for DNS Lookups,” on page 20
Section 2.5.2, “Configuring a Windows 2000 Server for DNS Lookups,” on page 20
2.5.1 Configuring a NetWare 6.x or 5.1 Server for DNS Lookups
On a NetWare® server, you need to have a resolv.cfg file in the sys:\etc directory that
defines the DNS name server for that NetWare server. The resolv.cfg file would look similar to
the following, based on a novell.com domain:
domain novell.com
nameserver 172.16.5.18
Consult your NetWare documentation for more detailed information about configuring a NetWare
server for DNS lookups.
2.5.2 Configuring a Windows 2000 Server for DNS Lookups
On the Windows* 2000 server:
1 Click the Start menu > Settings > Control Panel.
2 Double-click Network and Dial-Up Connections, double-click Local Area Connection, then
click Properties to display the Local Area Connection Properties dialog box.
3 In the list of protocols, select Internet Protocol (TCP/IP), then click Properties to display the
Internet Protocol (TCP/IP) Properties dialog box.
4 Click Advanced to display the Advanced TCP/IP Settings dialog box.
5 Click the DNS tab, then make sure the IP address of at least one DNS name server is listed in
the DNS Server Addresses list.
Consult your DNS documentation for more detailed information about configuring a Windows
workstation or server for DNS lookups.
20 GroupWise 7 Multi-System Administration Guide
2.6 Enabling MTAs to Perform DNS Lookups
After you have performed the necessary configuration to enable an MTA’s server to allow DNS
lookups (see Section 2.5, “Configuring the MTA’s Server for DNS Lookups,” on page 20), you
must configure the MTA to perform DNS lookups.
By default, your GroupWise system is configured not to allow MTAs to perform DNS lookups. You
can retain the system default of no DNS lookups, then enable DNS lookups for individual MTAs. Or
you can enable DNS lookups for all MTAs in your GroupWise system, then selectively disable DNS
lookups for individual MTAs.
Section 2.6.1, “Enabling DNS Lookups for All MTAs,” on page 21
Section 2.6.2, “Enabling/Disabling DNS Lookups for Individual MTAs,” on page 22
2.6.1 Enabling DNS Lookups for All MTAs
To configure your GroupWise system so all MTAs perform DNS lookups (provided their servers are
enabled for DNS lookups):
®
1 In ConsoleOne
to display the GroupWise System Preferences dialog box.
, click the Tools menu > GroupWise System Operations > System Preferences
2 Click the Routing Options tab.
3 Enable the Allow MTAs to Send Directly to Other GroupWise Systems option
If the option is dimmed, you have not defined an Internet domain yet. See “Configuring
Internet Addressing” in “System” in the GroupWise 7 Administration Guide.
4 Click OK.
Using Dynamic Internet Links 21
2.6.2 Enabling/Disabling DNS Lookups for Individual MTAs
If you’ve used the GroupWise System Preferences to enable all MTAs to perform DNS lookups in
order to send messages directly to other GroupWise systems (see “Enabling DNS Lookups for All
MTAs” on page 21), you can disable DNS lookups for individual MTAs.
If you haven’t used the GroupWise System Preferences to enable all MTAs to perform DNS
lookups, you can enable DNS lookups for individual MTAs.
1 In ConsoleOne, right-click the MTA object, then click Properties.
2 Click GroupWise > Routing Options to display the Routing Options page.
3 Select the Override box to the left of the Allow MTA to Send Directly to Other GroupWise
Systems option.
4 Select or deselect Allow MTA to Send Directly to Other GroupWise Systems as needed for this
MTA.
5 Click OK.
22 GroupWise 7 Multi-System Administration Guide
2.7 Understanding Dynamic Internet Links
The following diagram illustrates the basic process of establishing a dynamic Internet link between
GroupWise systems.
ctp.com
10
yes
no
2
1
9
GWMTP
12
MTA
DNS
11
SRV
no
yes
yes
MTA
3
Undeliverable
no
4
yes
MTA
no
no
yes
5
DNS
no
GWIA
yes
no
6
no
Undeliverable
no
no
8
7
yes
SMTP
DNS
yes
SMTP
Mail
Server
TXT
DNS
MX
yes
Domain
Look up
Undeliverable
Domain
2.7.1 Stage 1: GroupWise Client in the Sending System
The GroupWise client parses the address by breaking it down into parts and attempting to map it to
the userID.post_office.domain syntax. When the parsing is complete, the client looks in its own
system address book and asks: “Does the parsed address match any listed in the system address
book?”
The address can be typed by the user or obtained from the system address book.
If Yes: The GroupWise client sends this “internal” message to the MTA to be queued for
delivery.
If No: The GroupWise client attempts to resolve the address further. Go to Stage 2.
2.7.2 Stage 2: GroupWise Client in the Sending System
The GroupWise client checks the Internet domain addressing element listed after an @ sign in the
address syntax and asks: “Is this Internet domain defined in my GroupWise system (that is, is it
internal)?” If there is no Internet domain element at this point, the message is undeliverable.
If Yes: The client looks at the address to determine if all parts are present. If they are present, it
attempts to find a domain element in the address and resolve the address for local delivery. If a
domain element cannot be found, the message is undeliverable.
Using Dynamic Internet Links 23
Loading...