Exchange To Domino0

Printed in the U.S.A.
The Next Generation in Messaging: Moving from Microsoft Mail to Lotus Notes and Domino
SG24-5152-01
Part No. CT7SBNA

The Next Generation in Messaging:
Moving from Microsoft Mail
to Lotus Notes and Domino
Marion Hawker, Siva Kumar
International Technical Support Organization
http://www.redbooks.ibm.com
SG24-5152-01
44 Lotus Notes and Domino R5.0 Security Infrastructure Revealed
SG24-5152-01
The Next Generation in Messaging
Moving from Microsoft Mail to

Lotus Notes and Domino
June 1999
Take Note!
Before using this information and the product it supports, be sure to read the general information in
the Special Notices section at the back of this book.
Second Edition (June 1999)
This edition applies to Lotus Domino Release 5.0.
Comments may be addressed to: IBM Corporation, International Technical Support Organization
Dept. JN9B Building 045 Internal Zip 2834
11400 Burnet Road
Austin, Texas 78758-3493
When you send information to IBM, you grant IBM a non-exclusive right to use or distribute the
information in any way it believes appropriate without incurring any obligation to you.
© International Business Machines Corporation (1998, 1999). All rights reserved.
Note to U.S. Government Users: Documentation related to restricted rights. Use, duplication or disclosure
is subject to restrictions set forth in GSA ADP Schedule Contract with IBM Corp .
Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . v Lotus Domino Release 5.0 SMTP Mail

The Team That Wrote This Redbook . . . . . . . vi Routing . . . . . . . . . . . . . . . . . . . .. 14
Comments Welcome . . . . . . . . . . . . . . . . vii Understanding the SMTP Environment . . . .. 17
A Typical SMTP Connection between
1 Introduction . . . . . . . . . . . . . . . . . . 1 Domino and Microsoft Mail . . . . . . .. 17
Our Objective . . . . . . . . . . . . . . . . . . . . . 1
How Mail Routing Works Using SMTP . .. 18
Our Scope . . . . . . . . . . . . . . . . . . . . . . . . 2
Planning and Designing the SMTP Network .. 19
Coexistence Tools . . . . . . . . . . . . . . . . . 2
Hardware and Software Requirements . .. 19
Migration Tools . . . . . . . . . . . . . . . . . . 2
Microsoft Mail Postoffice Requirements . .. 20
Special Considerations . . . . . . . . . . . . . . 2
Microsoft Mail Naming Considerations . .. 20
Other Redbooks . . . . . . . . . . . . . . . . . . . . 3
Case Study: Designing the SMTP
2 Microsoft Mail and Lotus Network . . . . . . . . . . . . . . . . . . . .. 21
Domino . . . . . . . . . . . . . . . . . . . . . . . . 5 Planning for an SMTP Connection . . . . .. 23
What Is Microsoft Mail? . . . . . . . . . . . . ... 5 Installing the Microsoft Mail Gateway to
Network Design Aspects of Microsoft Mail ... 5 SMTP . . . . . . . . . . . . . . . . . . . . . .. 24
Network and Postoffice Concepts in Pre-installation Tasks . . . . . . . . . . . . .. 24
Microsoft Mail . . . . . . . . . . . . . . ... 5 Installing the Microsoft Mail Gateway
Name Architecture . . . . . . . . . . . . . ... 6 Component . . . . . . . . . . . . . . . . . .. 25
Logical Network Design . . . . . . . . . . ... 6 Installing the Gateway Access
Mail Routing in Microsoft Mail . . . . . ... 8 Component on the Gateway Postoffice .. 27
Comparing the Infrastructure Components Installing the Gateway Access
of Microsoft Mail and Lotus Domino ... 9 Component on a Downstream
Postoffice . . . . . . . . . . . . . . . . . . .. 29
Choosing a Coexistence Tool . . . . . . . . . ... 10
Setting up the Microsoft Mail SMTP
Coexistence Tools . . . . . . . . . . . . . . ... 10 Gateway . . . . . . . . . . . . . . . . . . . .. 30
Choosing a Migration Tool . . . . . . . . . . ... 11 Installing and Configuring Domino Release
Single-Step Migration Process . . . . . . ... 11 5.0 SMTP Routing . . . . . . . . . . . . . .. 33
Long-Term Coexistence and Migration ... 11 Pre-installation Tasks . . . . . . . . . . . . .. 33
Migration Tools . . . . . . . . . . . . . . . ... 11 Installing and Setting up Domino SMTP
Summary . . . . . . . . . . . . . . . . . . . . . ... 12 Routing . . . . . . . . . . . . . . . . . . . .. 34
3 Microsoft Mail and Lotus Using the Microsoft Mail SMTP Gateway
and the Domino SMTP Mail Routing . .. 45
Domino Coexistence: Open
Environment Using SMTP . . . . . . . . 13 Starting the MAILHUB Domino Server . .. 45
Microsoft Mail SMTP Gateway and Domino Stopping the Lotus Domino SMTP Mail
SMTP Mail Routing . . . . . . . . . . . . .. 14 Routing . . . . . . . . . . . . . . . . . . . .. 45
Microsoft Mail SMTP Gateway . . . . . . .. 14
iii
Starting the Microsoft Mail Gateway to Installing the User Migration Tool . ..... 85
SMTP . . . . . . . . . . . . . . . . . . . ... 45 Using the Schedule+ Migration Tool ..... 87
Stopping the Microsoft Mail Gateway to Monitoring the Logs and Statistics . ..... 92
SMTP . . . . . . . . . . . . . . . . . . . . ... 45
Summary . . . . . . . . . . . . . . . . . . .
..... 94
Sending SMTP Mail between Microsoft
Mail and Lotus Domino . . . . . . . . ... 45 Special Notices . . . . . . . . . . . . . . . . . 95
MS Mail AutoForward . . . . . . . . . . . . . ... 47 Related Publications . . . . . . . . . . . . . 99
Business Problem . . . . . . . . . . . . . . ... 47 International Technical Support
Organization Publications . . . . . . . . . . 99
Product Description . . . . . . . . . . . . ... 48
Product Design and Prerequisites . . . . ... 49
Other Lotus-Related ITSO Publications . . . . . 99
Redbooks on CD-ROMs . . . . . . . . . . . . . . 101
Product Configuration . . . . . . . . . . . ... 49
Product Information . . . . . . . . . . . . ... 50 How to Get ITSO Redbooks . . . . . . 103
Lotus Notes Directory Transporter for IBM Intranet for Employees . . . . . . . . . . . 103
Microsoft Mail SMTP Gateways . . . ... 50 IBM Redbook Fax Order Form . . . . 105
Business Problem . . . . . . . . . . . . . . ... 50 Index . . . . . . . . . . . . . . . . . . . . . . . . . 107
Product Description . . . . . . . . . . . . ... 51
ITSO Redbook Evaluation . . . . . . . 109
Product Information . . . . . . . . . . . . ... 51
Summary . . . . . . . . . . . . . . . . . . . . . ... 52
4 Migrating from Microsoft Mail
to Lotus Domino: Using the Lotus
Domino Migration Tools . . . . . . . . . . 53
Using the Administrator-Based Migration
Tool . . . . . . . . . . . . . . . . . . . . .... 53
Understanding the Migration Process .... 54
Preparing to Migrate Microsoft Mail
Users . . . . . . . . . . . . . . . . . . . .... 55
Installing the Migration Tools . . . . . .... 56
Performing the Migration Process . . .... 58
Monitoring Logs and Statistics . . . . . .... 80
Summary . . . . . . . . . . . . . . . . . . . . .... 82
5 Migrating from Microsoft
Schedule+ 1.0 to Lotus Domino
Calendaring & Scheduling . . . . . . . . 83
Understanding the Schedule+ 1.0
Environment . . . . . . . . . . . . . . . ... 83
Understanding the Lotus Domino
Calendaring & Scheduling
Environment . . . . . . . . . . . . . . . ... 84
Using the Binary Tree User Migration Tool ... 84
Understanding the Migration Process . ... 85
Planning for the User Migration Tool . ... 85
iv Moving from Microsoft Mail to Lotus Notes and Domino

Preface
This redbook describes how to migrate from a Microsoft Mail environment

to Lotus® Notes® and Domino® Release 5.0.
Following the introduction, the Microsoft Mail and Lotus Domino
environments are presented in an overview, and some general guidelines are
given for the selection of a coexistence and migration tool that meets the
customer’s requirements.
The chapters following the overview provide information on some of the
coexistence tools available. This is intended for those customers who have a
requirement for coexistence between the two environments before migrating
to Lotus Notes and Domino. The coexistence tools covered in this redbook
are the Microsoft Mail SMTP Gateway in conjunction with the SMTP mail
routing available with Lotus Domino Release 5.0 and two coexistence tools
offered by Binary Tree, Inc. for mail forwarding and directory
synchronization.
The later chapters focus on the migration from Microsoft Mail to Lotus
Domino. First, the administrator-based and user-based migration tools
provided by Lotus Domino Release 5.0 for migration from Microsoft Mail to
Lotus Domino Release 5.0 are discussed in detail. Then the user migration
tool from Binary Tree for migrating Schedule+ 1.0 data to Lotus Domino
Release 5.0 Calendaring & Scheduling is described.
This redbook documents a number of third-party products for migration and
coexistence. By including them in this document, IBM/Lotus do not solely endorse
these products for use in this type of environment. Other third-party products may
be available that perform similar or equivalent functions.
The redbook was written for system administrators, IBM business partners,
and the IBM® and Lotus community, who need a good technical
understanding of how to configure a coexistence environment between
Microsoft Mail and Lotus Domino Release 5.0, and how to migrate users and
data from Microsoft Mail to Lotus Domino Release 5.0.
v
The following redbooks cover related topics and might also be of interest:
• For a detailed technical comparison between Microsoft Exchange Server
Release 5.5 and Lotus Domino Release 5.0, refer to the following
redbook:
The Three Steps to Super.Human.Software: Compare, Coexist, Migrate. From
Microsoft Exchange to Lotus Domino. Part One: Comparison, IBM form
number SG24-5614, Lotus part number CT7QTNA
• For information on coexistence between, and migration from, Microsoft
Exchange Server Release 5.5 to Lotus Domino Release 5.0, refer to the
following redbook:
The Three Steps to Super.Human.Software: Compare, Coexist, Migrate. From
Microsoft Exchange to Lotus Domino. Part Two: Coexistence and Migration,
IBM form number SG24-5615, Lotus part number CT7QWNA
• For information on coexistence between, and migration from, Novell
GroupWise to Lotus Domino Release 4.x, refer to the following redbook:
Lotus Notes and Domino: The Next Generation in Messaging — Moving from
Novell GroupWise to Lotus Notes and Domino, IBM form number
SG24-5321, Lotus part number CT7NNNA
• For information on coexistence between, and migration from, Lotus
cc:Mail to Lotus Domino Release 4.x, refer to the following redbook:
The Next Step in Messaging: Upgrade Case Studies for Lotus cc:Mail to Lotus
Domino and Lotus Notes, IBM form number SG24-5100, Lotus part
number 12992
The Team That Wrote This Redbook

This redbook was produced by a team of specialists working at the
IBM/Lotus Integration Center in Westlake, Texas, on behalf of the
International Technical Support Organization at Lotus Development in
Cambridge, Massachusetts, USA.
Siva Kumar is a Technical Consultant for Lotus Development in the Asia
Pacific region. He specializes in mail migration and coexistence solutions
and provides pre-sales support for the Lotus Enterprise Business team. He
has worked on many major projects involving the migration of customers to
Lotus Domino. Siva has also more than two years of experience as a
Messaging Consultant providing pre-sales support for Soft-Switch products
in Lotus. Siva Kumar is a CLP Domino Application Developer.
Marion Hawker is a Technical Marketing Support Representative in the
IBM/Lotus Integration Center in Westlake, Texas. She is a member of the
Domino Messaging Integration team. Before joining that team, she was a
vi Moving from Microsoft Mail to Lotus Notes and Domino
project manager at IBM’s ITSO at Lotus Development, Cambridge,
Massachusetts. Lately, she has been managing redbook projects on behalf of
the Cambridge ITSO out of Westlake, Texas. Marion Hawker is a CLP
Domino Systems Administrator and a certified Project Management
Professional.
We would like to thank the following people for their support and guidance
throughout the production of this book:
• Binary Tree, Inc., in particular, Vadim Gringolts
• Graphic Services, Lotus North Reading
• Dennis Kemmerer, Lotus Development
• Scott Purdy, IBM/Lotus Integration Center, Dallas
Comments Welcome
Your comments are important to us!
We want our redbooks to be as helpful as possible. Please send us your
comments about this or other redbooks in one of the following ways:
• Fax the evaluation form found at the back of this book to the fax number
shown on the form.
• Use the online evaluation form found at
• Send your comments in an Internet note to

redbook@us.ibm.com
Preface vii
Chapter 1
Introduction
If you are currently planning to move from your existing LAN-based

messaging system to a different messaging environment, you are probably
faced with a wealth of choices in the area of messaging migration tools, and
a variety of methodologies you can use to get from here to there. It can be
overwhelming!
Have you ever struggled with trying to find the tools that will enable you to
coexist between your current messaging system and the one you are planning
to move to? Or are you trying to determine which is a suitable migration tool
that will allow you to perform a single-step migration of your users and their
data?
We hope that this book will help you find a solution to meet your needs.
Our Objective
This book was written to demonstrate how customers can move from an
existing messaging infrastructure based on Microsoft Mail to the power of a
Lotus Domino Release 5.0 messaging environment.
To accomplish this goal, we considered two strategies.
• A strategy whereby we could migrate all user information without first
establishing a coexistence environment between the existing messaging
infrastructure, in our case Microsoft Mail, and the messaging system that
the customer is moving to, in our case Lotus Domino. Here the major
consideration is finding a tool which will migrate all the data at once.
• Another equally valid strategy is to perform a phased migration of users
and their data by setting up a coexistence environment that enables an
exchange of messages between Microsoft Mail and Lotus Domino during
the migration phase. This strategy requires identifying both the migration
and coexistence tools available to assist in a process that can last for a
period of time, depending on the customer environment.
These two strategies were the guideposts used to investigate which tools to
apply.
1
Our Scope
There are a multitude of options available today. There are options for very
small migration efforts, options for the more typical migration efforts, for
example, a messaging environment of between 100 to 1,000 users, and finally,
there are options for those ‘industrial-strength’ migration efforts. We limited
our scope to those tools which would best address the needs of the small to
typical migration effort.
Coexistence Tools
In the area of coexistence, the objective was to consider both vendor-provided
tools and third-party tools. We discussed the Microsoft Mail SMTP Gateway
as well as two coexistence tools provided by Binary Tree, Inc.
We determined that we could not provide a document which would be of
significant value in those very large, industrial-strength environments. There
are simply too many variables to consider and most likely they would not
apply in all environments. Therefore, the Lotus Messaging Switch (LMS) was
determined to be outside the scope of this redbook.
Migration Tools
In the area of migration, we covered the administrator-driven and user-based
migration tools provided by Lotus Domino Release 5.0.
We also documented the migration tool offered by Binary Tree, Inc. to migrate
Microsoft Schedule+ 1.0 data to Lotus Domino Calendaring & Scheduling.
Special Considerations
This redbook documents third-party products for coexistence and migration. By
including them in this document, IBM/Lotus do not solely endorse these products for
use in this type of environment. Other third-party products may be available that
perform similar or equivalent functions.
2 Moving from Microsoft Mail to Lotus Notes and Domino

Other Redbooks
This redbook is one in a series of redbooks documenting the migration from a
LAN-based messaging system to Lotus Notes and Domino. The other books
available are as follows:
• The Three Steps to Super.Human.Software: Compare, Coexist, Migrate. From
• Lotus Notes and Domino: The Next Generation in Messaging — Moving from
• The Next Step in Messaging: Upgrade Case Studies for Lotus cc:Mail to Lotus
Domino and Lotus Notes, IBM form number SG24-5100, Lotus part number
12992
Chapter 1: Introduction 3
Chapter 2
Microsoft Mail and Lotus Domino
This chapter gives an overview of Microsoft Mail and Lotus Domino.

It covers the following topics:
• What is Microsoft Mail
• Network design aspects of Microsoft Mail
• Comparing the infrastructure components of Lotus Domino and
Microsoft Mail
• Choosing a coexistence tool
• Choosing a migration tool
• Summary
What Is Microsoft Mail?

Microsoft Mail is a LAN-based electronic messaging system. It provides
users with the ability to send and receive electronic messages. Microsoft Mail
includes two components: the Microsoft Mail postoffice and the Microsoft
Mail client.
Network Design Aspects of Microsoft Mail

In the following, we will discuss terms and concepts used in Microsoft Mail.
We will also cover aspects related to the Microsoft Mail network design to
give you an idea of what it looks like.
Network and Postoffice Concepts in Microsoft Mail

Microsoft Mail users have access to a collective mail-drop facility called a
postoffice. The postoffice that is created when you install Microsoft Mail is
called the local postoffice. You can create additional postoffices called
external postoffices. The mail transfer between the different postoffices is
done by a program called External.
Your LAN may service a single postoffice or many postoffices. Every
postoffice has an administrator, who takes care of the administrative tasks
that allow users to communicate with each other.
5
Every Microsoft Mail postoffice is associated with a network name. The
network name and postoffice name are entered during the Microsoft Mail
installation and setup process.
Name Architecture
The Microsoft Mail users are defined by a network name, a postoffice name
and a mailbox name. The general format is Network/Postoffice/Mailbox.
Each segment of the name can be up to ten characters long.
Logical Network Design

In the following, we will show you some examples of possible Microsoft
Mail network configurations.
Scenario 1
This scenario shows four postoffices in one network. The external program
transfers the mail between these postoffices.
PO1
MS Mail Network: NET1
PO2 LAN PO4
External
PC
PO3

Scenario 2
This scenario shows two Microsoft Mail networks with multiple postoffices
in each network.
PO1
SF
PO2 PO3
LAN
MS Mail Network: SFNET External

PC
External
PC
NY
PO2
LAN
MS Mail Network: NYNET
PO1
Chapter 2: Microsoft Mail and Lotus Domino 7

Mail Routing in Microsoft Mail
In Microsoft Mail, users can send e-mail to other users in the same postoffice
or in an external postoffice. The following sections explain how mail routing
works in an Microsoft Mail environment.
Sending Mail to Users in the Same Postoffice

When you send e-mail to a user in the same postoffice where your mailbox is
located, the mail is delivered by the client directly to the recipient’s mailbox.
MS Mail
User 1
MS Mail
Postoffice
MS Mail
User 2
Sending Mail to Users in External Postoffices

All postoffices other than the local postoffice are called external postoffices.
The following steps describe how mail routing works when a user in a local
postoffice sends mail to another user in an external postoffice:
1. A user in a local postoffice (Postoffice 1) sends e-mail to another user
whose mailbox is located in an external postoffice (Postoffice 2).
2. The mail is placed in the external postoffice’s queue.
3. The external program picks up the mail from the queue and delivers it to
the user’s mailbox in the external postoffice.
Note The external program runs on a dedicated DOS machine, and can
be run manually or scheduled to run automatically. A multi-session
version of External is available for OS/2.

There can also be two external machines talking with each other.
MS Mail External MS Mail

Postoffice 1 PC Postoffice 2
MS Mail MS Mail
User 1 User 2
Comparing the Infrastructure Components of Microsoft Mail

and Lotus Domino
The following table compares the infrastructure components of Lotus
Domino and Microsoft Mail.
Description MS Mail Equivalent Lotus Domino Equivalent
Postoffice/Server Postoffice Domino Server
Client MS Mail Client Lotus Notes Client
Mailbox Mailboxes (.MMF and Mail files (.NSF)
other files)
Transferring messages External Mail Program Domino Mail Router (MTA)
Address Book Global Address List Domino Directory
Directory Synchronization Dispatch Program Replication Process
Process

Choosing a Coexistence Tool
The following are some of the coexistence tools available for interconnecting
Microsoft Mail and Lotus Domino.
• SMTP connection
• Third-party gateway such as the TFS Gateway by TenFour, Inc.
• Lotus Messaging Switch (LMS)
Choosing a coexistence tool depends upon the following factors:
• Total number of e-mail users in the organization
• How long do you expect the coexistence phase to last
• Do you want automatic directory synchronization
• Expected mail traffic between Microsoft mail and Lotus Domino
networks
• Mail delivery confirmation
The following table is designed to give you some general guidelines:
Description SMTP Connection TFS Gateway LMS
Total e-mail users < 1000 < 2500 more than 2000
Coexistence duration 0 to 12 months 0 to 24 months 0 to permanent
Directory synchronization No Yes Yes
Mail traffic 500 to 2500 500 to 2500 5000 to 10000
messages per day messages per day messages per day
Mail delivery No Yes Yes
confirmation
Coexistence Tools
This redbook covers the following tools providing coexistence between
Microsoft Mail and Lotus Domino:
• Microsoft Mail SMTP Gateway
• MS Mail AutoForward, offered by Binary Tree, Inc.
• Lotus Notes Directory Transporter for Microsoft Mail SMTP Gateways,
offered by Binary Tree, Inc.

Choosing a Migration Tool
When choosing a migration tool, you may first want to consider which type
of migration process is suitable for your environment.
Single-Step Migration Process

Single-step migration means a complete migration from a Microsoft Mail
environment to Lotus Domino and Lotus Notes, without a transitional
period of coexistence between the two environments. Applying a single-step
migration process also means that there is no need for gateways to
interconnect Microsoft Mail and Lotus Domino.
A single-step migration process can usually be completed successfully for an
organization that meets the following criteria:
• It has fewer than 500 users.
• It has migration tools to assist in the conversion of user mailboxes to
Lotus Domino.
• The migration process can be performed in an organized fashion.
If the organization generally meets these conditions, it can use the
single-step migration process.
Long-Term Coexistence and Migration

Any long-term migration will require both the old Microsoft Mail and the
new Lotus Domino environments to coexist. The coexistence period can vary
from a few weeks to a few years. During this coexistence period, gateways
need to be used as a coexistence tool. The gateways will allow the users in
both environments to send messages to each other. Organizations that meet
the following criteria will probably need a long-term coexistence planning:
• There is a large number of users in the Microsoft Mail environment.
• There are organizational units in multiple locations that it would be
difficult to migrate concurrently to Lotus Domino.
• The hardware required for a migration to Lotus Notes is not yet fully in
place.
Migration Tools
This redbook covers the following Microsoft Mail to Lotus Domino
migration tools:
• Lotus Domino Release 5.0 migration tools
• User-based tool
• Admin-based tool
• Binary Tree user-based migration tool for Microsoft Schedule+ 1.0
Summary
In this chapter, we looked at network and postoffice concepts in Microsoft
Mail. We showed you some examples of possible Microsoft Mail network
configurations, and briefly discussed how mail routing works in Microsoft
Mail.
Next, we compared the infrastructure components as they apply to Microsoft
Mail and Lotus Domino.
Finally, we gave some hints and tips regarding the choice of a coexistence
and migration tool that meets your requirements.

Chapter 3
Microsoft Mail and Lotus Domino Coexistence:
Open Environment Using SMTP
The SMTP (Simple Mail Transfer Protocol) Gateway software allows an

electronic mail program to send messages to, and receive messages from,
other users on the Internet. An SMTP-to-SMTP connection can also be set up
if the organization requires an internal connection between two different
messaging systems.
This chapter discusses the following topics:
• Microsoft Mail SMTP Gateway and Domino SMTP mail routing
• Understanding the SMTP environment
• Planning and designing the SMTP network
• Installing the Microsoft Mail SMTP Gateway
• Installing and configuring Domino Release 5.0 SMTP mail routing
• Setting up the Microsoft Mail SMTP Gateway
• Using the Microsoft Mail SMTP Gateway and Domino SMTP mail
routing
• MS Mail AutoForward, offered by Binary Tree, Inc.
• Lotus Notes Directory Transporter for Microsoft Mail SMTP Gateways,
offered by Binary Tree, Inc.
• Summary
Note At the time of writing this redbook, we used build 166 of the Lotus
Domino Release 5.0 server and a Lotus Notes Release 5.0 client. Some
features described here may have changed since the product has become
available.
13
Microsoft Mail SMTP Gateway and Domino SMTP Mail Routing
The following components are required to connect Microsoft Mail and Lotus
Domino.
Microsoft Mail SMTP Gateway

The Microsoft Mail Gateway to SMTP allows a Microsoft Mail system to
exchange mail with another mail system using an SMTP connection. When
the SMTP connection is operational between Microsoft Mail and the other
mail system, the users in both mail systems can send and receive mail
through this direct SMTP connection.
Note In our environment, we used the Microsoft Mail Gateway to SMTP
Version 3.
The following figure shows a typical Microsoft Mail to SMTP connection.
The Microsoft Mail Gateway for SMTP runs on a dedicated PC.
Internet
MS Mail MS Mail MS Mail
Client Postoffice SMTP Gateway
Lotus Domino Release 5.0 SMTP Mail Routing

The Domino Release 5.0. server can route mail using both SMTP and Notes
routing. Users can send mail in Notes format or in MIME format.
The mail routing begins when a user sends a message from a client that is
connected to the Domino server. The message is transferred from the user’s
client to the MAIL.BOX database on the user’s mail server. The Router
(server task) checks the address in the message to determine how to route it
to the recipient and whether to use SMTP or Notes routing.
Here are some examples of how to set up Domino mail routing for SMTP.

Example 1: Using One Server for all Internet (SMTP) Messages
The following figure shows how to use one Domino server to route all SMTP
messages:
Lotus Domino R5 Server
Mail-01/Acme

Mailhub/Acme
Lotus Notes
Client
Internet
Lotus Notes
Client
Mail-02/Acme
In this example, a single Domino server, MAILHUB/ACME, handles

messages from the Acme organization destined for other Internet domains
(external addresses) and receives all mail addressed to the Acme Internet
domain (acme.com).
If a user on either one of the two Acme internal mail servers,
MAIL-01/ACME or MAIL-02/ACME, sends a message to an external
address — one with a domain name other than acme.com — the server
routes the message to MAILHUB/ACME. This server can then route the
mail to external domains.
The two internal mail servers can route Internet mail to the server routing
the SMTP (in our case, MAILHUB/ACME) using one of the following.
• Notes routing with a Foreign SMTP domain document and SMTP
connection document linking to MAILHUB/ACME
• SMTP routing, with MAILHUB/ACME confiured as the relay host.
Any mail from an external Internet domain — one other than acme.com — is
routed to MAILHUB/ACME, which is listed in the Domain Name Service
(DNS) as the host for acme.com. Once the mail reaches MAILHUB/ACME,
the server routes it to its destination.
Chapter 3: Microsoft Mail and Lotus Domino Coexistence: Open Environment Using SMTP 15
Example 2: Using all Servers to Route Outbound Mail and One Server
to Route Inbound Mail
The following figure shows how all the Domino servers are used to route out-
bound SMTP mail and only one server is used to route inbound SMTP mail.
SMTP
Lotus Notes
Outbound
Client
Mail-01/Acme
SMTP
Inbound & Internet
Lotus Notes Outbound
Client
Mail-02/Acme
SMTP
Outbound
Lotus Notes
Client
Mail-03/Acme
In this example, Acme has three mail servers: MAIL-01/ACME,

MAIL-02/ACME, and MAIL-03/ACME. Each server can route messages
from the Acme organization destined for other Internet domains (external
addresses). One server, MAIL-02/ACME, receives mail addressed to the
Acme Internet domain (acme.com).
If a user on one of the mail servers sends a message to an external address —
one with a domain other than acme.com — the server looks up the
destination domain in the DNS, connects to the destination server over
TCP/IP, establishes an SMTP connection, and transfers the message.
Any mail from an external Internet domain — one other than acme.com — is
routed to MAIL-02/ACME. The DNS lists MAIL2-E/EAST/ACME as the
host for acme.com. Once the mail reaches MAIL-02/EAST/ACME, the
server routes the message to its destination.
Since each server can send messages directly to external domains, no relay
host, foreign SMTP domain documents, or SMTP connection documents are
needed.

Understanding the SMTP Environment
The following section discusses a typical SMTP connection between Lotus
Domino and Microsoft Mail, and describes how mail routing works between
the two environments.
A Typical SMTP Connection between Domino and Microsoft Mail

The following figure explains how a typical SMTP connection between Lotus
Domino and Microsoft Mail can be set up.
Lotus Notes MS Mail
Network Network
SMTP
Lotus Notes
Outbound
Client
Mail-01/Acme
SMTP
Inbound &
Lotus Notes Outbound
Client MS Mail MS Mail MS Mail
Lotus Domino R5 Server SMTP Gateway Postoffice Client
Mail-02/Acme
SMTP
Outbound
Lotus Notes
Client
Mail-03/Acme
The SMTP connection can be used to connect the mail system to the Internet
or it can be used for an internal connection between two different mail
systems.
The Microsoft Mail SMTP Gateway connects directly to the Lotus Domino
Release 5.0 server via a TCP/IP network as shown in the previous figure.
Since all the Lotus Domino Release 5.0 servers can route SMTP messages in
the above example, all the Domino servers can connect to the Microsoft Mail
SMTP gateway to transfer SMTP messages which are destined to the
Microsoft Mail users.
The general format of SMTP addressing is:
username@domain1.domain2.domain3.…
The username is the mail ID of the user. The domain name specifies the host
address of the SMTP Gateway. The Microsoft Mail SMTP Gateway and the
Lotus Domino Release 5.0 server are assigned separate IP addresses and a
host name (including the domain name). In our example let’s assign the
following:
Domain name for Lotus Notes network: notes.acme.com
Domain name for Microsoft Mail network: msmail.acme.com
The following will be the users’ SMTP e-mail addresses:
Microsoft Mail User: msmailuser@msmail.acme.com
Lotus Notes Use: notesuser@notes.acme.com
How Mail Routing Works Using SMTP

The following section covers how message routing works between Microsoft
Mail and Lotus Domino using the SMTP connection.
Lotus Notes Lotus Domino R5 Server Lotus Domino R5 Server

Client Mail-01/Acme Mailhub/Acme
MS Mail MS Mail MS Mail

Client Postoffice SMTP Gateway
Lotus Domino to Microsoft Mail

These steps describe how mail is routed from a user in Lotus Domino/Notes
to a user in Microsoft Mail:
1. A Lotus Notes user composes a mail message to a Microsoft Mail
recipient.
2. The Lotus Notes user sends the message.
3. The Lotus Notes user’s client software uses Notes protocols to deposit the
message into the MAIL.BOX database on the user’s Domino mail server.

4. The Domino Mail Router finds the message in MAIL.BOX and
determines where to send the message for each recipient. The Router
calculates the next “hop” for the message on the path to its recipients
and uses the better protocol — either SMTP or Notes routing — to
transfer the message.
5. Using SMTP routing, the Router connects to the destination Microsoft
Mail SMTP Gateway and transfers a copy of the message.
6. The Microsoft Mail SMTP Gateway receives the message and delivers it
to the recipient’s Postoffice queue.
7. The message is then transferred from the queue to the Microsoft Mail
user’s mail file.
8. The Microsoft Mail recipient uses a client to read the message, which is
stored in his/her mail file.
Microsoft Mail to Lotus Domino

These steps describe how mail is routed from a user in Microsoft Mail to a
user in Lotus Domino/Notes:
1. A Microsoft Mail user composes a mail message for a user in Lotus
Domino. When the user clicks Send, the mail is transferred to the
Microsoft Mail postoffice.
2. The mail is moved to the SMTP queue for that postoffice.
3. The Microsoft Mail Gateway for SMTP establishes an SMTP connection
to the designated Lotus Domino Release 5.0 server. The Microsoft Mail
Gateway then transfers the mail to the Lotus Domino Release 5.0 server.
4. The Lotus Domino Mail Router reads the mail from MAIL.BOX and
delivers the mail to the user’s mail file.
5. The Notes user opens the mail file to view the SMTP mail received from
the Microsoft Mail user.
Planning and Designing the SMTP Network

This section discusses aspects related to planning for setting up an SMTP
connection between Microsoft Mail and Domino. We will also provide a case
study on how to design an SMTP network between the Microsoft Mail and
Domino environments.
Hardware and Software Requirements

The following section covers hardware and software requirements for the
Microsoft Mail Gateway to SMTP and for the Lotus Domino Release 5.0
server.
Microsoft Mail Gateway to SMTP
The hardware requirements for the Microsoft Mail Gateway to SMTP are as
follows:
Processor Intel Pentium-based
Operating System MS DOS or PC DOS V3.x or higher
RAM 8MB
Hard Disk Space 5 to 10MB
Network Adapter Any network adapter supported by one of the following:
• Microsoft TCP/IP for DOS
• FTP PC/TCP for DOS
• Novell LAN Workplace for DOS with TCP/IP
• WIN/TCP for DOS RunTime (Version 4.1) from the
Woollongong Group
The software requirements are as follows:

Protocol Type Description
TCP/IP One of the following versions of TCP/IP software has to
be installed:
• Microsoft TCP/IP for DOS
• FTP PC/TCP for DOS
• Novell LAN Workplace for DOS with TCP/IP
• WIN/TCP for DOS RunTime (Version 4.1) from the
Woollongong Group
IPX IPX/SPX has to be installed.
Note Refer to the Microsoft Mail Gateway for SMTP Administrator’s Guide for
more details.
Lotus Domino Release 5.0 Server

Refer to Lotus Domino Release 5.0 documentation for the recommended
configuration.
Microsoft Mail Postoffice Requirements

Microsoft Mail Server Version 2.1 or later is required.
Microsoft Mail Naming Considerations

When you set up a Microsoft Mail Gateway for SMTP, the default mapping
for the SMTP address is in the following format:
MS Mail Address: Network/Postoffice/Userid
SMTP Address: userid@postoffice.network.com

Consider the following with regard to the SMTP address components:
• The postoffice name is mapped to domain1.
• The network name is mapped to domain2.
• The .com element is the domain suffix.
The Microsoft Mail alias of any user can be sent along with the SMTP user
address. The following shows an example of a name that can cause
problems:
<John Smith, Mkting/NY> jsmith02@msmail.acme.com
The Microsoft Mail Alias name can contain special characters such as a
comma (,) or a semicolon (;). In Domino, these characters have a special
meaning, for example, commas and semicolons are name separators. When
planning for Microsoft Mail to Domino coexistence, be sure to remove all
those special characters from the Microsoft Mail user’s alias.
Case Study: Designing the SMTP Network

So far we have discussed in general how to set up an SMTP connection
between Microsoft Mail and Lotus Domino. In this section we will discuss in
more detail how to connect Microsoft Mail and Lotus Domino using the
SMTP Gateway and the Lotus Domino Release 5.0 server.
The following case study explains the current setup of the Microsoft Mail
environment in the ACME organization and the new setup for Lotus
Domino. We will show you how to connect these two environments.
Microsoft Mail Environment

The ACME Microsoft Mail environment looks like this:
ACMEHUB
Directory Synchronization
Network: ACME
Server
ACMESF ACMELA ACMENY
User User User User User User
ACME currently has four Microsoft Mail postoffices, one hub postoffice and
3 downstream postoffices:
• ACMEHUB is the hub postoffice for mail routing within Microsoft Mail
and also functions as the directory synchronization server.
• ACMESF is a postoffice hosting the user mailboxes in the San Francisco
office. It also functions as a directory synchronization requester.
• ACMELA is a postoffice hosting the user mailboxes in the Los Angeles
• ACMENY is a postoffice hosting the user mailboxes in the New York
• All the four postoffices are set up as shared directories on Novell
NetWare servers.
Lotus Domino Environment

ACME’s new Lotus Domino setup looks like this:
Domain: ACME MAILHUB/SF/ACME
MAIL1/SF/ACME MAIL2/LA/ACME MAIL3/NY/ACME
User User User User User User
ACME is planning for one Domino domain called ACME and four Domino
servers:
• MAILHUB/SF/ACME is the Domino hub server responsible for mail
routing within Lotus Domino.
• MAIL1/SF/ACME is the home server for the Notes users in the San
Francisco office.
• MAIL2/LA/ACME is the home server for the Notes users in the Los
Angeles office.

• MAIL3/NY/ACME is the home server for the Notes users in the New
York office.
All the Domino servers are set up in a Windows environment. They replicate
their Domino directories with the MAILHUB server.
Planning for an SMTP Connection

Using the above information about the existing Microsoft Mail environment
in the ACME organization and the new Lotus Domino environment, we can
now plan to interconnect Microsoft Mail and Lotus Domino using an SMTP
connection.
Note In ACME’s environment, we have a hub Microsoft Mail postoffice
and a hub Domino server for routing messages. This makes it easy for us to
plan for interconnection. If you do not have a hub Microsoft Mail postoffice
or a hub Domino server, it is advisable to set up a hub in each environment.
Otherwise, you have to set up one Microsoft Mail SMTP Gateway for each
SMTP Naming for the Microsoft Mail Postoffices

We selected the following SMTP naming convention for the different
Microsoft Mail postoffices:
ACMESF Postoffice:
MS Mail address: ACME/ACMESF/userid
SMTP address: usersid@ACMESF.ACME.COM
ACMELA Postoffice:
MS Mail address: ACME/ACMELA/userid
SMTP address: usersid@ACMELA.ACME.COM
ACMENY Postoffice:
MS Mail address: ACME/ACMENY/userid
SMTP address:. usersid@ACMENY.ACME.COM
SMTP Naming for the Domino Domain

We selected the following SMTP naming convention for the Domino domain:
Domain Name: ACME
Organization Unit Name : SF
Notes address: User Name/SF/ACME@ACME
SMTP address: user_name@ACME.COM
Domain Name: ACME
Organization Unit Name : LA
Notes address: User Name/LA/ACME@ACME
Domain Name: ACME

Organization Unit Name : NY
Notes address: User Name/NY/ACME@ACME
The following figure shows the SMTP connection between Microsoft Mail
and Lotus Domino:
MAILHUB/SF/ACME
MS Mail SMTP
gateway
SMTP
ACMEHUB Notes and MTP mail over the Notes routing

Installing the Microsoft Mail Gateway to SMTP

The following steps show you how to install the Microsoft Mail Gateway to
SMTP. First, let us look at the pre-installation tasks required for the gateway.
Pre-installation Tasks
These are the pre-installation tasks:
1. Install and set up the PC that will run the Microsoft Mail Gateway to
SMTP.
2. Install and set up MS-DOS.
3. Install and set up the client network protocol to connect to the Microsoft
Mail postoffice.

4. Install and set up one of the following TCP/IP software for the SMTP
connection:
• Microsoft TCP/IP
• FTP TCP/IP
• Novell TCP/IP
• Excelan TCP/IP
• Woollongong TCP/IP
Note The Microsoft Mail Gateway to SMTP software works only with
one of the above TCP/IP software packages.
5. Make sure that the Microsoft Mail postoffice MAILDATA directory has
been mapped.
6. Ping to the DNS server or the TCP/IP gateway or to the Lotus Domino
server that connects the SMTP gateway to verify the connection.
7. Get the domain name for the Microsoft Mail SMTP network or assign a
domain name.
8. Get the TCP/IP address and the host name for the PC that runs the
Microsoft Mail Gateway to SMTP.
The Microsoft Mail Gateway to SMTP runs on a dedicated PC. There are two
components for the Microsoft Mail Gateway to SMTP software. They are:
• Disk 1: The Gateway component of the Microsoft Mail Gateway to
SMTP. The Gateway component includes the executable files for the
SMTP Gateway.
• Disk 2: The Gateway Access component of the Microsoft Mail Gateway
to SMTP. The Gateway Access component includes the files that are
used by the gateway postoffice and the downstream postoffices to access
the gateway host.
Note The gateway postoffice is the postoffice where the Gateway
component is installed. This is generally the hub postoffice. The gateway
postoffice stores all the SMTP gateway configuration. The SMTP Gateway
administration is done on the gateway postoffice.
In addition to running the Gateway component, the gateway postoffice (hub
postoffice) also requires the Gateway Access component. This Gateway
Access component also needs to be installed on the downstream postoffices.
Installing the Microsoft Mail Gateway Component

Follow these steps to install the Microsoft Mail Gateway to SMTP on the
gateway postoffice machine:
1. Insert the Gateway component disk 1 into drive A.
2. Type install and press Enter. The install program starts and the
following window is displayed:
3. Press Enter to continue. The following window is displayed:
4. Enter the MAILEXE directory path of the gateway Microsoft Mail

postoffice.
5. Enter the MAILDATA directory path of the gateway Microsoft Mail post
office.

6. Enter the type of TCP/IP software that has been installed on the PC.
7. You will be prompted with Do You Wish to make any changes to the
above choices (Y/N). Press N to continue. The Gateway component files
are installed. When the installation is complete, the following message is
displayed:
Microsoft Mail Gateway to SMTP installed
This completes the Gateway component installation.
Installing the Gateway Access Component on the Gateway Postoffice

Follow these steps to install the Gateway Access component on the gateway
postoffice machine:
1. Remove the disk from the diskette drive and insert the Gateway Access
component disk into drive A.
2. Type install and press Enter. The installation program starts and the
following window is displayed:
3. Press Enter to continue. The following window is displayed:
4. Enter the directory path of the MAILDATA directory of the postoffice.

5. You will be prompted with Do You Wish to make any changes to the
above choices (Y/N). Press N to continue. The following window is
displayed showing the file names that are being installed:

The Gateway Access component files are installed. When the installation is
complete, the following message is displayed:
Microsoft Mail Gateway Access for SMTP installed
This completes the Gateway Access component installation.

Important Install the Gateway Access component on every downstream
postoffice. Make sure you have obtained the required number of licenses.
Installing the Gateway Access Component on a Downstream Postoffice

Follow these steps to install the Gateway Access component on the
downstream postoffices:
1. Insert the Gateway Access component disk into drive A.
2. Type install and press Enter. A screen appears listing the items required
by the install program.
3. Press Enter to continue.
4. The next screen prompts you to enter the drive and path where the
Microsoft Mail data files are located. Enter the MAILDATA directory
path of the downstream Microsoft Mail postoffice and press Enter.
5. You are prompted to enter the network name:
• If your downstream postoffice is directly connected to the gateway
postoffice, enter the network name of the gateway postoffice and
press Enter.
• If your downstream postoffice is not directly connected to the
gateway postoffice, enter the network name of the forwarding
postoffice and press Enter.
6. Next, you are prompted to enter the postoffice name:
• If your downstream postoffice is directly connected to the gateway
postoffice, enter the postoffice name of the gateway postoffice and
press Enter.
• If your downstream postoffice is not directly connected to the
gateway postoffice, enter the postoffice name of the forwarding
postoffice and press Enter.
7. You are prompted with Do You Wish to make any changes to the above
choices (Y/N). Press N to continue. The Gateway Access component files
are installed. When the installation is complete, the following message is
displayed: Microsoft Mail Gateway Access for SMTP installed.
This completes the Gateway Access component installation.
Setting up the Microsoft Mail SMTP Gateway
The following section covers how to set up the Microsoft Mail Gateway to
SMTP.
All the setup for the Microsoft Mail Gateway to SMTP is done on the
gateway postoffice. For example, in ACME’s Microsoft Mail environment,
the setup is done on the ACMEHUB postoffice.
Follow these steps:
1. At the MS DOS prompt, change to the drive where you have the
Microsoft Mail Admin programs installed.
2. Type one of the following commands:
• admin, if your MAILDATA directory is mapped to the M drive.
• admin -d<drive letter>, where <drive letter> is the drive name which
has been mapped to the MAILDATA directory.
The Admin program starts and prompts you for the Admin mailbox
name.
3. Enter the Admin mailbox name and press Enter.
4. Enter the admin’s password and press Enter. The Admin menu is
displayed.

5. Choose the Gateway option from the mail menu. The Gateway menu is
displayed.
6. Choose Setup from the SMTP Gateway menu. The following window is
displayed:
7. In the Domain suffix field, type the domain suffix for the Microsoft Mail
SMTP environment and press Enter.
Note The domain suffix will be added to the sender’s address of the
SMTP mail that is sent from the Microsoft Mail network. In ACME’s
environment, the domain suffix .com and the network name will be
added to the postoffice to form the complete SMTP domain name for
the Microsoft Mail SMTP environment. For the ACMESF postoffice,
for example, the following will be the default full domain suffix:
userid@acmesf.acme.com.
8. In the Internet Name of Gateway field, enter the fully qualified host
name of the PC that runs the SMTP Gateway and press Enter.
9. In the IP address of SMTP Router field, enter the IP address of the
machine that runs the Lotus Domino Release 5.0 server which has the
outbound SMTP mail routing enabled and press Enter.
10. You will be prompted with SMTP Configuration Yes No. Choose Yes to
save the configuration.
11. If you do not see the SMTP menu, choose Gateway - SMTP from the
Admin menu.
12. Choose Postoffices from the SMTP menu. The following window is
displayed:
13. Enter the Microsoft Mail network name and press Enter.
14. Enter the postoffice name and press Enter.

15. Choose Yes when prompted to Create SMTP Local Postoffice.
16. Repeat the previous steps for all the postoffices in the Microsoft Mail
environment.
Note The Microsoft Mail Gateway to SMTP can receive SMTP mail for all
the postoffices listed in this SMTP postoffice list. If you have not created an
SMTP postoffice for a Microsoft Mail postoffice in your Microsoft Mail
network, the users in that postoffice cannot receive any SMTP mail.
Remember that for SMTP mail, the Gateway Access component has to be
installed in all the postoffices. If the Gateway Access component is not
installed in a postoffice, the users in that postoffice cannot send any SMTP
mail.
This completes the setup for the SMTP Gateway in the Microsoft Mail
network.
Installing and Configuring Domino Release 5.0 SMTP Routing

The following steps show you how to install and configure SMTP mail
routing in Lotus Domino Release 5.0. First, let us look at the pre-installation
tasks required for SMTP mail routing
These are the pre-installation tasks:
1. Install and set up the machine that runs the Lotus Domino server.
2. Install and set up the operating system.
3. Set up the network protocol to connect to the Notes network. If you are
using TCP/IP, go to step 6 now.
4. Set up the TCP/IP protocol for the SMTP connection.
5. Set up the domain name for the Domino SMTP network or assign a
domain name.
6. Set up the TCP/IP address, the domain name and the host name for the
PC that runs the Domino server.
Note When setting up the Domino server for SMTP mail routing the
server’s host name will be formulated using the TCP/IP configuration.
In our example the domain name of Notes is ACME and the TCP/IP
domain name is set up as acme.com.
7. Install the Lotus Domino Release 5.0 server.
Installing and Setting up Domino SMTP Routing
This section describes the steps required to install and set up the Domino
server for SMTP mail routing using the following design:
MAILHUB/SF/ACME
MS Mail SMTP
gateway
SMTP
ACMEHUB Notes and MTP mail over the Notes routing

When you install the Lotus Domino Release 5.0 server, the SMTP mail
routing function is installed along with the Domino server.
In our case study we will need to configure the MAILHUB/SF/ACME
server to route inbound and outbound SMTP messages. All the other servers
will route SMTP messages over Notes routing to the MAILHUB server. The
following needs to be done:
1. Enable SMTP mail routing for inbound and outbound SMTP messages
on the MAILHUB server.
Enabling SMTP mail routing can be performed when setting up the
Domino server or using the Domino Administrator.
2. Set up the other servers to route SMTP messages over Notes routing to
MAILHUB. The following steps are required:
i. Creating a Foreign Domain document for SMTP mail routing.
ii. Creating a connection document for connecting every server to
MAILHUB.
iii. Configuring the Message settings for every server to route SMTP
mail.

Enabling SMTP Mail Routing for MAILHUB during Server Setup
The following instructions show you how to enable SMTP mail routing when
you set up the Domino server.
After installing the Domino server, do the following:
1. Start the Domino server. The Domino setup menu is displayed.
2. Select either First Domino Server if you are setting up the first server, or
Additional Domino Server if this is an additional server.
Note If you select to install an additional server, you must register an
additional server first.
3. Proceed to the next step by clicking the > button. The following screen is
displayed:
4. Select Advanced Configuration and click the > button to go to the next
screen. The following screen is displayed:
5. In the Internet Mail Packages section, select the SMTP option.

6. Click the > button to go to the next screen. The following screen is
displayed:
7. Enter the data required for the new server and click Finish to complete
the setup.
8. Wait until the setup is completed and then click Save & Quit to quit the
setup.
This completes the steps required to enable SMTP mail routing during the
Domino server setup.
Enabling SMTP Mail Routing for MAILHUB Using the Domino

Administrator
The following instructions show you how to enable SMTP mail routing on
the MAILHUB/SF/ACME server using the Domino Administrator.
Note To use the Domino Administrator for the setup, you must have
installed the Domino Administrator client and set it up to connect to all the
servers in the ACME domain. You will also need the Administrator’s Lotus
Notes ID for performing the steps described in the following:
1. Start the MAILHUB/SF/ACME Domino server.
2. Start the Domino Administrator.
3. Enter the administrator’s password when prompted.
4. In the Domino Administrator, select Administration - Refresh Server
List - Current Domain. All the Domino server names are added to the
All Servers view.
5. Select the All Servers view. The server names available in the ACME
domain are displayed.
6. Click the MAILHUB/SF/ACME server. The Domino Administrator
connects to the MAILHUB/SF/ACME server.
7. Click the Configuration tab.
8. Select the Server view. The following screen is displayed:

9. Click the Current Server Document. The following screen is displayed.
Click the Edit Server button to edit the settings.

10. On the Basics tab, select Enable in the SMTP listener task field.
11. Click Save and Close to save the new configuration.
This completes the steps required to enable the MAILHUB server to handle
inbound and outbound SMTP messages.
Setting up MAILHUB and the other Domino Servers to Route SMTP

Messages
The following steps show you how to set up the Domino servers in the
ACME domain to route all the SMTP messages to the MAILHUB server.
1. In the Domino Administrator, select the MAILHUB server from the All
Servers view.
2. Click the Configuration tab.
3. Choose Messaging - Message Settings. The Messaging Settings for
MAILHUB/SF/ACME dialog box is displayed.
4. Click the Edit Settings button to edit the document.
5. On the Basics tab, select Enabled in the field called SMTP used when
sending messages outside of the local internet domain.
6. Select MIME messages only in the field called SMTP allowed within the
local internet domain.
7. We typed msmailgw.acme.com in the field called Local Internet domain
smart host.
Note A smart host is a host to which SMTP-routed messages are sent
when the message recipient cannot be found in the local Internet
domain’s directory. When a message is received, the Router looks for the
recipient’s address to see if it is in the local Internet domain or in an alias
Internet domain.
If the address cannot be located in the local Internet domain, then the
Router checks the Person document to see where to send the message. If
the Domino network is connected to other mail systems through an
SMTP connection, the users of those mail systems may not be listed in
the Domino directory. In that case you can set up a smart host.
8. In the Host name lookup field, enter one of the following:
i. If you have DNS set up and if you need the Domino server to look
up the DNS for the host name, then select Dynamic lookup only.
ii. If you need DNS and local host file lookup, then select Dynamic then
Local.
9. Click Save and Close to save the new configuration. The following
screen shows our completed configuration setup for the
MAILHUB/SF/ACME server.

Creating a Foreign Domain Document for SMTP Mail Routing
The following steps show you how to set up a Foreign Domain document for
routing the SMTP messages to the MAILHUB server.
In the Domino Administrator, perform these steps:
1. Select the Domains view. The Domain view is displayed.
2. Click the Add Domain button.
3. On the Basics tab, select Foreign SMTP Domain in the Domain type field.
4. Click the Routing tab.

5. Type *.acme.com in the Internet Domain field.
6. Type MAILHUB/SF/ACME in the Internet host field.
Note All the SMTP messages from the other Domino servers in the
ACME domain will be routed to the MAILHUB server over Notes
routing.
7. Click the Save and Close button.
Creating a Connection Document for SMTP Mail Routing

You must create a connection document for every server in the ACME
domain to the MAILHUB server for routing SMTP messages. The following
instructions guide you on how to create an SMTP connection document
between the MAIL1/SF/ACME server to MAILHUB.
1. Select the Connections view.
2. Click the Add Connection button.
3. On the Basics tab, select SMTP in the Connection type field.
4. Type MAIL1/SF/ACME in the Source server field.
5. Select Direct connection in the Connect via field.
6. Type MAILHUB/SF/ACME in the Destination server field. The
following screen shows the connection document for the MAIL1 server
to MAILHUB.

7. Click the Replication/Routing tab.
8. Enter 1 in the Route at once if field.
9. Click the Save and Close button to save the new configuration.
10. For each server in the ACME domain repeat the above steps to create a
connection document to MAILHUB.
Configuring the Message Settings Mail Routing

For each server in the ACME domain, you must configure the message
settings for SMTP mail routing. As an example, the following steps guide
you on how to update the message settings for the MAIL1 server.
1. Select the Server - Configurations view. All the server’s Configuration
documents are shown.
2. Open the MAIL1/SF/ACME Configuration document.
3. Click the Router/SMTP tab.
4. Select MIME messages only in the field called SMTP allowed within the
local internet domain.
5. We typed msmailgw.acme.com in the field called Local Internet domain
smart host.
The following screen shows the configuration for MAIL1 server.
6. Click the Save and Close button to save the new configuration.
7. For each server in the ACME domain, repeat the above steps.
8. Replicate the address book from the MAILHUB server to the other
servers. For example, to replicate the MAILHUB address book to the
MAIL1 server follow these steps:
9. On the MAILHUB Domino server console, enter the command replicate
Mail1 names.nsf.
10. Repeat the above step to replicate to the other servers.
This completes the setup for routing SMTP messages from the Notes
network to the Microsoft Mail network in Acme’s environment.

Using the Microsoft Mail SMTP Gateway and the Domino SMTP
Mail Routing
The following section covers how to use the gateways.
Starting the MAILHUB Domino Server

The SMTP mail routing feature has been enabled on the MAILHUB server.
When the Domino server is started, the SMTP mail routing for both inbound
and outbound messages is also started. Perform these steps to start the
MAILHUB server.
1. On the Domino server console, enter the command show tasks.
2. You must have the following tasks started for SMTP mail routing:
• SMTP Server Idle task
• SMTP Server Listen for connect requests on TCP Port 25
• SMTP Server Control task
Stopping the Lotus Domino SMTP Mail Routing

To stop the Lotus Domino SMTP mail routing, at the MAILHUB Domino
server console, type tell smtp quit.
Starting the Microsoft Mail Gateway to SMTP

The following steps show you how to start the Microsoft Mail Gateway to
SMTP.
1. Start the PC that runs the Microsoft Mail Gateway to SMTP.
2. Switch to the drive that is mapped to the MAILEXE directory.
3. Type smtpmta and press Enter. The Microsoft Mail Gateway to SMTP
starts and displays the started status on the screen.
Stopping the Microsoft Mail Gateway to SMTP

To stop the Microsoft Mail Gateway to SMTP, follow these steps:
1. Press ESC on the keyboard.
2. Press Y to stop the SMTP Gateway.
Sending SMTP Mail between Microsoft Mail and Lotus Domino

The following covers how to send SMTP messages from Microsoft Mail to
Lotus Domino, and from Lotus Domino to Microsoft Mail.
Sending an SMTP Message from Microsoft Mail to Lotus Domino
The following steps show you how to compose a new message in Microsoft
Mail and send it to a Notes user through the SMTP Gateway.
1. Start the Microsoft Mail client.
2. Click Compose.
3. In the To field, enter the SMTP address of the Lotus Notes user. If the
SMTP addresses of the Notes users are entered in the Global Address
List, you can enter the alias name of the user or choose the name from
the Global Address List.
Note In Acme’s Domino SMTP setup, the SMTP domain suffix for the
Domino environment is set to acme.com.
4. Complete the message and click Send to send this message.
Note You can check the Microsoft Mail Gateway to SMTP screen and
the Lotus Domino server window to see whether the message has been
transferred successfully.
Sending an SMTP Message from Lotus Domino to Microsoft Mail

The following steps show you how to compose a new message in Lotus
Notes and send it to a Microsoft Mail user.
1. Start the Lotus Notes client.
2. Open your mail file.
3. Click New Memo on the action bar.

4. In the To field, enter the SMTP address of the Microsoft Mail user.
Note In Acme’s environment, the Microsoft Mail domain suffix is set to

postoffice.network.com (acmesf.acme.com).
5. Complete the memo and click Send on the action bar to send this
message.
MS Mail AutoForward
The following sections describe a mail-forwarding tool provided by Binary
Tree, Inc. The tool is called MS Mail AutoForward.
Business Problem
One of the principal requirements during mail migration from any mail
system to Lotus Notes/Domino is to ensure that once a user is migrated
from the old mail system to Lotus Domino, all subsequent messages sent to
the user are delivered to his/her Lotus Domino mailbox.
Such messages typically represent newly composed mail items, replies to
mail messages previously sent by the user, or mail items sent to distribution
lists, which include the user’s address. Ordinarily, delivery of mail to the
new Lotus Notes mailbox is achieved by using the old mail system’s
function to automatically reroute all mail directed to the old mail address
to the new one.
However, Microsoft Mail does not have a function of automatically rerouting
mail from one mail address to another.
A person managing mail migration from Microsoft Mail to Lotus Domino
must decide on an approach to handle mail sent to a Microsoft Mail address,
which represents a user who has already migrated to Lotus Domino. There
are a few options available:
• Keep the old Microsoft Mail address around and suggest that a user
periodically check the old Microsoft Mail mailbox for mail received after
migration. The user can review such mail and decide whether to
manually forward it to Lotus Domino or remove it. This approach
requires that during a transitional period, which may last for months,
users work with multiple mailboxes.
• Keep the old Microsoft Mail address around and periodically check the
old Microsoft Mail mailbox on behalf of the user for mail received after
migration. Then all such mail can be manually forwarded to Lotus
Domino. Depending on the number of users migrated from Microsoft
Mail to Lotus Domino, this approach requires significant dedication of
administrative resources.
Remove the old Microsoft Mail address and reject all mail sent to it.
Unfortunately, originators of mail are not informed of the real reasons for
mail rejection and may become irritated by the fact that a mail address,
which has always worked, no longer works.
Pursue a third-party solution, such as MS Mail AutoForward from Binary
Tree, Inc.
Product Description
MS Mail AutoForward consists of two components: Microsoft Mail and
Lotus Notes.
A separate Microsoft Mail module is installed and configured for each
Microsoft Mail postoffice, for which automatic mail forwarding is required.
Using configuration screens, an administrator selects users from the
postoffice and enables automatic mail forwarding for them.
A Microsoft Mail module can be installed in Windows 95, Windows 98, or
Windows NT. Even though a separate module is required for each Microsoft
Mail postoffice, multiple instances of MS Mail AutoForward can be run on
the same PC.
A Lotus Notes module is installed and configured as a Lotus Notes Mail-In
Database on a single Lotus Domino server. It does not require any dedicated
hardware.

Product Design and Prerequisites
For each Microsoft Mail postoffice, a corresponding Microsoft Mail module
continuously polls Microsoft Mail mailboxes, which have been designated
for automatic mail forwarding. When new mail items are found, they are
extracted from the Microsoft Mail mailbox, processed, and redirected to a
predefined Lotus Domino Mail-In Database. An agent running against the
database extracts mail items, completes the redirection process, and delivers
mail to an appropriate Lotus Domino user.
If necessary, a notification is sent back to the originator of each mail item to
inform him/her of the mail address change. Proper logging is maintained in
both Microsoft Mail and Lotus Domino, so that a network administrator can
monitor the mail-forwarding process.
MS Mail AutoForward makes the following assumptions:
• A coexistence backbone has been set up to allow mail exchange between
Microsoft Mail and Lotus Notes.
• Directory information is exchanged between Microsoft Mail and Lotus
Notes to ensure that all current Lotus Notes addresses appear in the
Microsoft Mail directory and all current Microsoft Mail addresses
appear in the Domino directory.
• During mail migration the same name will be assigned to users in Lotus
Notes as has been previously assigned to them in Microsoft Mail.
Note The product design allows for certain flexibility in implementing the
product in environments where some of the above assumptions do not
apply.
Product Configuration
Initial product configuration on the Microsoft Mail side requires identifying
the drive letter assigned to the postoffice directory, Microsoft Mail network
and postoffice names, administrator ID and password, default postoffice
password, and the like.
Initial product configuration on the Lotus Notes side requires setting up the
Mail-In Database and assigning it an entry in the Domino directory.
Ongoing product configuration is performed as follows:
• When a Microsoft Mail user is migrated to Lotus Domino, his/her
Microsoft Mail directory entry is not deleted but rather modified.
• The mailbox is recovered using Microsoft Mail Admin utility to reset the
mailbox password to the postoffice default value.
• The mailbox ID remains intact.
• The full name is modified to make the user “less visible” in the directory.
For example, the full name may be prepended by a symbol or a string,
which pushes it to the bottom of the alphabetically sorted list of
postoffice directory entries. John Smith may become ZZJohn ZZSmith to
ensure that regardless of the sort order (by First Name or by Last Name),
the resulting full name appears at the bottom of the sort list.
• The user is no longer included in the directory synchronization process
set up between Microsoft Mail postoffices as well as between Microsoft
Mail and other environments, specifically, Lotus Domino. Depending on
the coexistence backbone, which is set up between Microsoft Mail and
Lotus Domino, the user may need to be manually removed from the
Domino directory.
• Using the MS Mail AutoForward configuration program, the user is
included in the list of “polled” mailboxes.
• No action is needed on the Lotus Domino side.
Product Information
For information on the mail-forwarding tool, refer to the following Web site:
www.binarytree.com.
Lotus Notes Directory Transporter for Microsoft Mail SMTP Gateways

The following sections describe a directory synchronization tool provided by
Binary Tree, Inc. It is called Directory Transporter for Microsoft Mail SMTP
Gateways.
Business Problem
One of the principal requirements during mail migration from any mail
system to Lotus Domino is to ensure the ability to exchange mail and
directory data between the old mail system and Lotus Domino.
A number of solutions can be used to achieve that type of coexistence
between Microsoft Mail to Lotus Notes. One of the methods of mail
connectivity is the use of an SMTP connection.
While achieving mail connectivity between Microsoft Mail and Lotus Notes,
an SMTP connection does not include a method of synchronizing directory
data between the Microsoft Mail directory and the Domino directory.

A person managing mail migration from Microsoft Mail to Lotus Domino
must decide on an approach to synchronize directory data. There are several
options available:
• No directory synchronization. This option puts an unnecessary burden
on end-users to manually enter addresses in the mail items sent to Lotus
Domino.
• Manual directory synchronization process. While this is viable for small
environments, this option is time- and resource-consuming and has a
high potential for errors.
• Pursue an automated third-party solution, such as the Directory
Transporter for Microsoft Mail SMTP Gateways offered by
Binary Tree, Inc.
Product Description
The Directory Transporter for Microsoft Mail SMTP Gateways is a directory
synchronization product intended to assist with migration and/or coexis-
tence between Microsoft Mail and Lotus Domino. The Directory Transporter
is specifically engineered to support an SMTP backbone between the two
mail systems. It is designed to simplify the migration process from Microsoft
Mail to Lotus Domino by removing the requirement to add additional
hardware and software to support synchronization of the directories.
The Directory Transporter for Microsoft Mail SMTP Gateways runs on a
Windows 95/98/NT PC with a Lotus Notes Client and a connection to a
The following functions are offered:
• Includes a Domino directory agent.
• Does not use the SMTP backbone for synchronization, so it does not take
away from mail connectivity bandwidth.
• Supports existing Lotus Notes SMTP addresses by using the existing
Domino configuration.
• Supports Microsoft Mail SMTP addresses via a configuration option.
• Participates in the native Microsoft Mail directory synchronization
stream without adding another requestor.
• Uses directory shadowing to ensure that the directories of both systems
are always up-to-date.
Product Information
For information on the mail-forwarding tool, refer to the following Web site:
www.binarytree.com.
Summary
In this chapter, we started by giving you an overview of the Microsoft Mail
SMTP Gateway and the SMTP mail routing function provided by the Lotus
Domino Release 5.0 server.
We then covered aspects related to the planning and designing of an SMTP
network. We also provided a case study on how to design an SMTP network
between the Microsoft Mail and Domino environments.
Next, we showed you how to install and configure the Microsoft Mail SMTP
Gateway and the Lotus Domino Release 5.0 server with SMTP mail routing
enabled.
Following this, we gave you an example of how to send mail between
Microsoft Mail and Lotus Domino using the SMTP Gateway.
Finally, we discussed two third-party tools available from Binary Tree, Inc.
One of the tools provides automatic mail-forwarding from Microsoft Mail to
Lotus Domino, the other tool offers directory synchronization between
Microsoft Mail mailboxes and the Domino directory.

Chapter 4
Migrating from Microsoft Mail to Lotus Domino:
Using the Lotus Domino Migration Tools
The migration tools provided by the Lotus Domino Administrator allow you
to migrate users from your existing messaging system to Lotus Domino.
There are migration tools available for various messaging systems. In this
chapter, we will discuss how to use the Microsoft Mail to Lotus Domino
migration tools.
Using the administrator-based Microsoft Mail to Lotus Notes migration tool
allows the administrator to migrate the directory information as well as the
user’s mailbox from the Microsoft Mail postoffice to Lotus Domino.
The user-based upgrade tool allows users to migrate messages from an
off-line Microsoft Mail mailbox to a Lotus Domino mail file.
This chapter covers the following topics:
• Using the administrator-based migration tool
• Using the user-based upgrade tool
• Summary
Note At the point of writing this redbook, we used build 166 of the Lotus
available.
Using the Administrator-Based Migration Tool

The following topics are discussed in this section:
• Understanding the migration process
• Preparing to migrate Microsoft Mail users
• Installing the migration tools
• Performing the migration
• Monitoring the logs
53
Understanding the Migration Process
Using the Microsoft Mail to Lotus Notes migration tool from the Domino
Administrator, you can import users and groups from a selected Microsoft
Mail postoffice and add them to Notes.
The migration process allows you to do the following:
• Import users and groups from the postoffice and create entries for them
in the Domino directory
• Create a Notes ID and mail file for imported users
• Migrate the contents of mailboxes (.MMF files) from a central location,
such as the Microsoft Mail Postoffice server
You can migrate mailbox information from Microsoft Mail Versions 3.2, 3.5,
and 3.6.
The following table lists details of what gets migrated from Microsoft Mail to
Lotus Notes:
Items in Microsoft Mail . . . Migrated/Not Migrated to Notes
Custom message types, including Not migrated
Scheduler messages
Delivery failure messages Not migrated
Public groups Group document in Domino directory
Interpersonal mail messages (IPM) Not migrated
Message date and priority Message date and priority
Messages and attachments Messages and attachments
Outbox folder Not migrated
Password Password
Personal Address Book Personal Address Book*
Postoffice address list Domino directory
Read and unread status Read and unread status
Sender and recipient information Sender and recipient information
Shared and group folder Not migrated
Wastebasket or Deleted mail folder Not migrated
* Personal Address Books are automatically sent to users in a Notes mail

message attachment. Users then run the user upgrade wizard at their
workstations to migrate Address Book information to their Notes Personal
Address Books.

Preparing to Migrate Microsoft Mail Users
This section describes the software requirements and pre-installation tasks
for running the migration tools.
Software Requirements for Using the Administrator Migration Tool

These are the software requirements for setting up the Domino
administrator-based migration tool:
Program Software Requirements
Lotus Domino Administrator Microsoft Windows NT
(we used build 166)
Lotus Domino server (we used Any platform supported by Lotus Domino
build 166)
Software Requirements for Using the User Upgrade Tool

These are the software requirements for setting up the user upgrade tool:
Lotus Domino Administrator Microsoft Windows NT
(we used build 166)
Lotus Domino server (we used Any platform supported by Lotus Domino
build 166)
Lotus Notes client (we used Microsoft Windows NT
build 166)
Before migrating users from Microsoft Mail to Notes, complete the following
tasks:
• Determine the order in which you want to convert your postoffices. This
should be your migration schedule.
• Verify that you have access to the certifier IDs and passwords for the
Domino organizations and organizational units where you are
registering users.
• Verify that you have purchased the appropriate Notes client license for
each Microsoft Mail user you are migrating.
• Back up important Domino information.
Chapter 4: Using the Lotus Domino Migration Tools 55

• Verify that you have Editor, Designer, or Manager access rights to the
Domino directory on the Registration server.
• From the administrative workstation, log in to Notes with a Notes ID
that has “Create database access” on the Mail server. This type of access
is specified in the server document pertaining to the Mail server.
• From the administrative workstation, map a drive to the location of the
Microsoft Mail postoffice you are migrating users from.
• (Optional) Set registration preferences.
• (Optional) Create a Notes group to which you can add migrated users.
• Send any pending Microsoft Mail messages.
• Back up the mailbox files stored at the postoffice. If you do not have a
Microsoft Mail administrator who backs up mailbox files on a regular
basis, refer to the Microsoft Mail Administrator’s Guide for instructions
on backing up data.
• On the administrative workstation, close all applications, except for
Notes, and close any Domino databases.
Installing the Migration Tools

The tasks described in this section require the use of the Domino
Administrator and migration tools. By default, the migration tools are not
installed with the Domino Administrator; you must select the Migration
Tools component during the installation process.
Tip For best performance, it is recommended that you run the Domino
Administrator on a computer within the same Domino domain as the
destination mail server.
The following steps show you on how to install the Microsoft Mail migration
tools:
1. Start the Lotus Notes client installation program.

2. Continue installation until you see the following screen:
3. Select Domino Administrator and then click the Customize button. The
following screen is displayed:

4. From the list of components to install, select Migration tools and click the
Change button. The following screen is displayed:
5. From the Select Sub-components dialog box, select the following options:
• MS-Mail Client Migration
• MS-Mail Admin Migration
Note If you are installing the user upgrade tool on a user’s workstation,
select MS Mail Client Migration only.
6. Continue and complete the Lotus Notes client installation as directed.
Note For details on how to set up the administrator client, refer to the
Domino Administration guide.
This completes the migration tool installation.
Performing the Migration Process

This section describes the migration process using the Lotus Domino
Administrator. In our case study, we will migrate users from the ACMESF
Microsoft Mail postoffice to the MAIL1/SF/ACME Domino server.
These are the steps involved in the migration process:
• Migrating the user’s mailbox from the Microsoft Mail postoffice to Lotus
Notes.
• Migrating the Personal Address Book from the Microsoft Mail postoffice
to the Lotus Notes Personal Address Book.

• Migrating public groups from the Microsoft Mail postoffice to the Lotus
Domino directory.
• Migrating archived messages.
Migrating a User’s Mailbox
The following steps guide you on how to migrate users from the Microsoft
Mail postoffice to Lotus Domino:
1. Start the Lotus Domino Administrator.
2. Enter the Notes Administrator’s password and click the OK button.
3. Click the ACME Domain icon in the bookmark bar.
4. Select All Servers - MAIL1/SF/ACME from the view. The Domino
Administrator will connect to the MAIL1 server.
5. Select the People/Groups tab. The following screen is displayed:
6. Click the People button to expand the People section.

7. Click the Register option.
8. Enter the certifier password and click OK.

The following screen is displayed:
9. On the Basics tab, click the Registration Server button and select
MAIL1/SF/ACME as the registration server.
10. Click the Mail tab.
11. Click the Mail Server button and select MAIL/SF/ACME as the mail
server.

12. Click the Migrate people button. The following screen is displayed:
13. Under Foreign directory source, select MS Mail Users. The following
screen is displayed:
14. In the Postoffice path field, enter the Microsoft Mail postoffice path from
where the Microsoft Mail users will be migrated to Domino.
Note You should enter the mapped drive letter for the Microsoft Mail
postoffice. In our case study, we mapped the M: drive to the ACMESF
15. Specify the administrator’s name of that postoffice.
16. Specify the administrator’s password.

17. Click OK to close the screen. The tool displays all the user names and the
group names from the Microsoft Mail postoffice.
18. Select the names of users who need to be migrated and click the Add
button.
Note Migrating groups is discussed later in this chapter.
The following screen displays the user names selected from the ACMESF
postoffice:
19. Click the Advanced button. The following screen is displayed:
20. Leave the Convert Personal Address Book check box selected if you
want to migrate the Personal Address Book information stored with
the user’s Microsoft Mail mailbox.

21. After the migration completes, the Domino Administrator automatically
places a message in the Inbox of the user’s mail file to which it attaches a
temporary Notes Personal Address Book. It contains the migrated
information. Users then run the upgrade wizard for Microsoft Mail at
the Notes client to copy information from this temporary Notes
document to the Personal Address Book on the Notes desktop.
22. Click OK to close the window.
23. In the Migration options section, leave the default options that are
selected. You can select whether or not to convert mail. Deselect the
check box if you wish to migrate the directory only.
24. Click the Migrate button. The tool adds the selected names into the
registration queue. The following message box is displayed:
25. Click OK to continue.

26. Click Done to close the migration window. The following screen is
displayed:

27. If you want to modify any user details, click the user name which is
displayed in the Registration queue. You can modify the details and then
continue the registration process.
28. Click on Register All. The tool will register the Microsoft Mail user
names with Domino and migrate all the messages from their Microsoft
Mail mailboxes to the Notes mail files.
After completing the migration, the tool displays the following message:
29. Click OK to close the window.

30. Click the Done button to close the Registration screen.
Note All the error and informational messages are written into the local
Notes log file located on the administrator’s workstation.
The following screen shows the People/Group view in the Domino
Administrator for the MAIL1/SF/ACME server:

The following screen shows John Doe’s Notes mail file after the migration
has completed successfully:
This completes the migration of Microsoft Mail user names and messages
from Microsoft Mail to Lotus Notes.
Migrating the Personal Address Books

When migrating a user mailbox, if you have selected to also migrate the
user’s Personal Address Book, the migration tool will migrate the Microsoft
Mail personal address list into a Lotus Notes Personal Address Book and
send it to the user as an attachment.
The following steps guide you on how to detach the Personal Address Book
once it has been migrated to Lotus Notes:
1. Open the user’s mail file.

2. Open the mail which was sent to the user by the migration tool. The
3. Double-click the attachment and click the Detach button.

4. Enter the file name and save the address book in the Data directory.
5. Close all the open windows in Notes.
6. Select File - Open Database. The following screen is displayed:

7. Select Doe’s Address Book and click the Open button. The following
This adds John Doe’s Personal Address Book to the Notes bookmark and
completes the migration of the personal address list from Microsoft Mail
to Lotus Notes.
Migrating Public Groups

The following instructions guide you on how to migrate public groups from
the Microsoft Mail postoffice to the Lotus Domino directory.
1. Go to the “Migrating a User’s Mailbox” section (earlier in this chapter)
and perform steps 1-18.

2. Check the Show only groups check box. The following screen is
displayed:
3. Select the group name that you want to migrate and click the Add
button. The following screen is displayed:
4. Specify the required information as appropriate for your environment

and click OK to close the screen.

The tool displays all the names of users who are members of the group
you are migrating. If you do not plan to migrate all the users in this list,
you can select a user name and remove it from the list.

The following screen displays the group we called sales and which we
selected for migration with the member names removed:
5. Click Done to close the screen.

6. Click Done to close the Registration screen.

7. Open the Lotus Domino directory to check the Group view. It looks like
this:
8. Double-click the sales document. The following screen displays the

member list of the sales group:
This completes the public group migration from Microsoft Mail to Lotus
Domino.

Migrating Local Mailboxes and Archived Messages
If the Microsoft Mail users have local mailboxes or archived mailboxes on
their local machines, the user upgrade tool can be used to migrate these
mailboxes from Microsoft Mail to Lotus Domino.
By default, when installing the Lotus Notes client, the user upgrade tool
does not get installed. Refer to the “Preparing to Migrate Microsoft Mail
Users” and “Installing the Migration Tools” sections earlier in this chapter
for information on how to install the user upgrade tool.
Note The user upgrade tool must be installed on the user’s local machine.
The following tasks will be performed to migrate archived messages:
• The administrator sends an upgrade notification.
• The Notes user runs the upgrade wizard.
Sending an Upgrade Notification
The following steps guide you on how to prepare and send an upgrade
notification:
2. Enter the Notes administrator’s password and click OK.
3. Click the ACME Domain icon in the bookmark bar.
4. Select All Servers - MAIL1/SF/ACME from the view. The Domino
Administrator will connect to the MAIL1 server.
5. Right-click the view pane.
6. Select Open Directory. The Lotus Domino directory database is opened.
7. Select the Mail Users view.

8. Click the Send Upgrade Notification button located on the action bar.

9. In the To field, select the addresses to whom this upgrade notification
needs to be sent.
10. Select the option Send out cc:Mail/MS Mail/MS Exchange convert local
information notices.
11. In the Mail Conversion Options section, select MS Mail. The following
screen displays the new configuration:
12. Click the Send button to send this notification to the users.
This completes the steps required to create and send a notification for
migrating archived messages.

Running the User Upgrade Tool
The following steps guide you on how to use the user upgrade tool to
migrate the local mailbox or the archived mailbox:
1. Open your mail file. The following screen displays John Doe’s Inbox
view with the notification from the administrator:

2. Double-click the Upgrading from Microsoft Mail to Notes mail message.
3. Click the Convert Local Data to Notes button. The upgrade wizard is
started and the following screen is displayed:

4. Click the Next button to continue. The following screen is displayed:
5. Enter the MS Mail mailbox name and the password.


7. Select the Custom option and click the Next button to continue. The
8. Leave the default selection and click the Next button. The following

9. Click the Select Files button. The following screen is displayed:
10. Select the local mailbox or the archive mailbox you want to migrate and
click the Add button.
11. Click the Done button to close the screen.
12. Change the Template name and Folder name if they are different.
14. Click the Finish button to complete the setup and continue the
migration.
15. The tool displays the following screen to enter the password for the
Notes ID. Enter the password and click OK.

The following screen shows the information displayed by the tool during
the migration process:
16. After completing the migration, the tool displays the following screen.
Click OK to close the screen.
This completes the steps required to migrate the local mailbox or the
archived messages from the MS Mail mailbox to the Notes mail file.
Monitoring Logs and Statistics

All the messages received during the migration process are logged into the
local log file located on the administrator’s workstation.
Viewing the Administrator’s Log File

The following steps guide you on how to open the Notes log file and view
the log messages:
2. Choose File - Open Database from the menu bar.

3. Select the Notes log file and click the Open button. The log file is opened.
4. Click the Miscellaneous Events view.
5. Scroll down to the section listing the administrator’s name.
6. Double-click the document that displays the date and time when you
performed the migration process. The following screen shows the log
document for Hub Admin/ACME:
7. Press ESC to close the screen.
Viewing the User’s Log File

The following steps guide you on how to open the Notes log file and view
the log messages recorded during the user upgrade process:
2. Select File - Open Database from the menu bar.
3. Select the Notes log file for the user and click the Open button. The log
file is opened.
4. Click the Miscellaneous Events view.
5. Scroll down to the section listing the user’s name.

6. Double-click the document that displays the date and time when you
performed the migration process. The following screen shows the log
document for John Doe:
7. Press ESC to close the screen.

This completes the steps required to view the log files.
Summary
In this chapter, we discussed the administration-based migration tool and
the user-based migration tool provided by Lotus Domino Release 5.0 for
migrating users and their data from Microsoft Mail to Domino Release 5.0.
For both tools, we first described the migration process and covered some
aspects related to planning.
We then described how to install and configure the tools.
We showed you how an administrator can migrate a Microsoft Mail user’s
mailbox to Lotus Domino, how personal address lists are handled, and how
public groups are migrated.
Finally, we explained how Microsoft Mail users can migrate their local
mailboxes and archived mailboxes to Lotus Domino.

Chapter 5
Migrating from Microsoft Schedule+ 1.0 to
Lotus Domino Calendaring & Scheduling
This chapter describes how to migrate from Microsoft Schedule+ 1.0 to

Lotus Domino Release 5.0 Calendaring & Scheduling. It covers the following
topics:
• Understanding the Schedule+ 1.0 environment
• Understanding the Lotus Domino Calendaring & Scheduling
environment
• Using the Binary Tree user migration tool to migrate
• Summary
Note At the time of writing this redbook, we used build 166 of the Lotus
available.
Understanding the Schedule+ 1.0 Environment

Schedule+ provides users with an easy way to keep track of their own
appointments and tasks, as well as efficiently organize meetings with other
users. With Schedule+, users can view the times of the people they want to
invite to a meeting.
The Schedule+ user’s appointments, tasks and other schedule information
such as notes and private settings, are stored in calendar (.CAL) files. Each
user has two calendar files: a server file and a local file. The server file is the
user’s .CAL file that is located on the server hosting the user’s postoffice. The
local file is the user’s .CAL file that is located on a local hard drive.
When a user works with Schedule+, the changes made to the schedule are
made directly to the postoffice (server) version of the calendar file. The
online calendar file is automatically copied to the local calendar file every
minute and a final time when the user quits working online. When the user
works offline, all changes are stored to the local calendar file. The next time
the user works online, Schedule+ will automatically update the server
calendar file with the changes made offline.
83
Understanding the Lotus Domino Calendaring & Scheduling Environment
In Lotus Domino Release 5.0, the Calendaring & Scheduling (C&S)
functionality is available as part of the user’s mail file. It focuses on two
aspects of C&S:
• Group scheduling
• Time management
The Domino mail file includes views for the Calendaring & Scheduling
functions. The following window shows a typical Domino mail file calendar
view.
Using the Binary Tree User Migration Tool

The Binary Tree user migration tool is used to migrate the appointments and
tasks from Microsoft Schedule+ to Lotus Domino Calendaring & Scheduling.
The user migration tool is a single Domino database which is used by Notes
users to perform the migration.

Understanding the Migration Process
After installation of the user migration tool, the Domino database
CS2NOTES50.NSF is used by the users to migrate their appointments and
tasks to Lotus Calendaring & Scheduling. The migration process works like
this:
• Every user creates a migration document in the C&S Migration database.
• The migration document includes the programs for exporting the
appointments and tasks from Microsoft Schedule+ and for importing
them into the user’s Lotus Domino mail file.
In this chapter, we will discuss how to migrate the Microsoft Schedule+
calendar of the user John Doe to Lotus Domino.
Planning for the User Migration Tool

The software requirements are as follows:
Operating system Windows 95/Windows NT
Lotus Notes client Release 5.0 (We used build 166)
Microsoft Schedule+ Version 1.0
Installing the User Migration Tool

The user migration tool can be installed when installing the Lotus Notes
client software. By default, the Schedule+ migration tool is not installed
when installing the Lotus Notes client. If you did not install the migration
tool when installing the Lotus Notes client, you need to rerun the Lotus
Notes client installation.
The following steps show you how to install and set up the Binary Tree
Microsoft Schedule+ to Notes migration tool.
1. Start the Lotus Notes client installation.
Chapter 5: Migrating from Microsoft Schedule+ 1.0 to Lotus Domino Calendaring & Scheduling 85
2. Continue the installation until you see the following screen:
3. Select Notes Client or the type of client you need to install.

4. Click the Customize button. The following screen is displayed:
5. Scroll down and select Migration Tools.

6. Click the Change button. The following screen is displayed:
7. Deselect all the other migration tools and select the Calendar Client
Migration Tools.
8. Click the Continue button.
9. Complete the client installation.
10. After installing the client, set up the client for connecting to the Domino
server.
This completes the Microsoft Schedule+ to Notes migration tool installation.
Using the Schedule+ Migration Tool

The following steps show you how to use the Binary Tree user migration tool
to migrate your appointments and tasks from the Microsoft Schedule+
calendar file to Lotus Domino Calendaring & Scheduling.
Preparing the Migration Settings Document

Follow these steps:
2. Choose File - Database - Open. The following dialog box is displayed:
3. Select C&S 1.0 for Notes 5.0 from the database list.
4. Click the Open button. The migration tool database is opened and the

5. Click the Schedule+ 1.0 button. The following screen is displayed:
Click the Click here to Create or Modify Migration Document button.

The following migration settings document is displayed:
6. In Section1. Define Source, enter C:\SCHDPLUS in the Schedule+

directory field. This is the directory where the user’s calendar file (.CAL)
is stored.
7. Enter the appropriate start date in the Starting Date field. This date is
entered in MM/DD/YY format.
8. Enter the appropriate end date in the Ending Date field. This date is
entered in MM/DD/YY format.
9. In Section 3. Define Destination, click the Find my mail file button. The
tool will update the user’s mail server name and the mail file name.
These data are taken from the Location document that is currently in
use.
The following document is the Schedule+ to Notes migration document
for John Doe:
Exporting and Importing Data

The following steps show you how to export and import the appointments
and tasks from Schedule+ to Domino.
1. In the Schedule+ to Notes migration document, click the Export
Schedule+ File button to export all your appointments and tasks from
your Microsoft Schedule+ calendar file.
2. The system will create two files, SLPSDUMP.TXT and SLPSERR.TXT, on
your local c: drive. These files get deleted when the importing process is
completed.

3. You will be prompted to enter the mailbox name and password to log on
to Microsoft Schedule+. The following Mail Sign In dialog box is
displayed:
4. After logon, the system will export all the appointments and the tasks.
The following message is displayed showing the status during the
export process:
When the export process is complete, the following message is

displayed:
5. Click OK to close the message.

6. Click Begin Import to import all the exported appointments and tasks to
your Domino mail file.
7. Wait until the import complete message appears in the status bar of the
Notes client.
8. Close the migration tool database.
This completes the migration of appointments and tasks from the Schedule+
calendar file to the Lotus Domino mail file.
9. Open your Domino mail file and click the Calendar view to view your
appointments. The following window displays the Calendar view of John
Doe’s mail file that contains the calendar information that has been
migrated from Schedule+:
This completes the steps to migrate the appointments and tasks from the
Microsoft Schedule+ calendar file to the Domino mail file.
Monitoring the Logs and Statistics

The statistics of the migration process are written to your migration settings
in the C&S 1.0 to Notes 5.0 database. The following steps show you how to
view the statistics.
1. Open the C&S 1.0 to Notes 5.0 database.

2. Click Schedule 1.0 in the navigator pane. The following view is
displayed:
3. Double-click the John Doe settings document.

4. Scroll down to the statistics section. This section contains statistics
related to the calendar migration.
The following illustration displays the statistics report for John Doe’s
calendar migration:
5. Press ESC to close the document.
Summary
In this chapter, we discussed the user migration tool provided by Binary
Tree, Inc. to migrate appointments and tasks from Schedule+ 1.0 to Lotus
Domino Release 5.0.
We described how to install the user migration tool and how to use the
migration database to specify the required migration settings.
Finally, we showed you how to perform the actual migration of calendar
data from Schedule+ to Lotus Domino Calendaring & Scheduling.

Special Notices
This publication is intended to help administrators migrate users and data

from Microsoft Mail to Lotus Domino Release 5.0.
The information in this publication is not intended as the specification of any
programming interfaces that are provided by Lotus Domino. See the
publications section of the announcement for Lotus Domino and related
products for more information about what publications are considered to be
product documentation.
References in this publication to IBM products, programs, or services do not
imply that IBM intends to make these available in all countries in which IBM
operates. Any reference to an IBM product, program, or service is not
intended to state or imply that only IBM products, programs, or services
may be used. Any functionally equivalent program that does not infringe on
any IBM intellectual property rights may be used instead of the IBM
product, program or service.
Information in this book was developed in conjunction with use of the
equipment specified, and is limited in application to those specific hardware
and software products and levels.
IBM may have patents or pending patent applications covering subject
matter in this document. The furnishing of this document does not give you
any license to these patents. You can send license inquiries, in writing, to the
IBM Director of Licensing, IBM Corporation, 500 Columbus Avenue,
Thornwood, NY 10594 USA.
Licensees of this program who wish to have information about it for the
purpose of enabling: (i) the exchange of information between independently
created programs and other programs (including this one) and (ii) the
mutual use of the information which has been exchanged, should contact
IBM Corporation, Dept. 600A, Mail Drop 1329, Somers, NY 10589 USA.
Such information may be available subject to appropriate terms and
conditions, including, in some cases, payment of a fee.
The information contained in this document has not been submitted to any
formal IBM test and is distributed AS IS. The information about non-IBM
(“vendor”) products in this manual has been supplied by the vendors, and
IBM assumes no responsibility for its accuracy or completeness. The use of
this information or the implementation of any of these techniques is a
customer responsibility and depends on the customer’s ability to evaluate
95
and integrate them into the customer’s operational environment. While each
item may have been reviewed by IBM for accuracy in a specific situation,
there is no guarantee that the same or similar results will be obtained
elsewhere. Customers attempting to adapt these techniques to their own
environments do so at their own risk.
Any pointers in this publication to external Web sites are provided for
convenience only and do not in any manner serve as an endorsement of
these Web sites.
Any performance data contained in this document was determined in a
controlled environment, and therefore the results that may be obtained in
other operating environments may vary significantly. Users of this document
should verify the applicable data for their specific environment.
The following document contains examples of data and reports used in daily
business operations. To illustrate them as completely as possible, the
examples contain the names of individuals, companies, brands, and
products. All of these names are fictitious and any similarity to the names
and addresses used by an actual business enterprise is entirely coincidental.
Reference to PTF numbers that have not been released through the normal
distribution process does not imply general availability. The purpose of
including these reference numbers is to alert IBM customers to specific
information relative to the implementation of the PTF, when it becomes
available to each customer according to the normal IBM PTF distribution
process.
The following terms are trademarks of the International Business Machines
Corporation in the United States and/or other countries:
AIX NetView
AS/400 Network Station
BookManager OS/2
BookMaster OS/400
DB2 OS/390
DB2 Universal Database VisualAge
IBM Visual Beans
MQSeries VisualGen
The following are trademarks of Lotus Development Corporation in the
United States and/or other countries:
1-2-3® LotusScript®
Approach® Lotus SmartSuite®
cc:Mail Notes HiTest
DataLens® Notes ViP®
Freelance® Notes Mail®
InterNotes NotesPump

InterNotes Web Publisher NotesSQL
Lotus® Notes/FX
Lotus Domino Phone Notes®
Lotus Notes Reporter Phone Notes Mobile Mail
Lotus Notes SmartIcons®
Video Notes Word Pro
The following terms are trademarks of other companies:
C-bus is a trademark of Corollary, Inc.
Java and all Java-based trademarks and logos are trademarks or registered
trademarks of Sun Microsystems, Inc. in the United States and/or other
countries.
Microsoft, Windows, Windows NT, and the Windows logo are trademarks
of Microsoft Corporation in the United States and/or other countries.
PC Direct is a trademark of Ziff Communications Company and is used by
IBM Corporation under license.
ActionMedia, LANDesk, MMX, Pentium and ProShare are trademarks of
Intel Corporation in the United States and/or other countries. (For a
complete list of Intel trademarks see www.intel.com/dradmarx.htm)
UNIX is a registered trademark in the United States and other countries
licensed exclusively through X/Open Company Limited.
Other company, product or service names may be the trademarks or service
marks of others.
Special Notices 97
Related Publications
The publications listed in this section are considered particularly suitable for
a more detailed discussion of the topics covered in this redbook.
International Technical Support Organization Publications

For information on ordering these ITSO publications see, “How To Get ITSO
Redbooks.”
• Eight Steps to a Successful Messaging Migration: A Planning Guide for
Migrating to Lotus Notes and Domino, IBM form number SG24-5335, Lotus
part number CT6HINA
• Lotus Notes and Domino: The Next Generation in Messaging — Moving from
• The Next Step in Messaging: Upgrade Case Studies for Lotus cc:Mail to Lotus
Domino and Lotus Notes, IBM form number SG24-5100, Lotus part
number 12992
Other Lotus-Related ITSO Publications

The publications listed in this section may also be of interest:
• Lotus Solutions for the Enterprise, Volume 1. Lotus Notes: An Enterprise
Application Platform, IBM form number SG24-4837, Lotus part number
12968
• Lotus Solutions for the Enterprise, Volume 2. Using DB2 in a Domino
Environment, IBM form number SG24-4918, Lotus part number
CT69BNA
99
• Lotus Solutions for the Enterprise, Volume 3. Using the IBM CICS Gateway
for Lotus Notes, IBM form number SG24-4512
• Lotus Solutions for the Enterprise, Volume 4. Lotus Notes and the MQSeries
Enterprise Integrator, IBM form number SG24-2217, Lotus part number
12992
• Lotus Solutions for the Enterprise, Volume 5. NotesPump, the Enterprise Data
Mover, IBM form number SG24-5255, Lotus part number CT69DNA
• Lotus Notes 5.0: A Developer’s Handbook, IBM form number SG24-5331,
Lotus part number CT6HPIE
• Lotus Notes and Domino R5.0 Security Infrastructure Revealed, IBM form
number SG24-5341, Lotus part number CT6TPNA
• Enterprise-Wide Security Architecture and Solutions, IBM form number
SG24-4579
• Understanding LDAP, IBM form number SG24-4986
• LotusScript for Visual Basic Programmers, IBM form number SG24-4856,
Lotus part number 12498
• Secrets to Running Lotus Notes: The Decisions No One Tells You How to
Make, IBM form number SG24-4875, Lotus part number AA0424
• Deploying Domino in an S/390 Environment, IBM form number SG24-2182,
Lotus part number 12957
• Developing Web Applications Using Lotus Notes Designer for Domino 4.6,
IBM form number SG24-2183, Lotus part number 12974
• High Availability and Scalability with Domino Clustering and Partitioning on
Windows NT, IBM form number SG24-5141, Lotus part number
CT6XMIE
• From Client/Server to Network Computing, A Migration to Domino, IBM
form number SG24-5087, Lotus part number CT699NA
• Lotus Domino Integration Guide for IBM Netfinity and IBM PC Servers, IBM
form number SG24-2102
• Lotus Domino Release 4.6 on IBM RS/6000: Installation, Customization and
Administration, IBM form number SG24-4694, Lotus part number 12969
• High Availability and Scalability with Domino Clustering and Partitioning on
AIX, IBM form number SG24-5163, Lotus part number CT7J0NA
• AS/400 Electronic-Mail Capabilities, IBM form number SG24-4703
• Mail Integration for Lotus Notes 4.5 on the IBM Integrated PC Server for
AS/400, IBM form number SG24-4977
• Using Lotus Notes on the IBM Integrated PC Server for AS/400, IBM form
number SG24-4779

• Lotus Domino for AS/400: Installation, Customization and Administration,
IBM form number SG24-5181, Lotus part number AA0964
• Lotus Domino for S/390 Release 4.5: Installation, Customization & Admin-
istration, IBM form number SG24-2083, Lotus part number AA0963
• Lotus Domino for S/390 Performance Tuning and Capacity Planning, IBM
form number SG24-5149, Lotus part number CT6XNIE
• Porting C Applications to Lotus Domino on S/390, IBM form number
SG24-2092, Lotus part number AB1720
• Enterprise Integration with Domino for S/390, IBM form number SG24-5150
• Managing Domino/Notes with Tivoli Manager for Domino, Enterprise Edition,
Version 1.5, IBM form number SG24-2104
• Measuring Lotus Notes Response Times with Tivoli’s ARM Agents, IBM form
number SG24-4787, Lotus part number CT6UKIE
• Implementing LAN Server for MVS in a Lotus Notes Environment, IBM form
number SG24-4741
• Using ADSM to Back Up Lotus Notes, IBM form number SG24-4534
• NetFinity V5.0 Database Support, IBM form number SG24-4808
• An Approach to ODBC: Lotus Approach to DB2, IBM form number
SG24-4685
Redbooks on CD-ROMs
Redbooks are also available on the following CD-ROMs:
Collection Kit
CD-ROM Title Number
Lotus Redbooks Collection SK2T-8039
Tivoli Redbooks Collection SK2T-8044
Application Development Redbooks Collection SK2T-8037
RS/6000 Redbooks Collection (PostScript) SK2T-8041
RS/6000 Redbooks Collection (HTML, BkMgr) SK2T-8040
RS/6000 Redbooks Collection (PDF) SK2T-8043
AS/400 Redbooks Collection SK2T-2849
Transaction Processing and Data SK2T-8038
Management Redbook Collection
Networking and Systems Management Redbooks Collection SK2T-6022
System/390 Redbooks Collection SK2T-2177
Related Publications 101

How to Get ITSO Redbooks
This section explains how both customers and IBM employees can find out about ITSO redbooks,
redpieces, and CD-ROMs. A form for ordering books and CD-ROMs by fax or e-mail is also provided.
• Redbooks Web Site http://www.redbooks.ibm.com

Search for, view, download or order hardcopy/CD-ROM redbooks from the redbooks Web site. Also
read redpieces and download additional materials (code samples or diskette/CD-ROM images) from
this redbooks site.
Redpieces are redbooks in progress; not all redbooks become redpieces and sometimes just a few
chapters will be published this way. The intent is to get the information out much quicker than the
formal publishing process allows.
• E-mail Orders
Send orders via e-mail including information from the redbooks fax order form to:
e-mail address
In United States: usib6fpl@ibmmail.com
Outside North America: Contact information is in the “How to Order” section at this site:
http://www.elink.ibmlink.ibm.com/pbl/pbl/
• Telephone Orders
United States (toll free) 1-800-879-2755
Canada (toll free) 1-800-IBM-4YOU
Outside North America Country coordinator phone number is in the “How to Order”
section at this site:
• Fax Orders
United States (toll free) 1-800-445-9269
Canada (toll free) 1-800-267-4455
Outside North America Fax phone number is in the “How to Order” section at this site:
This information was current at the time of publication, but is continually subject to change. The latest
information for customers may be found at http://www.redbooks.ibm.com/ and for IBM employees
at http://w3.itso.ibm.com/.
IBM Intranet for Employees

IBM employees may register for information on workshops, residencies, and redbooks by
accessing the IBM Intranet Web site at http://w3.itso.ibm.com/ and clicking the ITSO
Mailing List button. Look in the Materials repository for workshops, presentations, papers, and
Web pages developed and written by the ITSO technical professionals; click the Additional
Materials button. Employees may also view redbook, residency, and workshop announcements
at http://inews.ibm.com/.
103
IBM Redbook Fax Order Form
Please send me the following:
Title Order Number Quantity
First name Last name
Company
Address
City Postal code Country
Telephone number Telefax number VAT number
❏ Invoice to customer number
❏ Credit card number
Credit card expiration date Card issued to Signature
We accept American Express, Diners, Eurocard, MasterCard, and Visa. Payment by credit card not available
in all countries. Signature mandatory for credit card payment.
105
Index
A E M
Access to certifier IDs, 55 Exporting Schedule+ appointments Mail routing in MS Mail, 8
Administrator-based migration and tasks, 90 Mail-forwarding tool, 47
tool, 53, 58 Message settings, 43
Alias, 21 Microsoft Mail alias, 21
Archived mailboxes, 72, 75 F Microsoft Mail SMTP
Foreign Domain document, 41 Gateway, 13, 17, 21
Microsoft Schedule+ 1.0, 83
B
Backing up mailboxes, 56 G Migrate people button, 61
Migrating appointments and
Binary Tree, 83 Gateway Access tasks, 84
component, 25, 29, 33
Migrating archived mailboxes, 72, 75
Gateway component, 25
C Global Address List, 46
Migrating local mailboxes, 72, 75
Migrating public groups, 67
Certifier IDs, 55 Guidelines for choosing a coexistence
Migrating the Personal Address
Choosing a coexistence tool, 10 tool, 10 Book, 65
Choosing a migration tool, 11 Migrating users, 59
Coexistence tools, 2, 10
Components for the SMTP H Migration document, 85, 87
Hardware requirements, 19 Migration process, 54
Gateway, 25 Migration schedule, 55
Configuring Domino SMTP
Migration tools, 2, 11, 53
routing, 33
Configuring message settings, 43
I MIME format, 14
Importing Schedule+ appointments Monitoring logs, 80
Configuring the SMTP Gateway, 30
and tasks, 90 MS Mail AutoForward, 47
Connection document, 42 MS Mail concepts, 5
Create database access, 56 Importing users, 54
Creating mail files, 54 Infrastructure components, 9
Creating Notes IDs, 54
Installing Domino SMTP routing, 33
Installing the migration tools, 56, 85
N
Installing the SMTP Naming considerations, 20
D Gateway, 24, 27, 34 Network design, 6
Notes log file, 64, 80
Designing an SMTP network, 19
Notes routing, 15
Directory synchronization tool, 50
Disclaimer, 2
L
Domain suffix, 32 Local mailboxes, 72, 75
Long-term migration, 11
P
Domino Administrator, 37 Pending Microsoft Mail messages, 56
Domino directory, 56 Lotus Domino Calendaring &
Scheduling, 84 Performance, 56
Domino Release 5.0 migration Personal Address Books, 54, 62, 65
Lotus Domino SMTP MTA, 13
tools, 53 Planning for an SMTP
Domino SMTP mail Lotus Messaging Switch, 2
connection, 19, 23
routing, 14, 21, 33 Pre-installation tasks, 24, 33, 55
Downstream postoffices, 29 Preparing the migration settings
document for Schedule+, 87
Public groups, 67
107
R
Redbooks, 3
Registration server, 56
S
Sending mail, 45
Server document, 56
Setting up the SMTP Gateway, 30
Single-step migration, 11
Smart host, 40
SMTP address components, 21
SMTP connection document, 42
SMTP mail routing, 14, 15, 16, 17, 18
SMTP naming convention, 23
SMTP postoffice list, 33
Software requirements, 19, 55
Special characters, 21
Starting Domino SMTP mail
routing, 45
Starting the SMTP Gateway, 45
Stopping Domino SMTP mail
routing, 45
Stopping the SMTP Gateway, 45
T
Tell smtpmta quit, 45
U
Upgrade notification, 72
Upgrade wizard, 54, 63, 72
User migration tool for Schedule+, 84
User-based migration tool, 53, 72
Using the migration tool, 87
V
Viewing logs, 92
Viewing migrated
appointments, 92
W
What gets migrated, 54
www.binarytree.com, 50

ITSO Redbook Evaluation
Moving from Microsoft Mail to Lotus Notes and Domino SG24-5152-01
Your feedback is very important to help us maintain the quality of ITSO redbooks.
Please complete this questionnaire and return it using one of the following methods:
• Use the online evaluation form at http://www.redbooks.ibm.com

• Fax it to: USA International Access Code +1 914 432 8264
• Send your comments in an Internet note to redbook@us.ibm.com
Which of the following best describes you?
___Customer ___Business Partner ___Solution Developer ___IBM employee
___None of the above
Please rate your overall satisfaction with this book using the scale:
(1 = very good, 2 = good, 3 = average, 4 = poor, 5 = very poor)
Overall Satisfaction ________________
Please answer the following questions:
Was this redbook published in time for your needs? Yes _________ No ________
If no, please explain:
____________________________________________________________________________________
____________________________________________________________________________________
____________________________________________________________________________________
____________________________________________________________________________________
What other redbooks would you like to see published?
____________________________________________________________________________________
____________________________________________________________________________________
____________________________________________________________________________________
Comments/Suggestions: (THANK YOU FOR YOUR FEEDBACK!)
____________________________________________________________________________________
____________________________________________________________________________________
____________________________________________________________________________________
____________________________________________________________________________________
© Copyright IBM Corp. 1999

Printed in the U.S.A.
The Next Generation in Messaging: Moving from Microsoft Mail to Lotus Notes and Domino
SG24-5152-01
Part No. CT7SBNA

The Next Generation in Messaging:
Moving from Microsoft Mail
to Lotus Notes and Domino
Marion Hawker, Siva Kumar
SG24-5152-01

Exchange To Domino0

Transféré par

Informations du document

Description originale:

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Exchange To Domino0

Transféré par

Droits d'auteur :

Formats disponibles

Printed in the U.S.A.

Part No. CT7SBNA

International Technical Support Organization

The Next Generation in Messaging

Moving from Microsoft Mail to

Second Edition (June 1999)

This edition applies to Lotus Domino Release 5.0.

© International Business Machines Corporation (1998, 1999). All rights reserved.

Preface . . . . . . . . . . . . . . . . . . . . . . . . v Lotus Domino Release 5.0 SMTP Mail

iv Moving from Microsoft Mail to Lotus Notes and Domino

This redbook describes how to migrate from a Microsoft Mail environment

The Team That Wrote This Redbook

• Send your comments in an Internet note to

If you are currently planning to move from your existing LAN-based

2 Moving from Microsoft Mail to Lotus Notes and Domino

This chapter gives an overview of Microsoft Mail and Lotus Domino.

What Is Microsoft Mail?

Network Design Aspects of Microsoft Mail

Network and Postoffice Concepts in Microsoft Mail

Logical Network Design

MS Mail Network: NET1

PO2 LAN PO4

6 Moving from Microsoft Mail to Lotus Notes and Domino

MS Mail Network: SFNET External

MS Mail Network: NYNET

Chapter 2: Microsoft Mail and Lotus Domino 7

Sending Mail to Users in the Same Postoffice

Sending Mail to Users in External Postoffices

8 Moving from Microsoft Mail to Lotus Notes and Domino

MS Mail External MS Mail

Comparing the Infrastructure Components of Microsoft Mail

Chapter 2: Microsoft Mail and Lotus Domino 9

10 Moving from Microsoft Mail to Lotus Notes and Domino

Single-Step Migration Process

Long-Term Coexistence and Migration

12 Moving from Microsoft Mail to Lotus Notes and Domino

The SMTP (Simple Mail Transfer Protocol) Gateway software allows an

Microsoft Mail SMTP Gateway

Lotus Domino Release 5.0 SMTP Mail Routing

14 Moving from Microsoft Mail to Lotus Notes and Domino

Lotus Domino R5 Server

In this example, a single Domino server, MAILHUB/ACME, handles

In this example, Acme has three mail servers: MAIL-01/ACME,

16 Moving from Microsoft Mail to Lotus Notes and Domino

A Typical SMTP Connection between Domino and Microsoft Mail

How Mail Routing Works Using SMTP

Lotus Notes Lotus Domino R5 Server Lotus Domino R5 Server

MS Mail MS Mail MS Mail

Lotus Domino to Microsoft Mail

18 Moving from Microsoft Mail to Lotus Notes and Domino

Microsoft Mail to Lotus Domino

Planning and Designing the SMTP Network

Hardware and Software Requirements

The software requirements are as follows:

Lotus Domino Release 5.0 Server

Microsoft Mail Postoffice Requirements

Microsoft Mail Naming Considerations

20 Moving from Microsoft Mail to Lotus Notes and Domino

Case Study: Designing the SMTP Network

Microsoft Mail Environment

ACMESF ACMELA ACMENY

User User User User User User