Moving from cc:Mail to Lotus Domino R5 Moving ... - IBM Redbooks

Moving from cc:Mail to Lotus Domino R5 

Marion Hawker, Harry Blumenstock, Kevin O’Connell 

International Technical Support Organization 

www.redbooks.ibm.com 

SG24-5649-00

xii Lotus Domino Release 5.0: A Developer’s Handbook

International Technical Support Organization 

SG24-5649-00 


November 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. 

First Edition (November 1999) 

This edition applies to Lotus Domino Release 5.x. 

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 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 ........................ 

The team that wrote this redbook ......... 

Comments welcome ................ 

1 cc:Mail basics ................ 

What is the front-end software ........... 

What is a cc:Mail post office ............ 

Compatibility between versions ........ 

User files ...................... 

Main message store ................ 

Post office control files .............. 

What are the administration utilities ....... 

The Admin utility ................. 

The Router utility ................. 

What is Automatic Directory Exchange 

(ADE) ...................... 

What are calllists ................... 

cc:Mail directory terminology ........... 

Aliases .......................... 

Considerations before the migration ....... 

Summary ........................ 

2 Installing and configuring 

the cc:Mail MTA ................. 

7 

Pre-installation tasks ................. 7 

Installing the cc:Mail MTA on Windows 

NT ........................ 8 

Using the Configuration Assistant to 

configure the cc:Mail MTA ......... 10 

Configuring the Domino server ........ 11 

Configuring the cc:Mail post office ...... 22 

Customizing the cc:Mail MTA 

configuration .................. 23 

v 

vi 

vii 

1 

2 

2 

2 

3 

3 

3 

4 

4 

4 

4 

5 

5 

6 

6 

6 

The cc:Mail MTA Server document ...... 24 

The cc:Mail Post Office document ....... 29 

The Connection document ........... 32 

The Foreign cc:Mail Domain 

document .................... 

Summary ........................ 

3 Operating the cc:Mail MTA ...... 

37 

Connectivity between cc:Mail and 

Domino ..................... 37 

Synchronizing the two directories ........ 39 

Populating the Domino Directory 

with cc:Mail names .............. 39 

Populating the cc:Mail directory ........ 42 

Bulletin board coexistence ............. 42 

cc:Mail MTA server configuration ...... 43 

cc:Mail post office configuration ........ 44 

Performing the bulletin board 

synchronization ................ 45 

Public mailing list titles ............... 47 

Propagating public mailing list titles 

into Domino .................. 

Propagating Notes group names to 

cc:Mail ...................... 

Summary ........................ 

4 Migrating from cc:Mail to 

Domino R5 using Domino 

Upgrade Services ............... 

49 

Understanding the Domino Upgrade 

Services (DUS) ................. 49 

Supported cc:Mail versions ............. 50 

What gets migrated from cc:Mail to 

Domino? ..................... 

34 

35 

47 

47 

48 

50 

iii

Notes equivalents for migrated 

Organizer information ............ 52 

Hardware and software requirements ...... 53 

Preparing to migrate cc:Mail users ........ 53 

General administrative tasks .......... 54 

Notes and Domino preparation tasks ..... 54 

cc:Mail preparation tasks ............ 55 

Installing the Domino Administrator 

client with the migration tools ....... 58 

Migrating users from cc:Mail to Lotus 

Domino ..................... 66 

Importing users and groups from a 

cc:Mail post office directory ........ 67 

Migrating Public Mailing Lists 

(Groups) from cc:Mail to Domino ..... 84 

Migrating Organizer information ....... 90 

Registering imported users and 

completing the cc:Mail migration ..... 94 

Checking the logs and verifying that the 

migration was successful .......... 99 

Checking the Notes log file ........... 99 

Looking at the Domino Directory ...... 100 

Checking the migrated Notes mail 

files ....................... 

Verifying that bulletin boards have 

been migrated properly .......... 

Checking the converted Organizer 

files ....................... 107 

Migrating private mailing lists ........ 115 

Testing mail access and mail transfer 

for the migrated users ........... 

Summary ....................... 

5 Migrating personal cc:Mail 

data using the Upgrade Wizard .... 

What is migrated by the Upgrade 

Wizard ..................... 

103 

105 

115 

116 

117 

117 

Installing the Notes client and the 

Upgrade Wizard ............... 118 

Setting up the Notes client ............ 124 

Sending users an upgrade notification 

message .................... 

Running the Upgrade Wizard .......... 

Starting the Upgrade Wizard ......... 

Selecting your user name ........... 

Selecting an upgrade method ........ 

Selecting upgrade options ........... 

Selecting archive conversion options .... 

Performing the upgrade ............ 

Checking if the migration was successful .... 

Summary ....................... 

6 Migrating Organizer data 

with the user migration tool ...... 

An overview of the migration process ..... 

Configuring the general settings ........ 

Migrating Organizer data ............. 

Define Source section .............. 

Click the Button to Export section ...... 

Define Destination section .......... 

Click the Import Button ............ 

Reopen this document to see statistics 

section ..................... 

Summary ....................... 

Special notices ................ 

Related publications ............ 

International Technical Support 

Organization publications ......... 

Redbooks on CD-ROMs .............. 

How to get ITSO redbooks ....... 

IBM intranet for employees ............ 

IBM redbook fax order form ...... 

Index ......................... 

ITSO redbook evaluation ........ 

130 

136 

137 

140 

140 

141 

143 

146 

148 

154 

155 

155 

156 

158 

160 

160 

161 

163 

163 

164 

165 

169 

169 

172 

173 

173 

175 

177 

179 

iv Moving from cc:Mail to Lotus Domino R5

Preface 

This redbook describes how to move from an environment based on Lotus® 

cc:Mail® to an environment based on Lotus Domino R5. 

The first chapter provides an introduction to terms and concepts specific to 

cc:Mail. It is intended for those readers who are knowledgeable in the target 

messaging system, which is Lotus Domino, but require a high-level 

knowledge of the source messaging system, which is cc:Mail. 

Chapter 2 discusses in detail the cc:Mail Message Transfer Agent (MTA). 

First, the pre-installation tasks are covered, followed by a description of the 

installation process. After that, details are given on the configuration of the 

MTA using the Configuration Assistant. Finally, the chapter covers how to 

fine-tune the cc:Mail MTA configuration. 

Chapter 3 documents how to operate the MTA. This includes topics such as 

setting up connectivity between cc:Mail and Domino as well as directory 

synchronization and bulletin board coexistence. 

Chapter 4 explores aspects relating to the migration of cc:Mail users and 

their data to Domino R5 using the administrator-based Domino Upgrade 

Services. First, the chapter provides tables listing the Notes/Domino 

equivalents for migrated cc:Mail data and Organizer® data. Then it shows 

how to prepare cc:Mail users for migration, before describing how to install 

the Domino Administrator client with the Domino Upgrade Services. Finally, 

it demonstrates how to migrate users from cc:Mail to Domino R5. 

Chapter 5 discusses how to migrate personal cc:Mail data using the Upgrade 

Wizard that is provided with the Notes client. The chapter starts out by 

presenting a table that lists the equivalents for personal cc:Mail information 

migrated to Notes. Following that, it describes how to install the Notes client 

with the Upgrade Wizard. It shows how the administrator can prepare and 

send an upgrade notification message to the user. Finally, it gives details on 

how the users can migrate their personal cc:Mail information to Notes R5. 

The last chapter in this redbook discusses the steps involved in migrating 

stand-alone Organizer data to Domino R5 using the user migration tool. 

This redbook was written for customers, IBM® and Lotus business partners, 

and the IBM and Lotus community, who are involved in migrating cc:Mail 

customers to Lotus Domino R5. 

v

The team that wrote this redbook 

This redbook was produced by a team of specialists from around the world 

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. 

Marion Hawker is a Project Manager in the IBM/Lotus Integration Center in 

Westlake, Texas. She is a member of the Domino Enterprise Solutions team. 

Before joining that team, she was a 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 an IBM Certified Project Manager and a Certified Lotus 

Professional in Domino System Administration. 

Harry Blumenstock is a Technical Marketing Support Representative in the 

IBM/Lotus Integration Center in Boeblingen, Germany. He is a member of 

the Domino Messaging Integration team, with 21 years of IBM experience. 

He specializes in LAN e-mail coexistence and migration, providing pre-sales 

technical support as well as delivering technical workshops. Before joining 

the ILIC, he supported several gateway products that establish coexistence 

between host-based and LAN-based messaging systems. Job assignments 

included a four-year stay in the United States. Harry Blumenstock has more 

than seven years of experience in the area of Lotus Notes and related 

products. 

Kevin O’Connell is a Senior Technical Engineer at Lotus Development in 

Canberra, Australia. For the past three years, he has worked as a Field 

Service Engineer for Lotus. He specializes in the design and deployment 

of enterprise coexistence and migration projects, in roles which cover both 

strategic planning and the operational implementation. Prior to joining 

Lotus, Kevin O’Connell was involved in designing and implementing large 

cc:Mail infrastructures. 

Thanks to the following people for their invaluable contributions to this 

project: 

• Brandon Coker, Lotus Development 

• Feridon Farokhnia, IBM/Lotus Integration Center (very special thanks to 

Feridon!) 

• Glenn Matsuda, Lotus Development 

vi Moving from cc:Mail to Lotus Domino R5

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 

http://www.redbooks.ibm.com/ 

• Send your comments in an Internet note to 

redbook@us.ibm.com. 

Preface vii

viii Moving from cc:Mail to Lotus Domino R5

Chapter 1 

cc:Mail basics 

cc:Mail is a cross platform, LAN-based messaging system. Configured and 

monitored correctly, it is stable and provides reliable message delivery. 

It is a store-and-forward mail system that uses file locking to control 

message flow. 

As a product, cc:Mail can be divided into three sections: 

• Front end (the client) 

• Back end (the post office) 

• Administration utilities (maintenance tools) 

This chapter provides an overview of some basic cc:Mail concepts. 

The following topics are covered: 

• What is the front end software 

• What is a cc:Mail post office 

• What are the administration utilities 

• Compatibility between versions 

• What is Automatic Directory Exchange (ADE) 

• What are calllists 

• cc:Mail directory terminology 

• Aliases 

• Considerations before the migration 

• Summary 

1

What is the front-end software 

The cc:Mail client is the front-end software you would use to access the post 

office. It lets you create, send, save, and receive messages. There are a 

number of versions currently on the market, which include 16-bit and 32-bit 

clients. The client software can be run from either a network server or from a 

local machine. 

Each user has a small number of personal files that must be kept in a 

separate personal location. 

What is a cc:Mail post office 

The cc:Mail post office is a set of files located on a network file server. The 

post office is the central repository for cc:Mail messages and addresses. Each 

post office has a mail directory that lists all the people and post offices with 

which you can exchange mail. It contains all of the individual mailboxes 

(files) for local users and for other post offices. 

The cc:Mail post office is a file-sharing database. All cc:Mail applications 

may share the database, and they rely on the network’s file and record 

locking environment to do so correctly. 

The cc:Mail post office can be broken down further into user files, message 

stores, and controlling files. 

Compatibility between versions 

cc:Mail as a product has developed over the years with the most significant 

change happening around two years ago. This was a complete overhaul of 

the back-end post office structure. The new post office structure is known 

as DB8. 

Having a strong backwards compatibility has enabled many cc:Mail 

environments to evolve over the years. The following table shows which 

clients and administration tools can communicate to which back ends: 

DB6 

DB8 

Lotus Domino 

Client Release 2.x 

X 

Client Release 6.0x 

X 

Client Release 6.3x 

X 

X 

Client Release 8.x 

Admin tools 

Release 5.x 

X 

X 

X 

Releases 6-8 

2 Moving from cc:Mail to Lotus Domino R5

User files 

Each user has a separate file for their personal information. In DB6, these 

files always started with USR. These files are known as U files within DB8. 

The following information is kept within these files: 

• The user’s name (as it is known in cc:Mail) 

• The user’s cc:Mail password 

• Personal mailing lists 

• Personal Internet address (this is for DB8 only — in DB6, these addresses 

are kept in the privdir.ini file located in the user’s personal cc:Mail 

directory). 

• A pointer to each message sent or received by the user. 

Users can create personal cc:Mail archives. The location of the archives 

depends on the setting in the wmail.ini file. In general, by default, the 

archives are saved in the user’s personal cc:Mail directory. 

Main message store 

Each post office has a main message store. In DB6, this is called MLANDATA, 

and in DB8, this is called CCPOMS. This is where a single copy of every 

transmitted message is stored. 

If a message is sent to multiple users within a post office, only one copy of 

the message is stored. Each user will have a separate pointer to the message. 

When a message is deleted from a user’s inbox/folder, the pointer is 

removed. Once all pointers have been removed, the message will be deleted 

from the message store. 

Post office control files 

One of the main changes between DB6 and DB8 is the splitting of the 

CLANDATA file. This one file controlled all of the following internal post 

office information: 

• Master index 

• Directory store 

• Message index 

• Message allocation table 

• Free space table 

In DB8, this one file has been split into three files: ccpodd, ccpods, ccpomi. 

Chapter 1: cc:Mail Basics 3

What are the administration utilities 

Tools have been provided to enable cc:Mail administrators to create and 

manage post office directories, message flow, database maintenance, and 

troubleshooting. Most of these are DOS-based command tools, however, the 

later version of Admin (see the following section) is Windows-based. There 

are different versions of the tools for different operating systems. The tools 

perform the same task no matter what operating system is used. 

The Admin utility 

Admin is used to perform administration changes to the cc:Mail directory. 

This includes adding, deleting, renaming, and relocating users. It is also 

used to control calllists, bulletin boards, and mailing lists. 

The Router utility 

If an organization has multiple post offices spread over multiple floors or 

locations, a utility called Router is used to transmit messages between post 

offices. The cc:Mail Router is simply an executable that runs on a workstation. 

The cc:Mail Router moves messages from one post office to another 

across a LAN, across phone lines, or across a wide area network (WAN), 

using TCP/IP, IPX/SPX, APPC, SPP, or X.25. 

What is Automatic Directory Exchange (ADE) 

Automatic Directory Exchange (ADE) is responsible for moving 

non-message information between post offices, such as directory updates, 

bulletin board titles, and mailing list titles. It is not a separate application, 

but consists of code found in the Router and Admin applications. 

For post offices to exchange updates, they require an ADE relationship. 

There are a number of predefined ADE relationships. These ADE relationships, 

or a combination of them, are generally used in multiple post office 

sites. 


What are calllists 

Calllists can be created so that the administrator can control the Router 

utility. The administrator can then determine at what time a router initiates 

a call, and what priority is used to send messages. Also, message size 

restrictions and enforced, for example. Calllists are maintained from within 

the Admin program. 

If a Router does not have any calllist assigned to it and it has no special 

command line parameters, it will sit in a listening state, waiting to be called 

by another Router. 

If you have multiple Router sessions running on one machine (OS/2® or 

NT), calllists let you dictate what sessions are used for calling and what 

sessions are used for listening. 

cc:Mail directory terminology 

Each organization has its own method of assigning users to cc:Mail post 

offices. The cc:Mail administrator determines which post offices are 

connected directly and which ones are reached by routing mail through an 

intermediate post office. 

This information is part of the directory information. Each type of directory 

entry is given a single-character location type that describes the entry’s 

relationship to the post office. The following table lists the different location 

types: 

Type of Entry 

L 

l 

R 

r 

P 

p 

A 

a 

Description 

Local directory entry – a local user whose mailbox resides on this post 

office, and who accesses mail over the network. 

A LAN-based user whose mailbox does not reside on this post office. 

Mobile directory entry – a mobile user whose mailbox resides on this 

post office. 

A mobile user whose mailbox does not reside on this post office. 

Post Office directory entry – a post office that communicates to this 

post office directly. 

A post office that communicates to this post office via another post 

office. 

Alias directory entry – another name that points to an ‘L’ or ‘R’ entry. 

Another name that points to an ‘l’ or ‘r’ entry. 

Chapter 1: cc:Mail Basics 5

Aliases 

Aliases are created for users who receive mail from two or more different 

names. Aliases are sometimes used to temporarily forward mail from one 

user to another. Users that are aliased do not need to be located on the same 

post office. 

Considerations before the migration 

When upgrading any environment, the implementation team usually needs 

to ensure that all current functionality is provided in the new environment. 

This then leads us to the following issues that need to be addressed before 

the migration is started: 

• Gateways — the coexistence and migration of all current gateways needs 

to be addressed. Some gateways to consider would include SMTP, fax, 

pager, and X.400. 

• Stand-alone Organizer — with the integration of calendaring and 

scheduling in Notes/Domino, you will need to decide on what happens 

to Lotus Organizer. Organizer group scheduling can be migrated with 

the back-end migration tools provided by Domino R5, however, standalone 

Organizer needs to be migrated using the migration database that 

comes with the Notes R5 client. This is a user-operated tool. 

• VIM applications — any applications that use VIM calls to the cc:Mail 

post office will not work against a Domino directory. Application 

developers need time to recode applications so that the applications can 

talk to the Domino server. This includes applications that use the cc:Mail 

tools Import and Export. 

• Palm computers — will the facility for synchronizing palm computers 

with the new Domino environment be required? If so, the distribution 

and configuration of tools such as Easysync may be necessary. 

Summary 

This chapter addresses Domino administrators who require a quick 

overview of cc:Mail. We covered the general architecture of the product, 

and gave a short description of some of the key administration tools. We also 

provided a number of short descriptions of the major cc:Mail terminology. 


Chapter 2 

Installing and configuring the cc:Mail MTA 

This chapter describes how your cc:Mail and Domino environments can 

coexist using the cc:Mail MTA. The following topics are covered: 

• Pre-installation tasks 

• Installing the cc:Mail MTA on Windows NT 

• Using the Configuration Assistant to configure the cc:Mail MTA 

• Customizing the cc:Mail MTA configuration 

• Summary 

Pre-installation tasks 

Before installing the cc:Mail MTA, there are several tasks you will need to 

perform first: 

1. If you are upgrading from a previous release of the cc:Mail MTA, make 

sure all pending mail messages have been processed. Shut down the 

Notes Router, then, a few minutes later, stop the cc:Mail Router or 

Routers that communicate with the MTA. 

2. Shut down the Domino server. 

3. We recommend that you back up the Domino program and data 

directories. This information typically resides in the LOTUS\DOMINO 

and LOTUS\DOMINO\DATA directories, respectively. 

4. Verify that you have Designer access to the Domino Directory. 

Note If you are upgrading from a previous release of the cc:Mail MTA, 

you also need Designer access to the MTA server database. 

5. Make sure you remember your Domino server password if you 

specified one. 

6. Make sure the Domino domain name is not the same as any post office 

name. If it is the same name, the post office will need to be renamed. 

7. If you install the cc:Mail MTA on a server where another MTA is already 

installed, for example, the SMTP MTA, and you have modified the 

MTATBLS.NSF database for that MTA, make a copy of MTATBLS.NSF. 

7

To do so, choose File - Database - New Copy. After you have installed 

the cc:Mail MTA, reapply the local modifications from the copy to the 

MTATBLS.NSF file created by the install process. 

8. In a Windows NT environment, ensure that the Domino program 

directory (typically C:\LOTUS\DOMINO) is in your path. Otherwise, 

install will fail with a message that a DLL cannot be found. 

Installing the cc:Mail MTA on Windows NT 

The cc:Mail MTA executable programs and the DLLs need to be installed on 

the Domino server that directly connects to the cc:Mail hub post office. Other 

Domino servers route mail through the MTA using the appropriate design 

elements in the Domino directory. 

Note All of our tests were performed using cc:Mail MTA Version 4.6.5. 

This version can run on either Domino Release 4.6.x or Domino R5. This 

release of the MTA is only available for the Windows NT platform. The 

cc:Mail MTA can be found on and downloaded from the Lotus Web page 

www.lotus.com/migration. 

Follow these steps to install the cc:Mail MTA Version 4.6.x on a Domino 

server running on Windows NT: 

1. We created a temporary directory for the MTA software, and copied the 

self extracting executable (cg6mena.exe) file to the temporary directory. 

Double-clicking on the file, from within Windows Explorer, will 

automatically start the self-extraction. 

2. The WinZip Self-Extractor information dialog box is displayed. Click 

OK to continue. 

3. The next WinZip screen details the location and settings that will be 

initiated by the zip process. Once you are happy with these settings, 

click Unzip. 


Note If you deselect the option called When Done Unzipping Run: 

SETUP.EXE, the install process will stop after the files have unzipped. 

You will then have to manually start the process by double-clicking on 

the SETUP.EXE. 

4. A prompt will appear once the unzip has finished. Click OK. 

5. Setup displays a Welcome dialog. Click Next. 

6. The following screen tells you to shut down your Domino server if it is 

still running. It also warns you to back up the MTATBLS.NSF file if you 

have modified it, for example, to install the SMTP MTA. 

7. If you already have a backup of the file, or do not require a backup, 

click OK to continue setup. Otherwise, exit the install, back up the file, 

and start the install procedure again. 

8. Ensure that the default directories displayed are correct. If these 

directories are not correct, click No, and follow the instructions in the 

section titled “Pre-installation tasks” earlier in this chapter. 

Chapter 2: Installing and configuring the cc:Mail MTA 9

9. The next dialog box informs you of the space required to install the 

MTA, and the space available on the machine. It also gives you the 

option of a typical install and a custom install. 

Note Use typical install unless you have a specific need to perform a 

custom install. 

10. We selected the custom option to demonstrate what options are 

available. Click Next to proceed. 

11. The Lotus Notes cc:Mail MTA files are copied to your Domino server. 

The graphic on the left of the screen shows you the progress of the files 

being transferred. 

When setup displays the message saying “Setup has completed 

successfully,” click OK. 

12. If you created a backup of the MTATBLS.NSF before you started the 

Setup program, add the newly installed MTATBLS.NSF to your Notes 

desktop (File - Database - Open). Then apply the changes to your backup 

copy of MTATBLS.NSF using copy and paste, and replace the new 

MTATBLS.NSF file with your modified backup copy. 

Using the Configuration Assistant to configure the cc:Mail MTA 

You are now ready to configure the MTA. This configuration can be split 

into two sections: 

• Configuring the Domino server 

• Configuring the cc:Mail post office 


Configuring the Domino server 

The Domino-related setup tasks involve editing or creating four documents, 

the Domino server, cc:Mail Post Office server, Domain, and Connection 

documents, in the Domino Directory for the domain in which you installed 

the MTA. These documents provide the information required to route mail 

messages and directory information between cc:Mail and Domino. The 

documents also provide the information needed to run and customize the 

operation of the MTA. 

By replicating the Domino Directory among the other existing servers within 

the Domino domain, all the Notes users within that domain can exchange 

mail with the cc:Mail users. Therefore, you do not need to install the MTA 

on all the Domino servers within your domain. However, if there is a 

requirement for advanced MTA design, you will need to install the MTA 

on all the required Domino servers. 

Adding the Configuration Assistant database 

One of the databases supplied at the time of the cc:Mail MTA install is the 

Configuration Assistant. This database will step you through a standard 

cc:Mail MTA configuration. 

Follow these steps to add this database to your workspace: 

1. Ensure the Domino server is running. 

2. Start your Notes client. 

3. Choose File - Database - Open to add the following databases to your 

bookmarks: 

• cc:Mail MTA Config Assistant 

• cc:Mail MTA Administrator’s Guide 

• cc:Mail MTA 4.6.5 Release Notes. 


4. Click Open. This opens the cc:Mail MTA Config Assistant database. You 

may get the following message: 

5. Click Yes. The view pane of the Configuration Assistant database shows 

the following information: 

Note We are using cc:Mail MTA Release 4.6.5 even though the figure in 

the upper left hand indicates cc:Mail MTA v2.0. 

Read the information displayed, especially the Information You Need to 

Gather section. Ensure you collect all of the required information, such 

as the correct cc:Mail TCPIP ports and addresses. 

6. Once you have finished reading, click the Continue button at the top of 

the view pane. Notice that a checkmark appears next to the Before You 

Begin section in the navigator pane. 


Specifying a Public Address Book 

You are automatically taken to the Specify a Public Address Book section. 

Note In Domino R5, the Public Address Book is called Domino 

Directory. 

1. Click Specify a Public Address Book. A dialog box asks you to select the 

server on which the MTA is installed. In our case, it was 

MTASRV1/ILICDOM. 

2. Click OK. The Enter PAB Filename dialog box appears. Type the path 

and file name of the server’s Public Address Book, and make sure to 

include the .NSF file extension. 


3. Click OK. A checkmark appears next to the Specify a Public Address 

Book section. You are automatically taken to the Set Up or Select the 

MTA server section. 

Selecting the MTA server 

Follow these steps to select the MTA server: 

1. Click the Specify the MTA Server button at the top of the view pane. On 

the following dialog box, select the name of the Domino server where 

the MTA is installed. In our example, this was MTASRV1/ILICDOM. 


2. Click OK. The MTA Server form is displayed in the view pane of the 

Configuration Assistant. Notice how the Set Up or Select the MTA server 

section in the navigator pane has changed to reflect the selected server 

name. In our case, it now reads: MTA Server: MTASRV1/ILICDOM. 

3. Click the Edit Document button to go into edit mode. 


4. The pre-filled field values are based on defaults pulled from the Domino 

server. We left the cc:Mail MTA Password field unchanged. We changed 

the cc:Mail MTA Work Path field to show c:\lotus\domino\data\ 

ccmta_work, which was the work directory we had previously specified. 

Note For better performance and availablity, it is recommended not to 

specify the work path on a network drive. 

Caution The work path must already exist. Otherwise, the MTA will 

report an error when attempting to load. 

5. Ensure the Foreign cc:Mail Domain field shows the appropriate value. 

This is used when a cc:Mail user sends a message to a Notes user. If the 

cc:Mail user is not in the Public Address Book, the MTA will append this 

foreign domain name to the sender’s name. This ensures that the mail 

item can be sent back if the recipient chooses to reply. 

In our case, the name of the foreign cc:Mail domain was 

ccMTA-MTASRV1. 

6. Click the arrow next to Protocol to display the available options. 

7. The Protocol field specifies the network protocol the MTA will use to 

communicate with the cc:Mail post office. The MTA must communicate 

on the same protocol as the cc:Mail Router. The options that are 

available are SPX, TCP/IP at port address Port 21, or TCP/IP at port 

address Port CC0. 

Note All versions of Router prior to Version 5.14 use Port 21. Router 

5.13 can use either Port 21 or Port CC0. Beginning in 5.14, the default 

port number is CC0. This change was introduced because other 

applications sometimes used Port 21. 

8. We selected TCPIP Port CC0. 

9. Click OK. 


10. Click the arrow next to Message Conversion to display the options 

available for the Services available Field. 

11. Select the type of conversion you want. You can choose one of the 

following conversion types: 

• Message Conversion 

• Message Conversion and Directory Conversion 

• Message Conversion and Directory Conversion and Bulletin Board 

Conversion 

We selected Message Conversion and Directory Conversion. 

12. Save and close the document. A checkmark has been placed next to 

MTA Server: MTASRV1/ILICDOM. 


Specifying a post office 

Domino views the cc:Mail topology as a series of Domino servers within the 

Domino domain. Therefore, you need to create a definition within Domino 

that this cc:Mail environment exists. You do this by adding a document that 

is called a cc:Mail Post Office Server document. 

1. Click the Specify a Post Office button at the top of the view pane to start 

providing post office information. 

2. On the following dialog box, enter the name of the post office that the 

cc:Mail MTA will connect to. This is usually the top-most post office in 

the cc:Mail topology, sometimes referred to as the hub post office. In our 

example, we typed ILIChub. 

3. Click OK. This opens a form that lets you specify information for the 

cc:Mail Post Office Server document. 


4. We had to modify some of the values displayed. 

We typed a value for the cc:Mail call password to be used from your 

cc:Mail post office. 

Tip To determine the call password for the post office, run Admin 

against the post office. On the main screen of Admin, the call password 

is shown in the Post Office section. If it is blank or greyed out, it is the 

same value as the post office password. 

5. Specify a value for the cc:Mail Subnet Name field. 

Note A cc:Mail subnet is analogous to a Notes Named Network. The 

name you specify must be different from any other Notes Named 

Network you already have in place. It also must be different from any 

existing Domino server name or Domino domain name. It cannot be left 

blank. 

We changed the cc:Mail subnet name to ILIChub-subnet-tcpip. 

6. Click the arrow next to Propagation Type to display the available options. 

The following options are available 

• Broadcaster 

• Division 

• Enterprise 

• None 

7. We selected Broadcaster. Click OK. 

Note Depending on the number of MTAs in your domain and in the 

cc:Mail topology, you can specify a propagation type other than 

Broadcaster. For more details on this topic, refer to Chapter 6 in the 

redbook The Next Step in Messaging: Upgrade Case Studies for Lotus cc:Mail 

to Lotus Domino and Lotus Notes, Lotus part number 12992, IBM order 

number SG24-5100. 


8. The check box next to “Do you want to turn on call scheduling for this 

post office?” will initiate calls from Domino. By default, the MTA calls 

the post office once every six hours between 8 AM and 10 PM, seven 

days a week. After you finish using the Configuration Assistant, you can 

modify this schedule by editing the Connection document for this post 

office. 

9. The Protocol field shows the transport method you will be using to 

connect cc:Mail and Domino. This is a non-editable field, and the value 

is automatically gathered from the Server document. 

10. In the Net Address field, type the network address of the machine where 

your cc:Mail Router is running. In our example, we specified a TCP/IP 

address. 

11. The Target Public Address Book field should show the file name of the 

Domino Directory into which the cc:Mail directory will be populated. 

This does not have to be the main Domino Directory. It can also be a 

secondary directory, cascaded under the main Domino Directory. 

12. The Source Public Address Book field should show the file name of the 

Domino Directory from which the cc:Mail directory will be populated. 

There can be multiple address books listed here. 

13. Save and close the document. You can now see a checkmark next to 

Provide post office information ILIChub. 


Note The Configuration Assistant has also created the following two 

documents: 

• A Connection document for the cc:Mail post office 

• A Foreign Domain document to route mail to cc:Mail users whose 

names are not in the Domino Directory. 

Updating the Public Address Book 

The following steps apply the proposed changes to the Domino Directory. 

1. Click the Continue button to move to the next step, which is Upgrade the 

Public Address Book. 

2. Click Yes to confirm that you want to update the Public Address Book. 

3. Click OK on the dialog box which tells you that the Public Address Book 

has been updated. 

4. Scroll down the view pane of the Configuration Assistant and check for 

changes listed in the Public Address Book Changes section. 

Starting to set up the MTA in cc:Mail 

Next, you need to set up the MTA in cc:Mail. Click the Continue button. The 

view pane gives you instructions on how to set up the MTA in cc:Mail. 


Configuring the cc:Mail post office 

Follow these steps to configure the MTA in cc:Mail: 

1. Go to your cc:Mail post office machine. In our case, this was ILIChub. 

2. Bring up Admin. 

Note We used cc:Mail Admin 8.5 to perform these tasks. 

3. Choose manage Mail directory. 

4. Add a post office of the same name as your Domino domain. In our case, 

this was ILICDOM. 

5. Make sure that you do not already have an existing post office of the 

same name. 

6. Set the location as a post office (P). 

7. To specify the cc:Mail address, type the network address of the Domino 

server where the MTA is installed. In our case, we specified a TCP/IP 

address. You would specify this address only if your cc:Mail Router calls 

the MTA. 

8. Set the Propagation Type to be the same as you set in the Post Office 

document in the Domino server. In our example, we set this to 

Broadcaster. 

Note In those cc:Mail configurations where the default ADE profile for 

the post office has been set to Subordinate, you need to change the 

default to None before setting the propagation type to anything different 

than Subordinate. If the default remains at Subordinate and you are 

specifying a different propagation type for a new post office entry, then 

the ADE will not work properly. You can change the default ADE back 

to the original value after you have finished adding the new post office. 

Also, if a ~ADE_Mailbox post office entry exists in your cc:Mail 

directory, the ADE messages will be captured by this post office and will 

be propagated depending on the calllist settings in your cc:Mail post 

office. You may need to check the calllist settings for this entry, when 

you set up a coexistence environment between cc:Mail and Domino, and 

change the call time to more frequent intervals in order to see the results 

immediately. 


Note If you are planning to synchronize Public Mailing Lists into 

Domino, some custom changes need to be made to the propagation 

settings. Details on these settings can be found later in this chapter in the 

section titled, “The cc:Mail Post Office document.” 

9. Exit Admin and type y for yes to propagate your ADE changes. 

Customizing the cc:Mail MTA configuration 

In this section, we will look at the finer points of configuring the cc:Mail 

MTA. 

For the cc:Mail MTA to work correctly, four Server documents in the 

Domino Directory need to be updated or created. The Configuration 

Assistant creates these documents for you, however, sometimes you need to 

fine-tune the configuration to better suit the environment. 

The four documents that need to be changed are: 

• The cc:Mail MTA Server document 

• The cc:Mail Post Office document 

• The Connection document 

• The Foreign cc:Mail domain document 

The following sections describe how to customize these documents. 


The cc:Mail MTA Server document 

Perform the following steps to change the cc:Mail MTA Server document: 

1. Using the Domino administration client, select the cc:Mail MTA Server 

document from the All Server Documents view from the Configuration 

tab. 

2. Open the server document. In our example, this was 

MTASRV1/ILICDOM. 

3. From the Basics tab, check that the Routing tasks field has both Mail 

Routing and ccMail Routing specified. If either one does not appear, 

click the arrow to display the available options, and select the required 

setting. 


4. Click the MTAs tab, then the cc:Mail MTA tab. In our example, the 

General section is displayed: 

5. In the General section, note the Active message retries field, which sets 

the number of times that the cc:Mail MTA attempts to reprocess an 

active message on restart before it moves it to the Bad Message queue in 

the CCMCWQ.BOX file. This number should be set to 1 or 2. 

6. The Loop detection field in the Control section tracks how many times a 

message can bounce between cc:Mail and Domino. The default is 10. 

7. When the Send administrator notice of NDNs field is Enabled in the 

Control section, the cc:Mail MTA administrator receives notification 

whenever the cc:Mail MTA generates a Non Delivery Report for a 

message. The default is Disable. 

8. The Process Timeout Control section lets you define the number of 

minutes before the cc:Mail MTA will restart once it has come across a 

problem. 

The Warning Message Timer field specifies the number of minutes that 

the cc:Mail MTA will wait to hear from an MTA process before it logs a 

warning message indicating that the process is not responding. 

The Restart timer field specifies the number of minutes that the cc:Mail 

MTA will wait to hear from a non-responsive process before it initiates 

a restart. This setting takes effect only after the Warning Message Timer 

has expired and if cc:Mail MTA Restart is enabled in your configuration. 

This value should be at least twice the value of the Warning Message 

Timer. Lotus recommends setting the Restart timer to a minimum of 

30 minutes. 


Note For information on the auto-Restart feature of the MTA, refer to 

the cc:Mail MTA Administrator’s Guide in the section titled, “About 

auto-restart of the MTA.” 

9. Use the “Enable compaction,” “Start compaction at,” and “Perform 

compaction every” fields to automatically remove unusable space in the 

work queue database (CCMCWQ.BOX) and in the mailbox on the 

cc:Mail MTA server (CCMAIL.BOX). 

10. The options in the Queue monitoring section enable you to set thresholds 

of delayed mail. If these thresholds are met, an event will be created, thus 

providing statistics and events for the cc:Mail MTA outages. 

Note The settings for these fields depend on the volume and the types 

of messages that are typical for your system. If your mail volume is 

large, or if you frequently have messages that take a long time to 

process, you will want to set these values to be larger numbers. 

11. Scrolling further down, we come to the Message Conversion 

Configuration section. 


12. The first part of this section, Control, is used to set general configurations. 

A useful feature in this section is the message size limit. This lets 

you control the size of messages as well as the time range within which 

those large messages can be passed between cc:Mail and Domino. 

13. The Inbound Conversion and Outbound Conversion sections control the 

messages being sent from cc:Mail to Notes and from Domino to cc:Mail, 

respectively. The settings in these sections are used to ensure that cc:Mail 

users can read the messages they have received from Domino, and the 

other way round. We will only point out three fields from these sections: 

• Number of inbound message processes 

This is the number of inbound (cc:Mail to Notes) message conversion 

processes that the MTA will start up at initialization. The default 

value is 1. 

• Number of outbound message processes 

This is the number of outbound (Notes to cc:Mail) message 

conversion processes that the MTA will start up at initialization. The 

default is 1. 

The combined total of the inbound and outbound message processes can 

be no larger than 16. How this is split depends on your specific 

environment. 

• cc:Mail forward information handling 

This setting applies only to messages received from cc:Mail. Use this 

field to set how the cc:Mail MTA handles the forward history 

generated by cc:Mail. The default is to embed the forwarding history 

in the message. 

14. Scroll down and expand the Directory Conversion Configuration 

section. It looks like this: 

15. The Directory Log Level field shows the severity, or log level, of the 

directory conversion messages that the MTA writes to the Notes log. 

16. You would specify a value in the Propagation of names field if you use 

the MTA to connect two or more post offices through a multi-domain 

Notes backbone, and if you also use different user name formats in the 

two post offices. This field works in conjunction with the field titled 

“User name format in cc:Mail messages” in the Domino Server document. 

For more information, refer to the cc:Mail: MTA Administrator’s Guide in 

the section titled, “About customizing information exchange.” 


17. Registered Notes users on cc:Mail field: If you enter information on your 

cc:Mail users into the Domino Directory without using directory 

conversion, and then try to synchronize the directory with a cc:Mail post 

office, directory conversion may consider the cc:Mail names in the 

Domino Directory to be of “Notes origin” and will reject the changes 

intended for those users. 

To force directory conversion to accept changes for cc:Mail users that 

already appear in the Domino Directory as Notes users, enable 

“Registered Notes users on cc:Mail” in the Server document before you 

begin using directory conversion. This setting allows directory 

conversion to update the Person documents for the cc:Mail users in the 

Domino Directory with the necessary information when you use 

directory conversion for the first time. 

18. The field titled Build Notes short name for cc:Mail users is disabled by 

default, however, it should be enabled if you require every user to have 

a short name. This will add a short name for those users that are 

propagated to Domino from cc:Mail. The short name will always follow 

the format of first initial of the first name, followed by the last name of 

up to 8 characters. 

19. Apply all directory update messages field: By default, each time the 

update messages process initiates, it will apply only the first update 

message. Enabling this option means that all update messages that are 

queued will be applied. Note that this extra workload may slow down 

the message conversion tasks. 

20. The next twisty that can be expanded is the Bulletin Board Conversion 

Configuration. In this section, you can set the bulletin board log level 

and the bulletin board conversion processing interval. 

21. Scroll down and expand the Message Transport Configuration section. It 

looks like this: 

22. If required, this is where you can change the protocol you are using to 

communicate between cc:Mail and Domino. 


23. You can also modify the number of inbound and outbound sessions. This 

will depend on the number of listening and calling sessions that you have 

in cc:Mail. The total number of inbound and outbound sessions cannot 

exceed 16. For example, you can specify either 16 outbound sessions and 

0 inbound sessions, or you can specify 8 outbound and 8 inbound 

sessions. 

24. The Number of Data Connection Lost retries setting lets you specify the 

number of times that the MTA will attempt to resend a message that 

causes a Data Connection Lost (DCL) to be generated by the cc:Mail 

Router before it will move the message to the bad message queue in the 

ccmcwq.box file. If this field is set to zero, then messages will continue to 

be retried, but not moved to the bad message queue. 

This enables mail to continue to flow, while saving the message so the 

administrator can resolve the problem. 

The cc:Mail Post Office document 

We are now going to step you through the Post Office document. 

1. Open the All Server Documents view on the Configuration tab. 

You will notice that a document has been created by the cc:Mail 

MTA Configuration Assistant. It looks like this: 

2. Double-click on the Post Office document to open it. 


3. The Post Office Code Page field located in the Basics section only 

requires changing if the post office that the cc:Mail MTA is connecting 

to does not have code page 850 (International English) specified. 

4. If your cc:Mail users are using Release 8 of the cc:Mail client, you can 

enable the cc:Mail Rich Text Conversion Support field. If your post 

offices are still DB6, then rich text is not supported. 

5. Scroll down the post office document to view the next sections. 

6. In the Basics part, the ADE Connected PO field shows the name of the 

post office from which ADE updates destined for Notes will come. In 

our case, this was ILILhub. 

7. In the Full Name Propagation field, you can specify the way Notes user 

names appear in the cc:Mail post office. Select Last(Comma) First Middle 

if you want directory conversion to compose a post office directory entry 

for each Notes user using the contents of the Last name, First name and 

Middle initial fields of the corresponding Person document. The other 

options are First Full Name, First Hierarchical Name, and Nth Full Name. 


8. If you select Nth Full Name in the Full Name Propagation field, you 

must enter a number in the Nth Full Name Prop field. For example, if 

you want to use the third full name listed in the User name field in each 

Person document for the name of each Notes user to be converted to a 

cc:Mail directory entry, you would type 3 in the Nth Full Name Prop 

field. 

If you choose to use Nth Full Name and if that full name does not exist 

in the user’s Person document, the cc:Mail MTA will use the last full 

name. 

9. In the Filters part, you can limit what directory entries get propagated 

between cc:Mail and Notes. You can control such things as domains, 

servers, and post offices. 

10. Scroll down a bit and check the Propagation part of the Directory 

Conversion Configuration section. 

11. Under Propagation Notes to cc:Mail, the default for Mail-In Databases is 

Disabled. This does not allow cc:Mail users to send mail to Notes mail-in 

databases. 

12. The default for Group (to cc:Mail Mailing Lists) is Disabled. This does 

not allow cc:Mail users to send mail to users in Notes groups. 

Note Notes group names are propagated to cc:Mail as mailing-list 

titles. If you decide to enable groups to propagate between cc:Mail and 

Domino, you will need to make some custom ADE propagation changes. 

You will need to open the post office entry (P) for your Domino domain 

on the cc:Mail connected post office and change the propagation settings 

to send and receive mailing lists (L). 

13. Under Propagation cc:Mail to Notes, the default for Mailing Lists (to 

Notes Groups) is Disabled. This does not allow Notes users to send mail 

to users listed in cc:Mail mailing lists. 


14. Alias names are propagated to Notes so that Notes users can address 

mail to cc:Mail users using their cc:Mail alias names. 

Note A separate Person document is created for each alias name. 

Therefore, we recommend turning off the propagation of aliases. 

15. When the Lotus Organizer information field is enabled, the Organizer 

information will be propagated from one system to another. In the case 

of cc:Mail to Notes propagation, the contents of the Organizer comment 

fields will appear in the Person document in Notes as a hidden field. 

If you are planning for either coexistence between Organizer and 

Notes/Domino, or migration of Organizer data to Notes, then you 

should enable this option. 

16. Scroll down a bit and check the Message Transport Configuration 

section. The cc:Mail MTA Configuration Assistant should have correctly 

populated the settings in this section. 

The Connection document 

Perform the following steps to fine-tune the Connection document: 

1. In the navigator pane, under Messaging, open the Connections view. It 

looks like this: 

2. Open the Server connection document that the Configuration Assistant 

created for ILIChub. In our case, it looked like this: 

3. Under the Basics tab, the Connection type field should show a value of 

cc:Mail. 

4. The Source server field should show the name of the Domino server that 

is running the cc:Mail MTA. 


5. The Source domain field should show the name of the Domino domain 

that is running the MTA. 

6. The Use the port(s) field should show the port used by the MTA to 

connect to the post office. 

7. The Destination post office field should show the name of the cc:Mail 

post office to which the MTA will connect. 

8. The Destination domain field should show the name of the Domino 

domain that is running the MTA. 

9. Select the Schedule tab. It looks like this: 

10. In this section, you may want to change the Repeat interval of field to 

better reflect the needs of your environment. For the purpose of our test 

environment, we changed it to a very low value so that we could quickly 

test connections as required. 

Tip You may want to set up multiple Connection documents if you 

want the MTA to call Router more frequently during peak times, for 

example, and less frequently during off-peak times. 

However, avoid overlapping Connection documents that contain the 

Call Post Office task. The cc:Mail MTA can use only one outbound 

calling session for a specific post office, and conflicts between 

Connection documents can cause unexpected calling behavior. 

11. The cc:Mail tab should look like this: 


12. The Configuration Assistant will update the Tasks settings. If you 

require, you can change this setting by displaying the available options. 

The following keyword box appears. 

13. Select the options that you require and click OK. 

14. If you have made changes, save the document, then close it. 

The Foreign cc:Mail Domain document 

Perform the following steps to fine-tune the Foreign cc:Mail Domain 

document: 

1. In the navigator pane, under Messaging, open the Domains view. 

The Configuration Assistant has created a Foreign Domain document to 

route mail to cc:Mail users who are not in the Domino Directory. 


2. Open the document for ccMTA-MTASRV1. There are only two settings 

in this document that can be changed. These can be found in the Mail 

Information tab. It would be very unusual to have to change either of 

these settings. In our case, it looked like this: 

Summary 

This chapter first provided information on the tasks you would typically 

complete before installing the cc:Mail MTA. 

We then described how to install the cc:Mail MTA on Windows NT, and 

how to use the Configuration Assistant to configure the MTA. This process 

consists of a number of steps to be performed on both the Domino server 

side as well as the cc:Mail post office side. 

Finally, we documented how to fine-tune the configuration by changing 

specific values in several documents created by the Configuration Assistant. 


Chapter 3 

Operating the cc:Mail MTA 

In this chapter, we will look at everyday operations of the cc:Mail MTA. 


• Connectivity between cc:Mail and Domino 

• Synchronizing the two directories 

• Bulletin board coexistence 

• Public mail list titles 

Connectivity between cc:Mail and Domino 

In the previous chapter, we described how to configure the cc:Mail MTA in 

both Domino and cc:Mail. We are now ready to initiate the first connection 

between the two environments. 

Either the cc:Mail MTA or the cc:Mail Router can initiate the connection. In 

our case, we let the cc:Mail Router perform this task. 

Note For the cc:Mail MTA to initiate the connection, the settings in the 

Connection document are used. 

1. To load the cc:Mail MTA, at the Domino server console, type load ccmta. 

A number of tasks will be started, as shown in the following figure: 

37

2. It is advisable to add the MTA as a server task to the NOTES.INI file on 

the Domino server. To do so, open the NOTES.INI file in edit mode and 

go to the Server Task line. At the end of the line, add ccmta. Next time 

the server starts, the MTA will load automatically. 

Tip You can stop the MTA by typing tell ccmta q. 

3. In cc:Mail, we created a calllist entry that will initiate a call from cc:Mail 

to Domino every 5 minutes. It looks like this: 

4. The cc:Mail MTA will automatically accept the connection from the 

cc:Mail Router. It knows that the call comes from the cc:Mail Router 

because the call is made on TCPIP Port CC0. This connection will send 

both inbound and outbound messages, as shown in the following figure: 

The cc:Mail Router will continue calling the cc:Mail MTA every five 

minutes. This time frame can be adjusted depending on the amount of 

mail flowing between the two environments. 


Synchronizing the two directories 

To enable easy addressing of messages between Domino and cc:Mail, we 

need to populate the Domino Directory with the cc:Mail user names and 

then populate the cc:Mail directory with the Domino users. 

Before you transfer directory information from cc:Mail to Domino, and from 

Domino to cc:Mail, now is a good time to review the contents of both 

directories. 

Over a period of time, a number of inconsistencies can occur in both 

directories. For example, local accounts can be created that are never used. 

Maybe several employees have left the company, but the administrators 

were not notified. These and many other scenarios can leave a large number 

of out-of-date directory entries. 

Populating the Domino Directory with cc:Mail names 

To populate the Domino Directory with the cc:Mail directory entries, follow 

these steps: 

Important It is advisable to make a backup copy of both the cc:Mail hub 

post office and the Domino directory before you start. 

1. You may want to confirm that the propagation settings are correct in 

both cc:Mail and Domino before proceeding. 

In Domino, the propagation settings can be found in the Directory 

Conversion Configuration section of the cc:Mail Post Office document. 

In cc:Mail, it is a field that can be set within the Domino domain entry 

that can be located in the cc:Mail directory. In our scenario, we 

configured both the setting in the cc:Mail Post Office document as well 

as the field in the Domino domain entry to be Broadcaster. 

2. Directory synchronization can be scheduled using the cc:Mail calllist or 

Domino Connection documents. Directory synchronization is, for the 

most part, a one-time operation. Once the directory is brought over, it is 

maintained through ADE. 

In our example, we had the MTA perform a one-time call to the cc:Mail 

Router. 

Note To perform the initial directory synchronization, you could also 

use the cc:Mail Router to make an express call into the MTA. 

3. To initiate the directory synchronization, there is a series of commands 

you need to type at the Domino server console. First, type: 

tell ccmta request po_name (in our case: ILIChub) 

The cc:Mail MTA will create a request for synchronization (from 

ILIChub in our example). 

Chapter 3: Operating the cc:Mail MTA 39

4. When the directory conversion displays a message indicating that it has 

finished processing, initiate a call to the cc:Mail post office to send the 

request by typing: 

tell ccmta call poname=po_name (in our case: ILIChub) 

5. The cc:Mail Router receives the synchronization message and creates an 

ADE (Automatic Directory Exchange) which is then sent back to the 

cc:Mail MTA. 

Note Depending on how long it takes to build the ADE messages, the 

ADE may not get sent back to the cc:Mail MTA in the current 

connection. If this occurs, just initiate another call between Domino and 


Domino will receive the ADE message as it would any normal messages. 

6. To process the message you previously received from cc:Mail, type: 

tell ccmta applyade 

The Domino server applies the ADE messages, which creates a Person 

document in the Domino Directory for each cc:Mail user. 

This is what the synchronization process looks like: 

Note The applyade is scheduled to run automatically. The setting can 

be found in the Directory Conversion Configuration section of the MTA 

tab in the Server document. By default, it is set to every 10 minutes. 

Tip If the cc:Mail MTA indicates that it failed to apply some of the 

users, you can investigate what users were affected and what the 

problem was by looking in the Domino log on the cc:Mail MTA. 

7. To make sure all of the users have completely synchronized into the 

Domino Directory, open the People view from the People & Groups tab. 

All of the cc:Mail users will be listed among the Domino users. 


The mail tab on a Person document for a cc:Mail user will look like this: 

8. During the first synchronization, post offices that aren’t directly 

connected to the Domino server will also synchronize into the Domino 

Directory. A Server (Post Office) document is created for each post 

office. To check that this occurred correctly, look at the All Server 

Documents view in the Server section of the Configuration tab. It should 

look like this: 


Populating the cc:Mail directory 

To enable cc:Mail users to send mail to Domino users, we must populate the 

cc:Mail directory with the entries for the Domino users. 

An express call from cc:Mail to Domino is used when this process is initiated 

from cc:Mail. Here we will discuss the process when it is initiated from 

Domino. 

1. From the Domino server console, type the following command: 

tell ccmta sync po_name (in our case: ILIChub) 

This command generates an ADE message that includes the names of all 

the Notes users listed in the Directory. This message is stored in the 

CCMAIL.BOX database file. 

2. The synchronization message must be sent to cc:Mail, which can be done 

by typing the following: 

tell ccmta call poname=po_name (in our case: ILIChub) 

The synchronization message is pushed to the cc:Mail Router, and the 

cc:Mail Router applies the ADE update to ILIChub. 

Note If the directly connected post office is using an ~ADE-Mailbox, 

the synchronization message will not be applied until the ~ADE-Mailbox 

is next scheduled to run. 

The synchronization process may take several hours if you have a large 

Domino Directory or cc:Mail directory. It’s not just the updating of people 

documents, but also the Directory may require reindexing. 

Bulletin board coexistence 

There is a difference between the coexistence of bulletin boards and the 

migration of bulletin boards. For coexistence, you enable messages to flow 

from cc:Mail bulletin boards to Domino discussion databases and vice versa. 

The migration of bulletin boards involves moving the messages out of the 

bulletin boards and into a discussion database. 

For bulletin board messages to flow between cc:Mail and Domino, some 

configuration changes are required on both sides. 


cc:Mail MTA server configuration 

Follow these steps to set up bulletin board propagation. 

1. Open the cc:Mail MTA Server document in edit mode. 

2. In the cc:Mail Message Transfer Agent (cc:Mail MTA) section, under 

General, specify the option called Message Conversion and Directory 

Conversion and Bulletin Board Conversion in the Services available 

field. It looks like this: 

3. In the Bulletin Board Conversion Configuration section, you may also 

want to set the log level and polling time. In our example, it looked like 

this: 

Important Once configured, bulletin board messages flow from cc:Mail 

to Domino as “regular” bulletin board messages. This means that the 

cc:Mail Router needs to exchange both mail messages and bulletin board 

messages by using EXCH/MBD. However, messages posted in the MTA 

Bulletin Board Exchange database that need to be sent from Domino to 

cc:Mail depend on the polling frequency defined in the cc:Mail MTA 

Server document. Bulletin board deletions that flow from Domino to 

cc:Mail also depend on this polling time. If you have heavy bulletin 

board message traffic from Domino to cc:Mail, you may want to reduce 

the polling time interval. The default is 10 minutes. 


4. Open the cc:Mail Post Office Server document of the post office your 

cc:Mail MTA connects to in edit mode. 

5. In the Propagation section, enable Mail-In databases from Notes to 

cc:Mail and enable Bulletin Boards from cc:Mail to Notes, as shown in 

the following figure: 

cc:Mail post office configuration 

Follow these steps to configure the cc:Mail post offices: 

1. Using cc:Mail Admin, open the post office that your cc:Mail MTA 

connects to. 

2. Choose the bulletin boards you wish to propagate to the cc:Mail MTA 

Bulletin Board Exchange discussion database and add the Domino 

domain post office entry to its propagation lists. This is shown in the 

following figure: 


3. Verify that bulletin board title propagation is set to yes. 

4. Make sure the Domino domain post office entry is configured to send 

and receive bulletin boards. To do so, enable the B flag on the send and 

receive side of the propagation settings — this is done by default with a 

broadcaster-to-broadcaster relationship. 

5. Run a directory synchronization between cc:Mail and the cc:Mail MTA 

server. This can be done from either the cc:Mail Router or through a 

directory synchronization request from the cc:Mail MTA to cc:Mail. 

Important Any time you wish to exchange a new bulletin board title 

between cc:Mail and Domino, you will need to perform the steps listed 

above. 

Performing the bulletin board synchronization 

Follow these steps to perform the bulletin board synchronization: 

1. On the cc:Mail MTA Domino server, type the following command: 


This clears out any ADEs that may be waiting to be applied. 

2. From the cc:Mail Router, make an express call, with the following 

syntax: 

ntrouter Domino_domain_name post_office_path modem/none exch/bs 

This command will create a special ADE message that will be sent to the 

cc:Mail MTA. 

3. From the cc:Mail MTA, type the following command: 



This applies the bulletin board titles to the Domino Directory. The 

bulletin board titles can be found in the Mail-In Databases and 

Resources view of the People and Groups tab, as shown in the following 

figure: 

Note All the bulletin boards start with a ‘#’ (the pound sign) and they 

all refer to CCMTABBX.NSF as their database. A template for this 

database was added when the cc:Mail MTA was installed. 

4. The last command that needs to be typed at the cc:Mail MTA console is: 

tell ccmta applybbx 

This applies the bulletin board messages to the database. 

Tip If the bulletin board messages do not get added to the database, 

make sure that all the bulletin board titles exist as categories in the 

cc:Mail Bulletin Board Exchange database. If this is not the case, go 

through the steps outlined in this chapter one more time. 


Public mailing list titles 

Public mailing lists as a whole are not brought into Domino, only the titles 

are synchronized into the Domino Directory. This enables Domino users to 

send messages to the groups of people that make up the public mailing lists. 

They appear as groups in the Domino Directory, and they can be identified 

in the group list by a leading #. 

Propagating public mailing list titles into Domino 

To propagate public mailing list titles into Domino, follow these steps: 

1. From a Notes workstation, open the Domino Directory. Open the cc:Mail 

Post Office Server document in edit mode. 

2. Enable the field called Mailing Lists (to Notes Groups) under 

Propagation cc:Mail to Notes to propagate mailing-list titles to Notes. 

This is shown in the following figure: 

3. Save and close the document. 

4. In the cc:Mail post office directory, you have to ensure that title 

propagation is set on for the public mailing list you wish Domino users 

to have access to. 

After you have completed this procedure, you must resynchronize the target 

Domino Directory with the cc:Mail post office directory. 

Propagating Notes group names to cc:Mail 

Each Notes group name propagated to cc:Mail appears as a mailing-list title 

in the cc:Mail post office. 

To convert the group name to a mailing-list title, the cc:Mail MTA adds a # 

(the pound sign) to the beginning of the group name. The cc:Mail MTA can 

only support Mail-only and Multi-purpose groups. 

Tip The cc:Mail MTA will truncate any group names that exceed 29 

characters. 


If you do not want to propagate all of the group titles into the cc:Mail post 

office directory, you can make a small configuration change. 

1. Open the Domino Administration client. 

2. Select the group you do not want propagated. 

3. Change the Foreign directory sync allowed field from Yes to No. This 

can be found on the Administration tab. 

Once you have selected the groups that you wish to propagate, follow these 

steps: 

1. Open the Domino Administration client. 

2. Open the cc:Mail Post Office document in edit mode. 

3. Enable the field called Groups (to cc:Mail Mailing Lists) under 

Propagation Notes to cc:Mail. This is shown in the following figure: 

4. Save and close the document. 

5. You must resynchronize the Domino Directory with the cc:Mail post 

office directory. 

Summary 

This chapter described aspects relating to the operation of the cc:Mail MTA. 

First, we covered how to initiate the connection between cc:Mail and 

Domino using either the cc:Mail MTA or the cc:Mail Router. 

Then we documented how to synchronize the two directories by populating 

the Domino Directory with cc:Mail user names and then populating the 

cc:Mail directory with Domino user names. 

Finally, we provided details on bulletin board coexistence, and how you can 

synchronize public mailing list titles into the Domino Directory. 


Chapter 4 

Migrating from cc:Mail to Domino R5 using 

Domino Upgrade Services 

This chapter discusses one of the migration tools provided by Lotus Domino 

R5. We will cover the administrator-based Domino Upgrade Services (DUS). 

The migration tools based on the Domino Administrator client enable you 

to import cc:Mail users and groups from a selected server-based post office, 

register them as Notes users, and migrate the contents of their cc:Mail 

mailboxes to Lotus Domino R5 mail files. The tools also convert 

Organizer 2.x Group Scheduling files (.OR2 files) to Lotus Notes data. 

The following topics are covered in this chapter: 

• Understanding the Domino Upgrade Services (DUS) 

• Supported cc:Mail versions 

• What gets migrated from cc:Mail to Domino? 

• Notes equivalents for migrated Organizer information 

• Hardware and software requirements 

• Preparing to migrate cc:Mail users 

• Installing the Domino Administrator client with the migration tools 

• Migrating users from cc:Mail to Lotus Domino 

• Checking the logs and verifying that the migration was successful 

Understanding the Domino Upgrade Services (DUS) 

Lotus Domino R5 provides two sets of tools for migrating users from cc:Mail 

to Domino: The administrator-based migration tools, which can be selected 

as an option when installing the Domino Administrator client, and the end 

user Upgrade Wizard, which installs as an option of the Notes client. 

The administrator-based tools are also referred to as Domino Upgrade 

Services (DUS). The following describes the Domino Upgrade Services. 

Using the cc:Mail to Notes migration tool in the Domino Administrator, you 

can import cc:Mail users and groups from a selected post office and register 

them as Notes users. The migration process: 

49

Supported cc:Mail versions 

• Imports local users, groups and passwords from the post office (users in 

the directory whose locations are designated as L or R ) and creates 

entries for them in the Domino Directory. 

• Creates a Notes ID and mail file for imported users 

• Migrates the contents of mailboxes from the cc:Mail post office server 

• Converts Organizer 2.x for cc:Mail Group Scheduling files (.OR2 files) 

into Notes group scheduling format (.NSF) 

The cc:Mail to Notes migration tool supports migrating users who are 

currently using the cc:Mail Release 6.3x client. After the migration completes, 

the cc:Mail 6.3x client accesses a mail file on the Domino server, rather than a 

mailbox on the cc:Mail post office. 

There are two versions of the cc:Mail LAN post office database in use. They 

are commonly referred to as DB6 and DB8. The cc:Mail to Notes migration 

tool lets you migrate data from either database version. Upgrading from 

either version of the cc:Mail post office extracts information from the 

following: 

cc:Mail post office directory — The directory contains public post office 

information, including the post office name and directory entries, public 

mailing lists, and bulletin boards. 

Message file — The message store file keeps one copy of each message for 

all users in the post office. To save disk space, messages addressed to 

multiple users are stored just once in this file. 

Post office user files — The user files contain all private mailbox 

information, such as private mailing lists and folders. These files contain 

no messages, just pointers to the mail directory and message files. 

Organizer 2.x group scheduling files (.OR2 files) — For cc:Mail users who 

use Lotus Organizer 2.x, the OR2 files contain calendaring and scheduling 

information. 

Note Since the migration tools work exactly the same with cc:Mail DB6 and 

DB8 databases, we decided to use only DB8-based cc:Mail post offices when 

we wrote this redbook. 

What gets migrated from cc:Mail to Domino? 

The cc:Mail to Notes migration tool converts information in a cc:Mail post 

office to Notes/Domino, including mailboxes, messages, bulletin boards, 

and private and public directories, as shown in the following table. 


Items in cc:Mail … 

Archives 

Bulletin boards 

Bulletin board messages on mobile 

post offices 

Clipboard folder 

Folders and subfolders 

Message date 

Message priority 

Messages and attachments in 

migrated folders 

Mobile sessions log 

Password 

Post office directory 

Private mailing lists 

Public mailing list 

Read and unread marks 

Return receipts 

Rules 

Sender and recipient information 

Trash folder 

Undeliverable mail reports 

Migrated to ... / not migrated ... 

Not migrated* 

Discussion databases 

Not migrated 

Not migrated 

Folders and subfolders** 

Message date 

Message priority *** 

Messages and attachments **** 

Not migrated 

Password 

Domino Directory 

Group documents in Personal Address Book + 

Group document in Domino Directory 

Not migrated ++ 


Not migrated 

Sender and recipient information 

Not migrated 

Not migrated 

*Archives are not migrated by the migration tool in the Domino Administrator, but 

after you migrate users, they can run an Upgrade Wizard at their workstations to 

migrate their message archives. 

**For cc:Mail Release 8 clients, the migration converts nested folders and the 

messages they contain. 

***The migration tool preserves the message status in cc:Mail messages marked as 

Urgent (an exclamation mark appears next to the message in the Notes Inbox or 

folder). However, Notes does not assign a special status to migrated cc:Mail 

messages that were marked Low priority. 

****During migration, rich text attributes such as color, font style, font size, 

underlining, boldface, bullets, embedded objects, and doclinks are not preserved. 

+Private mailing lists are automatically sent to users in a Notes message attachment. 

Users then run an Upgrade Wizard at their workstations to migrate these lists to 

their Notes Personal Address Books. The Upgrade Wizard also migrates private 

addresses that cc:Mail Release 2.x and 6.x clients maintain locally in the file 

PRIVDIR.INI. The Upgrade Wizard does not support migrating private addresses 

for cc:Mail Release 8.x clients. 

++All migrated messages are marked unread. 

Chapter 4: Migrating from cc:Mail to Domino R5 using Domino Upgrade Services 51

Notes equivalents for migrated Organizer information 

The following table shows the Notes equivalents for migrated Organizer 

information. 

Organizer record type 

Address 

Alarm 

Anniversary 

Calendar appointment 

Call 

Categories 

Cost Code 

Group Scheduling meeting 

Included section 

Link 

Notepad page 

Preference options 

Planner event 

Repeating entry 

Rooms and resources 

Pending meeting notices*** 

To Do tasks 

User preferences and 

passwords 

Equivalent Notes entry 

Business card in Personal 

Address Book 

Alarm* 

Calendar anniversary 


To Do task 

Category 

— 


— 

— 

Personal Journal 

— 

Calendar event 

Repeating entry** 

— 

— 

To Do tasks 

— 

Comments 

Mailed to user 

Migrates first category 

listed only 

Not migrated 

Not migrated 

Not migrated 

Mailed to user 

Not migrated 

Not migrated 

Not migrated 

Not migrated 

*An alarm is migrated only if the resulting Notes record type also supports alarms. 

**Repeating items migrated to the Notes Calendar use the Notes Release 4.5 repeat 

structure, not the R5.0 repeat structure. Repeating entries migrated to the Notes To 

Do view appear as individual entries and no longer are designated as Repeating or 

include the repeating entry symbol. 

***Meeting invitations are migrated only if a user has responded to them. Users need 

to process any pending meeting notices they want migrated. 


Hardware and software requirements 

The hardware requirements for the machines on which you are planning to 

run the Domino Administrator client and the Notes client are the same as for 

any Windows 95/98 or Windows NT workstation. 

For the machine you are planning to use to perform the actual migration, 

you might consider adding extra memory for performance reasons as well as 

an additional hard disk drive with fast I/O to hold large mail files and get 

better throughput. The Domino migration tools are I/O intensive. 

Keep in mind that in Domino R5, the Notes client is only available for the 

following operating systems: 

• Microsoft Windows 95 or Windows 98 

• Windows NT 

• MacIntosh PowerPC systems. 

We were running the Domino Administrator client on a Netfinity 3000 

system with the following software: 

• Microsoft Windows NT 4.0 with Service Pack 4 

• Lotus Domino server R5.0.1a for Windows NT 

• Lotus Domino Administrator client R5.0.1a for Windows NT 

The Lotus Notes client was running on a Netfinity 3000 with the following 

software: 

• Microsoft Windows NT with Service Pack 4 

• Lotus Notes client R5.0.1a for Windows NT 

Note We recommend that you use a dedicated machine to run the Domino 

Administrator client to perform the migration. This way, the migration 

process will not affect the regular Domino operation nor will it affect mail 

and database servers. 

Preparing to migrate cc:Mail users 

The following tasks need to be completed before the migration process can 

be started: 

• General administrative tasks 

• Notes and Domino preparation tasks 

• cc:Mail preparation tasks 


General administrative tasks 

Perform the following general administrative tasks: 

• Determine the order in which to migrate post offices. This should be 

your migration schedule. 

• Decide which types of cc:Mail data to migrate. Migrating certain types of 

data, such as bulletin boards, may require additional planning and 

preparation. 

• Verify that you have purchased the appropriate Notes client license for 

each cc:Mail user you are migrating. 

• Estimate the amount of disk space required to migrate cc:Mail 

mailboxes. There is no formula for calculating exactly how much disk 

space a mailbox will require after it is converted to a Notes mail file. 

However, you can estimate the size of a converted mailbox by running a 

test migration, and comparing the size of a cc:Mail mailbox with the size 

of the resulting Notes mail file. 

You can use the cc:Mail command MSGMGR to determine the size of 

mailboxes in a post office. For example, to check the size for user Susi 

Switch in our post office ILICPO1 with password PASSWORD in the 

directory M:\CCDATA, we used the following command: 

MSGMGR /N ILICPO1 /P PASSWORD /D M:\CCDATA /U"Susi Switch" 

• Decide how your cc:Mail gateways will map to Domino domains for 

routing mail to external mail systems 

Notes and Domino preparation tasks 

Perform the following Notes/Domino preparation tasks: 

• On your administrative workstation, install the Notes Release 5 Domino 

Administrator client, and the optional cc:Mail Administrative migration 

tool. You must perform a custom installation to install the migration 

tools component. If the administrative client is already installed, just 

rerun the installation and choose custom installation in order to be able 

to select the cc:Mail administrative migration tools. 

• From the administrative workstation, map a drive to the location of the 

cc:Mail post office from which you are migrating users. If the post office 

is inactive, you can also copy all the PO data to a local drive on your 

migration machine. This will improve the migration performance. 


• Back up Domino information. Before you start the migration, we 

recommend that you back up the following Domino data: 

• NAMES.NSF 

• DESKTOP.DSK 

• NOTES.INI 

• *.ID files 

• From the administrative workstation, log in to Notes using a Notes ID 

with “Create New Database” rights on the mail server. You can verify 

these rights by checking the “Security” section in the Server document 

of the Domino server. 

• 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 Editor, Designer, or Manager access rights to the 

Domino Directory on the Registration Server. 

• (Optional) Set registration preferences. 

• (Optional) Create a Notes group to which you can add migrated users. 

• On the administrative workstation, close all applications, except for 

Notes, and close any Notes databases. 

• If you anticipate migrating additional messages for users after 

registration, during the registration process, change the access rights that 

mail file owners have to their mail files from the default level of 

Manager to Designer or Editor. 

cc:Mail preparation tasks 

Perform the following cc:Mail preparation tasks: 

• Clean up the cc:Mail message store. Instruct users to archive or delete 

mail that they no longer need. 

• Prepare the cc:Mail directory for migration. First you should check for 

any inactive accounts (those once created but never used or belonging 

to users who left the company). You can generate a report of cc:Mail 

account usage with the admin program DIRSTAT. Remove any inactive 

accounts from the post office directory to avoid migrating them to 

Domino. We used the following command to get an account usage 

status report for our post office ILICPO1: 

DIRSTAT ILICPO1 PASSWORD M:\CCDATA /DL /LU 


• Check for any names with invalid characters in the cc:Mail directory. 

Notes only supports letters (including National Language Support 

characters), numbers, ampersand, apostrophe, hyphen, period, space 

and underscore for registered user names. A cc:Mail name may contain 

characters that are not valid in Notes. Trying to register cc:Mail users 

with invalid names results in processing errors. 

• Familiarize yourself with how the migration tool parses cc:Mail name 

formats. Certain name formats and characters may not be converted 

correctly during migration. To ensure that all migrated users are created 

with appropriate Notes names, it may be necessary to edit certain names 

either before or after migration. 

Understanding how the migration tool parses cc:Mail name formats 

Unlike Notes names, which are made up of First name, Last name, and 

Middle initial components, the cc:Mail directory stores names as a single 

character string, including commas and spaces. The name format used 

depends on the conventions established within the organization. For 

example, the same user could be listed in the cc:Mail directory as either 

Susan Salani or Salani, Susan. 

In generating a Notes name from an imported cc:Mail name, the migration 

tool first determines the format of the name, and then parses the name into 

Notes name components. The Middle initial field in the Person document 

accommodates a maximum of two characters; longer names are truncated. 

The following table shows how the migration tool generates Notes names 

from common cc:Mail name formats: 

Format of cc:Mail name 

Resulting Notes name component 

Description 

Single name 

Example 

ssalani 

Example 

ssalani 

 

 

First Last 

Susan Salani 

First Last1 Last2 

Craig Van 

Horn 

First1 First2 Last 

Jo Anne 

Lordan 

Components 

Last name 

First name 

Middle initial 

Last name 

First name 


Last name 

First name 


Last name 

First name 


Salani 

Susan 

 

Van Horn 

Craig 

 

Anne Lordan 

Jo 

 

continued 


Description 

First Middle Last 

First Middle initial Last 

First1 First2 Middle 

initial Last 

First Middle initial Last1 

Last2 

Last, First 

Last1 Last2, First 

Last, First Middle 

Last, First Middle initial 

Last1 Last2, First1 First2 


Example 

Cheryl Lynn 

Lordan 

Judy J. 

Kaplan 

Jo Anne B. 

Lordan 

Craig R. 

Van Horn 

Salani, 

Susan 

Van Horn, 

Craig 

Malone, 

Derek Kevin 

Rutherford, 

Robin R. 

Van Horn, 

Jo Ann B. 

Components 

Last name 

First name 


Last name 

First name 


Last name 

First name 


Last name 

First name 


Last name 

First name 


Last name 

First name 


Last name 

First name 


Last name 

First name 


Last name 

First name 


Example 

Lynn Lordan 

Cheryl 

 

Kaplan 

Judy 

J. 

Lordan 

Jo Anne 

B . 

Van Horn 

Craig 

R. 

Salani 

Susan 

 

Van Horn 

Craig 

 

Malone 

Derek 

K. 

Rutherford 

Robin 

R. 

Van Horn 

Jo Ann 

B. 

• Make sure all users being migrated have passwords assigned. If the 

cc:Mail password is blank, null, or zero-length, the migration of the user 

will fail. If you have a cc:Mail user with this type of password, change it 

to a non-blank password in cc:Mail. Also be aware that if a cc:Mail user 

has never logged on or changed his or her password initially, the 

migration tool will fail. 

Tip In cc:Mail, the administrator can also change the password for 

some or all users (batch mode) of a post office by using the cc:Mail 

Import/Export programs. 

Note The cc:Mail migration tool does not support the selection in the 

Migration Options box to “Generate Random Passwords” for users who 

do not have passwords assigned. 


• Take the post office offline to make it inaccessible to users. You could do 

that by changing the directory name or revoking the users’ access rights 

to the existing directory. 

Note Do not shut down the post office. If you shut down the post office, 

the migration tool will fail, because it cannot access it using the Mail 

Engine API (MEAPI). 

• Send any in-transit cc:Mail messages. Post office mail queues are not 

migrated. Clear all Post Office Message Queues and Router Express calls 

with Send Only. 

• Back up the cc:Mail post office being migrated. This backup preserves 

the state the post office was in before you run the maintenance utilities. 

Having a backup lets you safely restore the post office if there are any 

problems during the migration. It is recommended that you back up the 

entire post office directory. 

• Verify the integrity of the post offices you are about to migrate by 

running regular maintenance. See the Lotus cc:Mail Administrator’s Guide 

for more information about using the cc:Mail maintenance tools. 

• (Optional) Delete unnecessary messages in the cc:Mail Message Log, 

Trash, and so forth, using the admin program MSGMGR. After deleting 

messages, run RECLAIM to recover disk space from these deleted 

messages. 

• Create a second backup of the post office that preserves the state the post 

office was in after you ran the maintenance utilities. 

Installing the Domino Administrator client with the migration tools 

This section describes how to install the Domino Administrator client 

including the migration tools for cc:Mail. 

By default, the migration tools are not installed with the Domino 

Administrator; you must select the Migration Tools component during 

installation. If you did not install either the Domino Administrator or the 

migration tools when you first installed the Notes client, run the installation 

again. 

1. From the Domino R5.0.1 CD, select the client subdirectory. 


2. To begin the installation, select Setup. 

The Lotus Notes Installation dialog box appears. 

3. Click Next to continue. 


4. The licencing agreement appears. Please read it. 

5. If you accept the terms and conditions, click Yes. 

6. Enter your Name and Company name into the two fields in the 

following window. 

7. Click Next. 


8. The following screen lets you specify the hard disks and directories 

where you want to install the Lotus program and data files. We decided 

to install them to drive D: into the directories shown in the following 

window (default directories). 



In the next window, you can choose which clients and/or features you 

want to install. 

10. Select Domino Administrator and click on Customize. 


The following window is displayed. 

11. From the list of components to install, check Migration Tools and click 

the Change button. The following window is displayed: 

12. You will see that all of the migration tools are selected by default. Since 

this section of the redbook describes how to migrate cc:Mail users with 

the administrator-based tools, we made sure that cc:Mail Admin 

Migration Tools was selected and all the other ones were unchecked. 


13. To proceed, click Continue. 

The following window shows you the default folder where the 

installation program is going to add the program icons for Lotus Notes. 

14. You can leave the defaults or change the name of the Program Folder. 

Click Next to continue. 


The installation program starts copying files to your computer. The 

copying progress is shown in the following window. 

15. After all the files have been successfully copied to the computer, the 

Lotus Product Registration window appears. 


16. You can fill out the registration form now if you wish, or leave the 

registration by clicking on Exit. We decided to register later and selected 

Exit. The following window appears telling you that you have successfully 

finished the Lotus Notes installation. 

This ends the installation of the Domino Administrator client. 

Migrating users from cc:Mail to Lotus Domino 

This section describes the migration process using the Domino 

Administrator we just installed in the previous section. In our environment 

we are going to migrate users from the ILICHUB cc:Mail post office to the 

MIGSRV1/ILICDOM Lotus Domino server. 

The following steps are necessary to perform the migration: 

• Importing users and groups from a cc:Mail post office directory 

• Migrating Public Mailing Lists (Groups) from cc:Mail to Domino 

• Migrating Organizer Information 

• Registering imported users and completing the cc:Mail migration 


Importing users and groups from a cc:Mail post office directory 

The cc:Mail post office directory contains information for all cc:Mail users 

who have mailboxes in that post office. Notes uses the information extracted 

from the post office directory to configure migrated users for registration. 

To import the cc:Mail post office directory, you must: 

• Connect to the cc:Mail post office 

• Import users and groups 

Connecting to the Domino server 

Follow these steps to select the Domino server to which you want to migrate 

the cc:Mail users. 

1. Start the Domino server you want to use as a migration server. We used 

our Domino server MIGSRV1/ILICDOM. 

2. Start the Lotus Domino Administrator client. 

3. After you enter the Notes Administrator’s password, the following 

screen appears: 

4. When the Domino Administrator client is started for the first time, it 

always connects to the local machine, which might not be a Domino 

server, for example, when an administrator works from a Notes client. 


The name of the server you are currently connected to is shown under 

the administration tabs. The previous picture shows that we are 

connected to the local machine. You can select the server you want to 

connect to by either clicking on the Domain icon in the bookmark bar or 

by choosing File - Open Server as shown in the following picture: 

5. The following window lets you choose or specify the Domino server to 

which you want to first connect and then migrate the cc:Mail users. 

We selected MIGSRV1/ILICDOM as our migration server. 

6. Click OK to continue. 

The Domino administrator will connect to the server specified in the 

previous picture. 


Selecting the Registration Server 

Follow these steps to select the Registration Server for registering cc:Mail 

users as Notes users: 

1. From the main administration window, select the People & Groups tab if 

it is not yet active. The following window is displayed showing the 

currently registered Notes users on server MIGSRV1/ILICDOM. 

2. Click the People button and select Register. The following window 

appears asking you for the certifier password. Since you are going to 

register the cc:Mail users you want to migrate first, you need to have the 

Domino certifier ID and the password available. 

3. Enter the password for your certifier ID and click OK to continue. 


The Register Person — New Entry dialog box is displayed. 

4. Check the name of the Domino server displayed next to the Registration 

Server button. If you want to change the Domino server where you want 

to register your cc:Mail users, click the Registration Server button and 

select the server you want. In our scenario, we used server 

MIGSRV1/ILICDOM as the registration server, as shown in the previous 

picture. 


Selecting the cc:Mail users for migration 

Follow these steps to select the cc:Mail users you want to migrate: 

1. On the Register Person dialog box, click the Migrate people button. The 

following screen appears: 


2. From the People and Groups Migration dialog box, open the Foreign 

directory source list. You will get a list of foreign mail system directories 

as shown in the following window: 

3. Select cc:Mail Users from the Foreign directory source list. The cc:Mail 

Post Office Information dialog box is displayed: 


4. Complete the following information in the cc:Mail Post Office 

Information dialog box as shown in the previous picture: 

• Post Office Name — Enter the name of the cc:Mail post office you 

want to connect to in order to import users from the cc:Mail directory. 

• Post Office Path — The drive letter and directory path that point to 

the cc:Mail post office. The post office can be installed on any 

machine, as long as you have access to it either locally (for example, 

C:\CCDATA) or through a mapped drive (for example, 

M:\CCDATA). In our environment, the post office was installed on 

an NT server box which was not the same as the Domino migration 

server. We mapped the entire drive C: from that server as logical 

drive M: to our migration machine. This way, we had access to all 

post offices which we had installed on that hard disk on the NT server 

box. 

• Post Office Password 

5. Click OK to continue. The post office name, path and password are 

verified and an error message will be displayed if any value is found to 

be incorrect. 

The following screen appears showing the contents of the cc:Mail post 

office directory in the Available people/groups window. 


The initial window will show both cc:Mail users and cc:Mail groups. 

There are two check boxes available above the Available people/groups 

window: 

• Show only groups 

• Show only people 

These two check boxes enable you to display either groups and no users, 

or just all the users and no groups. We are displaying both, groups and 

people, as shown in the previous picture. 

6. You are now ready to select users from the Available users/groups 

window in order to migrate them to Domino. 

Note We will discuss how to migrate groups later in this chapter in the 

section titled “Migrating Public Mailing Lists (Groups) from cc:Mail to 

Domino.” 

7. Select the users you want to migrate and click the Add button. We 

decided to migrate two cc:Mail users at this time, Henry Migrate and 

Susi Switch. The following screen is displayed: 


Specifying conversion settings 

Follow these steps to specify settings relating to the directory upgrade: 

1. Click the Advanced button to open a dialog box that lets you specify 

additional settings for migrating people from cc:Mail. 

The following window appears showing the Conversion Settings: 

These settings apply to all the users you migrate during this session. By 

default, all of the options, except “Convert bulletin boards to Notes 

discussion database” are enabled. The settings are divided into three 

sections: 

Conversion Settings, Gateway Settings, Other Settings. 

There are five directory upgrade settings as described in the following: 

• Mail private mailing lists/R8 address books as Notes attachments: 

Select this option to migrate private mailing lists contained in users’ 

cc:Mail mailboxes. During the migration, each user’s private mailing 

list is converted to a Notes Personal Group and placed within a 

temporary Personal Address Book (PAB). The cc:Mail to Notes 

migration tool automatically mails this PAB to the user. Users can run 

the cc:Mail to Notes upgrade wizard at their workstation to copy 

information from the temporary PAB to the PAB on their workstation. 

Caution Do not select this option if you are migrating cc:Mail Release 

6.3 users. The cc:Mail 6.3 client for Domino cannot correctly process 

migrated private mailing lists and users will be unable to access the mail 

file on the Domino server. 

• Convert Organizer .OR2 scheduling files to Notes: 

Select this option to convert Organizer data (OR2 files) for the selected 

cc:Mail users to Notes Calendaring and Scheduling information. 


Converting Organizer data requires you to connect network drives to 

the directories where the selected cc:Mail users store their Organizer 

data. 

Note We will discuss how to convert Organizer files later in this 

chapter in the section titled “Migrating Organizer information.” 

• Convert alias entries: 

Select this option to retain cc:Mail aliases for migrated users. Aliases 

for entries in the cc:Mail directory are added as entries in the User 

name field of the migrated user’s Notes Person document. 

• Convert bulletin boards to Notes discussion database: 

Select this option to convert bulletin boards in the specified cc:Mail 

post office to a Notes discussion database. All of the bulletin boards in 

a given post office are migrated to a single Notes discussion database 

on the mail server, called cc:Mail Migrated Bulletin Boards 

(CCNOTBB.NSF). Each migrated bulletin board becomes a category 

within the database. 

Important Converting bulletin boards requires a considerable amount 

of time and slows the process of migration. The good news is that 

bulletin boards have to be migrated only once for each post office. If you 

enable bulletin board conversion for multiple users or all users of a 

selected cc:Mail post office, the conversion process is repeated for each 

of the selected users. This way, your migration can take a long time, 

especially if there are many bulletin boards or they are large in size. 

We recommend that you enable this option for one user you migrate so 

that the bulletin boards are converted only once. After that, do not 

enable this option when you migrate the remaining users. 

• Retain cc:Mail MTA routing information for deferred mailbox 

migration: 

You would check this option if the registration and mailbox migration 

of cc:Mail users is not done at the same time. In this case, the Domino 

Upgrade tools will maintain the existing cc:Mail information 

(forwarding address) in the Person document of a migrated cc:Mail 

user until the mailbox migration is completed. 

2. Select the Conversion Settings as appropriate. We selected the settings 

for our scenario as shown in the previous screen. 


Specifying gateway settings 

Follow these steps to specify gateway settings: 

1. Click on Gateway Settings to continue. The following screen appears: 

2. If you have a cc:Mail post office which has a gateway installed routing 

mail to an external mail system, the gateway settings enable you to map 

that gateway to a Domino domain which will be used to route messages 

to the same external mail system. 

In our scenario, we had an SMTP gateway installed in cc:Mail. Our 

Domino domain will have an SMTP MTA installed, so we mapped the 

cc:Mail gateway post office SMTPGATE to the Domino domain 

ILICDOM. 

Note The migration tool will automatically overwrite the names of 

cc:Mail gateways in the sender’s address of a message, and replace them 

with the name of a corresponding Domino domain. This will enable your 

new Notes users to reply correctly to migrated messages originally 

coming from external mail systems into cc:Mail. The reply will be routed 

to the external mail system by way of the Domino gateway you mapped 

in the previous window. 


Specifying other settings 

Follow these steps to specify settings relating to the mailbox upgrade. 

1. Click on Other settings to continue. The following screen appears: 

2. On this screen, you can choose to upgrade to cc:Mail R6.3x Client for 

Domino, select a Post office for routing mail to Notes and set the Error 

Threshold for this migration session. 

The settings we chose for our scenario are shown in the previous figure. 

Note The settings in the previous figure are quite important, so we are 

going to explain them a little further. There are three settings available: 

• Upgrading to cc:Mail R6.3x Client for Domino: 

Select this option to automatically configure internal cc:Mail 

information that lets users access mail files on a Domino server with 

the cc:Mail Release 6.3x client. 

This process will add/modify two files in the CCDATA directory: 

NOTES.USR and CCNOTES.CFG. 

Do not select this option when importing users who are currently 

running a version of cc:Mail other than Release 6.3x, or who will use 

the Notes mail client after migration. To migrate users to the cc:Mail 

Release 6.3x client, the mail template R63MAIL.NTF must be 

available in the data directory of the users’ mail servers. This template 

is available on the Domino R5 server. 

When preparing to register Release 6.3x users, select R63MAIL.NTF 

as the mail template. If you do not provide the correct mail template 

for Release 6.3x users, they cannot access their mail files (other mail 

templates might work correctly, but are not supported using this 

client). 


• Post office for routing mail to Notes: 

In networks where the cc:Mail MTA connects cc:Mail and Notes, you 

can configure the migration tool to enable automatic forwarding from 

a cc:Mail post office to Notes. Having messages automatically 

forwarded eliminates the need to migrate additional messages later. 

When you specify the post office for routing mail to Notes, the cc:Mail 

post office directory retains an entry for each migrated user. 

However, the migration tool updates information in a user’s cc:Mail 

directory listing, as follows: 

• Changes the location code to lowercase “r“ to indicate that the user 

is now remote to this post office 

• Adds the name of the Notes mail domain where mail will be 

forwarded to the address field 

After the migration tool changes a user’s location information, they 

can no longer use a cc:Mail client to retrieve messages from their 

cc:Mail mailbox. 

• Error Threshold 

You can specify the number of errors to tolerate when migrating 

messages from mailboxes in the cc:Mail post office to Notes mail files. 

By default, the migration tool tolerates an unlimited number of errors, 

and completes the migration regardless of the error count. 


3. Click on Done to return to the People and Groups Migration window. 

Specifying migration options 

Now we are going to set the migration options. These options determine 

how the migration tool creates a user in Notes from information imported 

from cc:Mail. In our scenario, we selected Allow addition of empty groups to 

Notes, Convert mail and Add administrator to mail file access control list as 

shown in the previous picture. 

There are seven migration options as described in the following: 

• Generate random passwords for users with no passwords: 

The Domino migration tool for cc:Mail does not support the option 

“Generate random passwords.” To successfully migrate a user’s cc:Mail 

mailbox, you must provide a cc:Mail password for the user. Use the 

cc:Mail administration tool to create passwords for users before 

migration 

Tip Make sure that every user has logged on to his or her cc:Mail 

account at least once — if you try to migrate a mailbox which is new and 

nobody has ever logged on to it, the process will fail with a message 

“You must provide a password for this user.” 


• Overwrite existing passwords with random passwords: 

Not supported for cc:Mail — leave unchecked. 

• Add cc:Mail name to Notes Person document (required for cc:Mail 

MTA): 

The User name field of a Person document in Notes lists one or more full 

names. The first name in this field is the primary Notes name. In 

addition to this primary name, the User name field can contain 

secondary entries, which serve as aliases for the user and can be used in 

addressing mail. The migration tool imports the cc:Mail user name for 

use as secondary Notes name. 

• Allow addition of empty groups to Notes: 

Groups selected for import are considered empty if they do not contain 

any members who can be registered in Notes. By default, the migration 

tool does not import empty groups. Check this option if you want the 

migration tool to import empty groups — you might want to add users 

into the empty groups after the migration. 

• Add administrator to mail file access control list: 

During the migration process, the administrator ID you are using is 

temporarily added to the ACL of each mail file with Manager access. 

After you successfully migrated users, this administrator name is 

removed from the ACLs of the mail files and is replaced with the name 

of the mail file owner. As a result, you cannot open the user’s mail file 

after the initial migration. You are also not able to migrate additional 

mail to it. 

When the “Add administrator to mail file access control list” option is 

selected, the administrator name will not be removed from the user’s 

mail files after the migration process is completed. 

Caution Make sure you don’t forget to remove the administrator name 

from the user’s mail files after you are done with the migration. New 

Notes users might not like the idea to have some administrator’s name in 

their mail file ACL, having Manager access! 

• Convert mail: 

Domino Upgrade Services provides you with the option to convert 

existing cc:Mail mail files into Notes mail files. By default, this option is 

enabled. If you choose to convert mail, during the registration process, 

the migration tool automatically converts cc:Mail mail files to Notes mail 

files. 

If you disable the option Convert mail, the migration tool will only 

register your cc:Mail users in Notes and create their mail files. No mail 

will be migrated from cc:Mail to Notes. 


• Convert mail ONLY (Notes user and mail file must already exist): 

The Domino migration tool for cc:Mail provides you with the option to 

convert mail only. Select this option if you want to migrate cc:Mail users 

who are already registered in Notes, or if you want to migrate additional 

mail file contents for users you have migrated before. By default, this 

option is not selected. 

Importing the selected cc:Mail users 

Now that all the Advanced options and Migration settings have been set, we 

are ready to import our selected users into the registration queue. 

1. On the People and Groups Migration window, click the Migrate button 

to start the import process. The following window appears, showing that 

the two users we had selected for migration were successfully queued 

for Registration. 

2. Click OK to close the window and to continue. 


3. Click Done to close the People and Groups Migration window. The 

following screen appears: 

4. Since we have checked the Advanced button shown in the top left corner 

of the Register Person window, all the Register Options Icons (Basics, 

Mail, ID Info, Groups and Other) are displayed. From this window, you 

are able to make any changes you want in the Basics, Mail, ID Info, 

Groups and Other settings groups. 

Note We are not going to discuss the Notes registration settings in 

detail here, since they are exactly the same as when you are setting up 

new users in Notes. For more information about setting up users in 

Notes, refer to the yellow book Administering the Domino System. 

Keep in mind that the Registration server and/or the mail server can be 

any Domino server in your organization. These servers can be running 

on any platform supported by Lotus Domino. 

5. You are now ready to register users in the Registration queue with 

Status “Ready for registration” and migrate their mail files from cc:Mail 

to Domino. If you get any error messages in the Registration Status field, 

check the Notes log for possible errors and correct them first before 

attempting to migrate the users. 


Tip Users remain in the Registration queue until registered or specifically 

removed. You can save users in the queue for later registration. All 

the settings are preserved. 

Before we register the users, let us first look at how you migrate public 

mailing lists. 

Migrating Public Mailing Lists (Groups) from cc:Mail to Domino 

Important The term “Group” is not known in the cc:Mail system. The 

equivalent for a group is a public mailing list in cc:Mail. So whenever we use 

the term “Group” in this redbook, we are actually talking about a cc:Mail 

public mailing list. You will also find the term “Groups” being used in the 

user interface of the cc:Mail Migration tools — just substitute it with public 

mailing lists. 

With the Domino migration tool, you can migrate cc:Mail public mailing lists 

and their members from cc:Mail to Domino. The migration tool supports the 

migration of Local users, which are members of a public mailing list in that 

same directory. When you select a public mailing list (Group) for migration, 

the Local users in this list are always selected for migration, too. 

The migration tool will search the Domino Directory to determine whether 

the name of any selected group duplicates the name of an existing Notes 

group. If the group name you selected for migration appears to be unique, 

the migration tool will create a Notes group according to the settings chosen 

in the Group Migration Options window. If the migration tool finds that the 

group name selected already exists in the Domino Directory, the Existing 

Group Migration Options window will appear, allowing you to specify how 

to process the duplicate group. 

The following guides you through the additional steps neccessary when you 

have groups in your cc:Mail directory and you decide to use them for the 

migration process. 


1. Go to the section titled “Importing users and groups from a cc:Mail post 

office directory” earlier in this chapter and perform the steps from the 

beginning of that section through step 5 in the section titled “Selecting 

cc:Mail users for migration.” You should see the People and Groups 

dialog box, as shown in the following picture: 


2. Click on Show only groups. The following screen appears, showing 

cc:Mail groups only in the Available people/groups window: 


3. Select the group(s) you would like to migrate and click Add to continue 

(you can also click Add All to select all groups for migration). In our 

scenario, we selected the group Development. The Group Migration 

Options window appears, as shown in the following picture: 

4. The Group Migration Options dialog box lets you specify how the 

migration tool handles groups and its members. Let’s describe those 

options in more detail: 

• The first check box determines if you are going to create a new Notes 

group or if you want to migrate the users in the public mailing list to 

an existing Notes group. Since there was no existing “Development” 

group in the Domino Directory in our scenario, the Group Migration 

Options dialog box displayed the option “Create a new Notes group 

with the following settings.” 

• The name of the cc:Mail public mailing list we selected was put into 

the “Notes Group Name” field by default. 

• The “Group type” field lets you specify what type of Notes group will 

be created. The following four types of Notes groups can be selected: 

Mail only; Access Control List; Multi-purpose; Deny list only. 

By default, the migration tool creates Multi-purpose groups. This field 

cannot be changed if the group is an existing Notes group. For 

information about these different kind of groups, refer to the yellow 

book Administering the Domino System. 

The field “Description” displays an optional description of the 

imported public mailing list, which the migration tool adds to the 

Description field of the Notes group document it creates. 


• The option “Add nested groups contained in this group and their 

members” enables the migration tool to migrate users contained in a 

group, or a number of groups, within a group which was selected for 

migration. 

Important At the time this redbook was written, we found no method of 

creating a nested group (public mailing list) within the cc:Mail Directory. 

There is a feature called Bankshot Routing available in cc:Mail, which 

implies some sort of public mailing lists within public mailing lists. We 

discussed scenarios using Bankshot Routing, but we came to the 

conclusion that using this method has no impact on migration at all. 

• The last option, “Use above settings for all currently selected or 

nested groups (don’t prompt again),” lets you specify if you want to 

use the same settings for each group you selected for migration. 

Caution We recommend that you don’t use this option when you are 

planning to migrate public mailing lists to a combination of existing and 

new Notes groups. After you set this option, the migration tool does not 

display the Group Migration Options window again as it continues 

processing groups. This way, you cannot specify how to create or add 

members to those groups. 

As a result, the migration tool will create any new Notes group using 

their original cc:Mail mailing list name, which may lead to the creation 

of duplicate Notes groups. 



6. The People and Groups Migration window is displayed, as shown 

in the previous picture. Note that our cc:Mail public mailing list 

“Development” as well as the two local cc:Mail users (Henry and Susi) 

within that group have been added to the People/Groups to migrate 

window. 

Tip When the cc:Mail public mailing list you select for migration 

contains local cc:Mail users that are already in the People/Groups to 

migrate window, these users will not be added again. These existing 

users could be coming from other public mailing lists added previously, 

or they were added as single users. Adding the public mailing list 

“Development” in our scenario only added a group “Development” to 

the People/Groups to migrate list, while our two users were not added 

again, since they were already there. 


This concludes explaining the steps neccessary to add cc:Mail Public Mailing 

Lists to the People/Groups to migrate window. 

Go to step 7 in the section called “Selecting cc:Mail users for migration” 

earlier in this chapter to continue the migration process. 

Migrating Organizer information 

Before we continue registering the users, let us have a look at how Lotus 

Organizer data are converted into Notes data using Domino Upgrade 

Services. When migrating mailboxes for cc:Mail users, you have the option to 

also convert their Lotus Organizer 2.x Group Scheduling information (OR2 

files) into Notes data. 

Organizer information is migrated to locations in the Notes mail file, 

Personal Journal database, and Personal Address Book. Some Organizer data 

is not migrated; the migration tool only reproduces the Organizer views and 

documents that have appropriate equivalents in Notes. 

The cc:Mail to Notes migration tool migrates data from Organizer 2.x for 

cc:Mail for Windows only; it does not migrate data for stand-alone OR2 files, 

Notes Calendaring and Scheduling versions of OR2 files, or the Organizer 

PIM version (all other .ORx files). 

An end-user migration tool for moving Organizer OR2 stand-alone and 

Organizer PIM data to Notes is available as an optional installation 

component of the Notes Release 5 client. 

Changes made to the user’s cc:Mail directory entry 

After you migrate a cc:Mail user’s Organizer information, the cc:Mail to 

Notes migration tool modifies Organizer information in the Comments field 

of the user’s cc:Mail directory entry. The tool will change the following 

information: 

• The 02 keyword, which identifies the Organizer Calendar Path, to 92 

• The 04 keyword, which identifies the Organizer Agent Name, to 94 

These changes enable you to perform subsequent migrations to convert a 

user’s remaining Organizer information, while preventing other Organizer 

users from viewing migrated users’ free-time schedules or sending 

scheduling messages to these users’ Organizer Agents. The migration tool 

interprets the modified Comments information and correctly migrates 

additional Organizer data. The following picture shows you a snapshot of 

our cc:Mail directory. Note the comment field in Henry Migrate’s entry. It 

shows that his Organizer files were converted to Notes data and that the 02 

and 04 keywords have been changed to 92 and 94, respectively. 


Preparing to migrate Organizer information 

Before you start to migrate Organizer data for the cc:Mail users being moved 

to Notes, perform the following tasks first: 

• Map network drives to directories where users’ Organizer data (.OR2 

files) are stored from the workstation performing the migration. 

• Disconnect Organizer users from the directory where the Organizer data 

files (*.OR2) reside. 

• Verify that you have full access rights to the file server directories 

containing the OR2 files and at least Read access to Organizer OR2 files 

to be migrated. 

• Verify that you have Editor or higher access to the Notes mail files that 

will contain the migrated Organizer information. 

• Turn off all Organizer scheduling agents. 

• Verify that you have sufficient disk space to migrate the Organizer 

information. There must be 2MB of free disk space on the target Domino 

server for each 1MB of OR2 file you migrate. 

• Instruct Organizer users to perform the following preparation tasks that 

will assist in a faster migration: 

• Record the names of any included section, because included sections 

are not migrated. By knowing the names of any included sections, 

users can create links between the migrated documents in Notes. 

• Process pending meeting notices, because the migration tool does not 

migrate meeting invitations that have not been acted upon. 


• Delete data that do not need to be migrated. 

• Archive and compact data to be migrated to reduce the size of the 

OR2 files. 

• Compact Organizer data files to be migrated, using the Organizer 

administration program. Refer to the Organizer 2.x Administrator’s Guide 

for information about how to compact files. 

Performing the Organizer migration 

The following guides you through the additional steps neccessary when you 

have cc:Mail users who are using the Lotus Organizer GS and you decide to 

convert their OR2 files into Notes data. 

1. Go to “Importing users and groups from a cc:Mail post office directory” 

earlier in this chapter and perform the steps from the beginning of that 

section through step 1 in the section titled “Specifying conversion 

settings.” You should see the Conversion Settings dialog box, as shown 

in the following picture: 

2. Select “Convert Organizer .OR2 scheduling files to Notes.” We checked 

this function in addition to the ones we had selected in step 2 in the 

“Specifying conversion settings” section as shown in the previous 

picture. 

3. Finish the “Gateway Settings” and the “Other Settings” according to 

your environment, as described in sections “Specifying gateway 

settings” and “Specifying other settings” earlier in this chapter. 


4. Click Done. You will be returned to the People and Groups Migration 

dialog box, as shown in the following picture: 

5. You will notice that there is only one user in the People/Groups to 

migrate box this time. We selected Henry Migrate for this migration 

session, as he was one of the Lotus Organizer users in our scenario. 

6. Click Migrate to continue. You will be presented with an information 

window, as shown in the following picture: 

7. This window appeared because we selected the “Convert Organizer 

.OR2 scheduling files to Notes” function, and this text reminds you that 

you need access to the OR2 files from your workstation. 

Organizer OR2 files are typically stored separately from a user’s cc:Mail 

mailbox. To enable the migration tool to correctly locate the OR2 files 

and migrate Organizer information, you need to map drives on the 

administrative workstation to the Organizer data directories. 


Note Although the migration tool can only migrate OR2 files for 

Windows versions of Organizer for cc:Mail, OR2 files can be migrated 

from any location that the administrative workstation is connected to, 

regardless of the operating system. 

8. Click Yes to continue. The following window appears, indicating that the 

people you had selected for migration were successfully queued for 

registration. 

9. Click OK to close the message window, then click Done. 

10. You have now completed the additional steps necessary for Domino 

Upgrade Services to convert Lotus Organizer OR2 files into Notes data. 

Go to the following section to continue the migration process. 

Registering imported users and completing the cc:Mail migration 

After you successfully imported users into the registration queue, you are 

ready to register them and complete the migration. Depending on the 

options you select, the registration process: 

• Creates a Notes Person document and Notes ID file for each 

migrated user 

• Creates a Notes mail file 

• Migrates messages and other data from the cc:Mail mailbox 

• Converts Lotus Organizer OR2 files into Lotus Notes data 


Let’s get started with the registration process for the users listed in the 

Registration queue. You should still see the Register Person dialog box as 

shown in the following picture: 

1. Check the registration information for each name that appears in the 

Registration queue and make sure that it is correct. If required, you can 

still change the registration settings for individual users or for all users 

in the queue by changing the registration defaults. 


2. Click on Options. The Advanced Person Registration Options window 

appears as shown in the following picture: 

3. This window allows you to set advanced options, which will apply 

during this migration process. These options determine how Notes 

processes information when registering users. In our scenario, we did 

not select any of the advanced options, as shown in the previous picture. 

Note There are six Advanced Person Registration Options available as 

described in the following table: 

Option 

Do not continue on 

registration errors 

Keep successfully 

registered people in 

the queue 

Try to register queued 

people with error 

status 

Allow registration of 

previously registered 

people 

Don’t prompt for a 

duplicate person 

96 Moving from cc:Mail to Lotus Domino R5 

Purpose 

Stops registration if you have multiple users selected 

and the registration encounters an error. The default is 

to continue on registration errors. 

Keeps successfully registered users in the queue. The 

default is to remove successfully registered users from 

the queue. 

Tries to register queued users, even if their registration 

status contains errors. For example, if you choose this 

option, a user whose password is insufficiently 

complex will be registered. The default is not to 

register queued users who show an error status. 

Allows registration of users who were previously 

registered in Notes. The default is not to register 

previously registered Notes users. 

Takes one of these actions: 

1. Skips the user registration for both short name and 

full name single matches. 

2. Overwrites the existing user if the single match 

found is on the full name. Short name uniqueness is 

then required. 

The default is to prompt for duplicate users. 

continued

Option 

Don’t prompt for a 

duplicate mail file 

Purpose 

Takes one of these actions: 

1. Skips the user registration. 

2. Generates a unique mail file name by appending a 

number beginning with 1, then 2, etc., to a non-unique 

mail file name until a unique name is found. 

3. Replaces the existing mail file - option does not 

apply when the mail file is being created in the 

background via the Administration Process, or if the 

current ID does not have delete access to the mail file 

being replaced. 

The default is to prompt for a duplicate mail file. 

4. Select the Advanced Person Registration Option you want to apply for 

this registration and click OK to continue. You will get back to the 

Register Person window as shown in the following figure: 


5. You can register and migrate users individually by selecting them and 

clicking Register. To register and migrate all the users in the Registration 

queue, just click Register All. We selected Register All, because we only 

had two users to migrate in our Registration queue. 

The migration tool will register the two cc:Mail users with Domino and 

migrate all the messages from their cc:Mail mailboxes to Domino mail 

files. 

Important One additional step will be neccessary when you have users 

with Organizer files in the registration queue and you selected to convert 

these files to Notes. 

Notes requires you to authenticate a process before it runs. Since the 

Organizer migration is a separate process, before you can complete an 

Organizer migration and register users, you must supply a Notes 

password as shown in the next picture. 

The migration tool prompts you for the password when it is ready to 

register the first cc:Mail user for whom you selected the option “Convert 

Organizer .OR2 scheduling files to Notes.” 

Enter the password for the administrator ID you are using for the 

migration and click OK. The migration process will continue. 

You are prompted for the password only once during the session. 

The following window appears showing that the migration was 

successful: 

6. Click OK to close the message window. 

7. Now you will see the Register Person - New Entry window with empty 

fields. You will also notice that the two users from the Registration 

queue window are gone. Click the Done button to close the window. 


Checking the logs and verifying that the migration was successful 

After a migration completes, perform the following tasks to verify that the 

migration was successful: 

• Search the Miscellaneous Events view of the Notes log for migration 

messages and possible errors that occurred during the registration 

and the migration process. 

• Check the contents of the Domino directory and the Notes mail files. 

• Verify that bulletin boards have been migrated properly. 

• Test the access to mail and mail transfer for migrated users. 

After you determine that the migration was successful, you are ready to 

prepare end users to migrate locally-stored messaging data and other 

cc:Mail data that DUS did not process, using the Upgrade Wizard. 

Checking the Notes log file 

Let’s open our Notes log file and have a look at the Miscellaneous Events 

view. 

1. Start the Domino Administrator client and select Files - Notes Log - 

Miscellaneous Events. The following picture shows our log file after we 

successfully migrated two cc:Mail users to Domino: 


Important Make sure that you open the Notes log file in your \NOTES\DATA 

directory on the workstation on which you are performing the migration (File - 

Open Server - Local). This is the log file where you can find the migration 

messages. Don’t look at the Domino log file in \DOMINO\DATA — it does 

not contain any migration-related messages. 

Looking at the Domino Directory 

Next, let’s have a look at the Domino Directory to find out how our migrated 

cc:Mail users got registered. The following window shows the People view 

from our Domino Directory on server MIGSRV1/ILICDOM: 

You can see that both users we migrated from cc:Mail were added to the 

Domino Directory on our server MIGSRV1/ILICDOM. 


The Domino migration tool has also changed the location code in the cc:Mail 

directory for the two users it migrated to Domino as shown in the following 

picture: 

You can see that the location code has changed from “L” to “r,” indicating 

that these two users are no longer local to this post office. Any mail sent to 

their cc:Mail address will be automatically forwarded by the Domino cc:Mail 

MTA to the address in the “Address” field. 

Tip Be aware that the location code of those users you migrated changed to 

“r” in the cc:Mail directory. Therefore, they can no longer log on to this post 

office as local users. 

All the messages of migrated cc:Mail users are still in their cc:Mail mail file. 

If you change their location code from “r” to “L,” those users can still look at 

their cc:Mail messages. But remember that you will need to change the 

location code back to “r” for those users, so that their mail will be forwarded 

to Domino. 


Since we had chosen to also migrate groups (which are actually public 

mailing lists in cc:Mail), let’s see how they got migrated to Domino. From the 

Domino Directory, open the Groups view. The following window appears: 

As you can see in the previous picture, the Domino migration tool has 

created a group entry in the Domino Directory called “Development.” This 

entry was migrated from the public mailing list “Development” in the 

cc:Mail directory (for reference, have a look at the picture showing the 

cc:Mail directory earlier in this section). 


The members of the public mailing list in cc:Mail are also migrated and put 

into the group “Development,” as shown in the following picture: 

Checking the migrated Notes mail files 

Now that you have made sure that your users have been successfully 

registered in Domino and that their mail files have been migrated, check the 

contents of the Domino mail file for at least one of the newly migrated Notes 

users. 


The following window shows a snapshot of Susi Switch’s Notes mailbox, 

who is one of the two users we migrated: 

Tip Remember that you can only open a user’s mail file when your 

administrator name is in the Access Control List (ACL) with proper rights. 

We achieved that by selecting “Add administrator to mail file access control 

list” in the Migration Options. See the section titled “Specifying migration 

options” earlier in this chapter. Remember to remove your administrator 

name from the users’ mail files before they start using their Notes clients and 

access their Notes mail. 

When you check the contents of Susi Switch’s mail file shown in the previous 

picture, you can see that the Domino migration tools have migrated the 

following from the cc:Mail mailbox: 

• Messages and attachments in migrated folders (all migrated messages 

are set to a status of unread) 

• Return receipts 

• Folders and subfolders (also known as nested folders) 

You can also see the memo titled “cc:Mail Migrated Private Mailing List is 

attached” at the bottom of the list. This memo was sent by the migration 

tools and has the user’s temporary Personal Address Book attached. 


For reference, let’s have a look at a snapshot of Susi Switch’s mailbox in 

cc:Mail just before we migrated it to Domino: 

Verifying that bulletin boards have been migrated properly 

One of the Advanced Settings for migrating cc:Mail post offices is to convert 

cc:Mail bulletin boards. All of the bulletin boards in a selected cc:Mail post 

office are then converted to a single Notes discussion database on the 

Domino server. 

The database created has the title “cc:Mail Migrated Bulletin Boards” and 

has the filename CCNOTBB.NSF. Each migrated bulletin board becomes a 

category within this database. 


Since we decided to convert bulletin boards from the cc:Mail post office in 

our test scenario, let’s now have a look at that discussion database. 

1. Start the Domino Administrator client. 

2. Open the server you used for migration, then click on the Files tab. The 

following window appears: 

3. From the list of files, double-click on the database “cc:Mail Migrated 

Bulletin Boards” (last one on the list in the previous window) to open the 

discussion database. It should contain one category for each bulletin 

board you migrated from your cc:Mail post office. 


The following window shows the discussion database which was created 

from the two bulletin boards we migrated from cc:Mail in our scenario, 

sorted by Category: 

Checking the converted Organizer files 

One of the cc:Mail Advanced Upgrade settings was “Convert Organizer 

.OR2 scheduling files to Notes.” Since we checked that option and therefore 

migrated the contents of Henry Migrate’s Organizer file (OR2), let us now 

have a look at the results. 

Organizer meeting information 

Scheduled meetings in a user’s calendar section are converted to personal 

appointments in the user’s Notes calendar. Status information, and 

information about the meeting chair and attendees are migrated to the 

Detailed description field of the Appointment document. 

The information migrated to this field depends on whether the user is the 

meeting chair or a meeting attendee. For a meeting chair, the complete list of 

attendees is migrated. For an attendee, the description contains the name of 

the Chair only; the list of other attendees is not migrated. Other meeting 

information is not migrated. 


The following picture shows a snapshot of a weekly view in Henry Migrate’s 

Organizer: 

And here is the result in Henry’s Notes calendar: 


Organizer calls 

Entries in the Organizer Calls sections are migrated to tasks in the Notes 

Personal To Do view. The cc:Mail to Notes migration tool preserves the 

major data items of a call, placing them in equivalent fields of the task entry, 

or in the Details field. Call fields that do not have appropriate equivalents in 

Notes may not be migrated. 

We have put one entry into the Calls section in Henry’s Organizer as shown 

in the following picture: 

Calls are migrated into tasks in the Notes Personal To Do view. The 

following picture shows how Henry’s Organizer call looks in his Notes 

Personal To Do view: 


To Do section 

All the entries in a To Do section in Organizer are converted into a Notes To 

Do list. If the user has more than one To Do section in his Organizer, the 

migration tool combines them into a single Notes To Do list. 

Here is an entry from Henry’s To Do section in his Organizer: 

And the next picture shows that entry in his Notes To Do list: 


Organizer Address and Notepad sections 

Organizer Address and Notepad sections are migrated to the Personal 

Address Book (PAB) and Personal Journal databases, respectively, on a 

user’s Notes workstation. Multiple Address sections are migrated to a single 

PAB. Similarly, multiple Notepad sections are migrated to a single Personal 

Journal. 

The administrative workstation running the migration tool cannot write 

directly to a user’s Notes client. To provide users with the information 

migrated from Organizer, the migration tool places a message in the Notes 

Inbox, to which the Personal Address Book and Personal Journal containing 

the migrated Organizer information are attached. The message explains that 

the migrated Organizer information is attached and provides instructions for 

detaching the files, and adding the information to the existing Personal 

Address Book and Personal Journal databases. 

The following picture shows Henry Migrate’s Notes Inbox. Notice the two 

entries at the bottom; these two messages were sent by the Upgrade Services. 

The first message has a PAB with the Organizer Address section attached 

(file name OR2ADDR.NSF), the second one has a Personal Journal database 

with the Organizer Notepad section attached (file name NOTEPADS.NSF). 


The following window shows the contents of the Organizer Address section 

message: 

This snapshot shows the contents of the Organizer Notepad section message: 

As described in both messages, we detached the two PABs from the 

messages in Henry’s Notes Inbox and saved them in his Notes data directory 

(C:\LOTUS\NOTES\DATA). 


We then opened the PAB with the OR2 Addresses, and added all the 

information to Henry Migrate’s own Personal Address Book. The following 

picture shows a snapshot of the Contacts view in Henry’s PAB: 

The following picture shows how this entry looks in the Address section of 

the Organizer: 


In the next step, we opened the Personal Journal database with the OR2 

Notepads, and added all the information to Henry Migrate’s own Personal 

Journal database. The following picture shows a snapshot of the Contacts 

view in Henry’s PAB: 

The following picture shows how this entry looks in the Notepad section of 

the Organizer: 

This concludes the verification of the converted Organizer data. 


Migrating private mailing lists 

When you migrate a user’s mailbox and you choose to also migrate the 

user’s private mailing list, the migration tool will convert the cc:Mail private 

mailing list and place it into a temporary Personal Address Book (PAB). 

The Domino migration tool will automatically mail this PAB to the user as 

an attachment. 

Users can then run the cc:Mail to Notes Upgrade Wizard at their workstation 

to copy the data from the temporary PAB to the PAB on their workstation. 

This process is explained in detail in the chapter titled “Migrating personal 

cc:Mail data using the Upgrade Wizard” later in this book. 

Testing mail access and mail transfer for the migrated users 

As a final test, make sure that the users you migrated are able to access the 

Domino server, the Domino Directory and their corresponding mail files. 

The best way to do that is to install a Notes client and set it up with the ID 

file of one of the migrated users. After you have set up the client, make sure 

that all the Notes client functions are working without any problems. 

It is also advisable to send some mail to that new user and check if it is 

routed properly and finally ends up in that user’s mailbox. 

This completes the process of migrating from cc:Mail to Lotus Domino R5 

using Domino Upgrade Services. 

Summary 

In this chapter, we first gave an overview of the Domino Upgrade Services 

(DUS) to get an understanding of the functionality these services provide. 

Then we listed the supported cc:Mail versions and pointed out what is 

migrated from cc:Mail to Domino, and which data are not migrated. 

Next, we explained the preparatory steps that need to be done to get the 

cc:Mail users ready for migration. This includes general administrative tasks, 

Notes and Domino preparation tasks as well as cc:Mail preparation tasks. 

Then we showed you how to install the Domino Administrator client with 

the migration tools. 

Following that, we documented how to migrate users from cc:Mail to Lotus 

Domino using the Domino Upgrade Services. We also covered how to 

migrate cc:Mail public mailing lists as well as Lotus Domino Organizer files. 

Finally, we checked the Notes log files and the migrated data to make sure 

that the migration was successful. 



Chapter 5 

Migrating personal cc:Mail data using the Upgrade Wizard 

In this chapter, we are going to discuss another one of the migration tools 

provided in Lotus Domino R5. We will cover the end-user based Upgrade 

Wizard for cc:Mail. 

After you have successfully completed migrating your users from cc:Mail to 

Lotus Domino and have moved the contents of their mailboxes to a Domino 

mail server, users can then complete the migration by converting their 

personal mail data to Lotus Notes. 

Users migrate personal mail data, such as private addresses, mailing lists, 

and message archives, by running an Upgrade Wizard. They launch the 

wizard from an upgrade message in the Inbox of their Notes mail file. 

The administrator needs to send this upgrade message to the end user from 

within the Domino Administrator program. 

The Upgrade Wizard can be installed as part of each user’s Notes client or in 

a shared network directory. 

The following topics are covered in this chapter: 

• What is migrated by the Upgrade Wizard for cc:Mail 

• Installing the Notes client and the Upgrade Wizard 

• Setting up the Notes client 

• Sending users an upgrade notification message 

• Running the Upgrade Wizard 

• Checking if the migration was successful 

What is migrated by the Upgrade Wizard 

The Upgrade Wizard allows users to migrate their personal mail data from 

any local or mapped drive location. The Upgrade Wizard converts archived 

messages from cc:Mail into messages in a Notes mail file archive. Private 

addresses and private mailing lists are migrated into a Notes Personal 

Address Book (NAMES.NSF) on the user’s workstation. 

117

The following table shows how personal information from cc:Mail is 

converted to Notes information: 

Mail data from cc:Mail 

Archives (.CCA files) 

Attachments 

Message priorities 

Messages 

— 

Mobile post offices** 

Private mailing lists 

Private addresses 

Read/unread marks*** 


Trash folder 

Converts to these Notes equivalents 

Folder in mail file archive database 

Attachments 

Message priorities 

Messages* 

Hierarchical folder views 

Not migrated 

Group document in PAB 

Contact in PAB 

Read/unread status 


Not migrated 

*Rich-text formatting is not preserved in messages migrated from cc:Mail. 

International characters in the message body are successfully converted during 

migration. 

**The Upgrade Wizard can only migrate the archived messages of a cc:Mail mobile 

user. Users cannot migrate the contents of an entire mailbox from a mobile cc:Mail 

post office on their workstation. Mobile cc:Mail users who want to migrate messages 

must archive the messages in cc:Mail before running the Upgrade Wizard. 

***cc:Mail archives can contain only messages that have been read, and therefore the 

Upgrade Wizard assigns the status of Read to all migrated archived messages. 

Installing the Notes client and the Upgrade Wizard 

This section describes how to install the Lotus Notes client including the 

Upgrade Wizard for cc:Mail. The Upgrade Wizard runs on a workstation 

with Windows 9x or Windows NT 4.0. 

You need to install a Notes R5.x client on that workstation. The wizard will 

migrate data from any cc:Mail client, R2.x, R6.x and R8.x. 

You can install the wizard program files either in a shared network location 

or locally, as part of the Notes client installation. We chose to install the 

Upgrade Wizard locally in our scenario. 

The Upgrade Wizard is not installed by default with the Lotus Notes client. 

You must select the Upgrade Wizard component during the installation. If 

you did not select the cc:Mail Upgrade Wizard when you first installed the 

Notes client, you will need to run the installation again. 


1. From the Domino R5.0.1a CD, select the client subdirectory. 

2. Double-click on Setup to start the installation. The Lotus Notes 

Installation window appears. 

Chapter 5: Migrating personal cc:Mail data using the Upgrade Wizard 119

3. Click Next to continue. You are presented with the Licensing Agreement 

form, as shown in the following picture: 

4. Read the Licensing information, and if you agree with it, click Yes to 

continue. 

5. The next window asks for your name and your company’s name. 

6. Enter the information according to your environment. For our 

installation, we entered Susi Switch and IBM in the two fields. 


7. Click Next to continue with the installation. You are prompted to select 

the installation directories. 

8. Accept the default directories or change them to the ones where you 

want the Notes client installed. We left the defaults to install Notes to the 

c: drive. 

9. Click Next. The following screen is displayed. 


10. You can select which Lotus Notes client you want to install. Click the 

Notes Client button, then click on Customize. 

Important Don’t forget to click the Customize button. If you miss this 

step, you will not be able to select any migration components for 

installation, and the Upgrade Wizard will not be installed by default. 

11. The Components selection window displays, as shown in the following 

picture: 

12. Check the Migration Tools box in the Components window. 

13. Click Change in order to select the specific migration tool you want to 

install. The Select Sub-components window appears: 


14. By default, all the migration tools are checked. Make sure you uncheck 

those tools you don’t need, and leave the tool you need checked. For our 

scenario, we deselected all tools except the cc:Mail Client Migration 

Tools as shown in the previous picture. 

15. Click Continue to close the Select Sub-Components window. 

16. Click Next. The Program Folders window is displayed. 

17. You can choose a program folder where you want the installation 

program to copy the Notes program icons. We left the defaults for our 

installation. 


19. You are presented with a window showing you the progress of the files 

being copied to your workstation: 


20. When all the program files are installed, you are prompted with a 

registration window. Register your copy of the program or cancel from 

this window. The window appearing next indicates that you have 

successfully installed the Lotus Notes client. 

21. Now you are ready to set up the Notes environment for one of the new 

users you just migrated. 

Setting up the Notes client 

In this section, we are going to set up the Notes client for Susi Switch and 

connect the client to the Domino server. Follow these steps: 

1. From the Windows Start Menu, open the Lotus Applications program 

group and select Lotus Notes. The Lotus Notes Client Configuration 

window appears: 



3. Within this window, you can specify if you want to connect to a Domino 

server or if this client will be stand-alone. We left the default to connect 

to a Domino server. 

4. Click Next to continue. The Connection-Type selection window appears: 

5. Select the type of connection you wish for this client according to your 

environment. We decided to set up a connection to our server via LAN 

only. 


6. To continue, click Next. 

7. Enter the name of the server you want to connect to. We entered 

MIGSRV1/ILICDOM in our scenario. 


9. This window lets you specify how you want to be identified as a user of 

the Domino server you want to connect to. You can specify the name of a 

Notes user ID file (which the administrator made available to you), or 

you can use your name as identification. In our scenario, we chose to be 

identified by name and entered Susi Switch in the User name field, as 


Tip Make sure that your Domino server can be accessed from the client 

machine you are setting up through the protocol you are running (TCP/IP, 

NETBIOS, etc…) in your environment. For example, if you use TCP/IP and 

you are unable to ping your Domino server, the client setup will fail. 


10. Click Next to continue with the setup process. 

11. You will see a window with a message telling you that your connection 

to a Domain server over a LAN is set up. 

Tip Keep in mind that there has been no connection made to the server 

at this point. This message only tells you that all the necessary 

parameters are set to connect to a server. 

12. To continue, click Next. You are presented with a series of windows 

letting you specify how to set up the following: 

• Internet Mail Accounts 

• Internet News Servers 

• Internet Directory Servers 

• Internet Connection types (Proxy, etc…) 

13. Provide the setup program with the information needed to set up these 

connections according to your environment. We decided not to set up 

any Internet connections for our scenario. 


14. Click Next to continue from each window until you get to the 

Congratulations window as shown in the following picture: 

15. This window indicates that all the neccessary steps to set up your Notes 

client are completed. Click Finish to continue. Now your client will 

connect to the Domino server for the first time and try to find the user 

name you entered during setup as shown in the upper window in 

the following picture. If the lookup in the Domino Directories was 

successful, you will be prompted to enter a password, as shown in 

the lower section of the following picture. 

16. Enter the proper password for the Notes user for whom you are setting 

up the Notes client. We entered the password for Susi Switch. 

17. Click OK to continue. You will see a window with a message that states 

that the Notes setup is complete. 


18. Click OK to continue. The Lotus Notes Welcome screen appears as 


19. We decided to make the database “Workspace” our current home page. 

When we open Susi Switch’s Notes client, the following window is 

displayed: 

This concludes the section on setting up the Notes client. You are now ready 

to send an upgrade notification message to your users. This is done from the 

Notes administrator program. 


Sending users an upgrade notification message 

Migrated cc:Mail users run an Upgrade Wizard from their Notes client to 

migrate personal mail information from cc:Mail to Notes mail archives and 

Personal Address Books. 

Users run the wizard by clicking a button in the body of a Notes mail 

message you send from the Domino Administrator. The upgrade notification 

message you send contains information about the following: 

• The type of mail system users are migrating from 

• The location of the wizard program files 

• Other information needed to migrate personal mail data 

Before sending the upgrade notification, install the Upgrade Wizard locally 

on each migrated user’s workstation as part of the Notes client, or on a 

network directory that the users have access to. If required, refer to the 

previous section where we described how to install the Upgrade Wizard 

locally on Susi Switch’s workstation. 

Now let’s send an upgrade notification message to our Notes users. 

1. Start the Domino Administrator program. 

2. From the server pane, select the Domino server where you registered the 

migrated users. We selected our server MIGSRV1/ILICDOM. The 

following window is displayed: 


3. In the task pane, click the People & Groups tab, right-click the name of 

the server’s Domino Directory, and select Open Directory. The following 

window appears: 

4. Now we need to check if the administrator has the proper rights in the 

Access Control List (ACL) of the Domino Directory in order to perform 

the upcoming steps. 

From the Notes menu, select File - Database - Access Control. You are 

presented with the Access Control List dialog box as shown in the 

following picture: 


5. From the Basics pane of the Access Control List window, select the 

administrator ID you are using. 

6. From the Roles box, select UserModifier or NetModifier (or make sure 

they are checked). 

Note If you are using a local copy of the Domino Directory, select the 

Advanced pane and check “Enforce a consistent Access Control List 

across all replicas of this database.” 


8. You are returned to the window showing the open Domino Directory. 

Expand the Server view and select Mail Users. The following window 

appears showing you all the Notes mail users in your Domino domain: 

9. As you can see from the previous picture, we have two Domino servers 

in our Domino domain, with server MIGSRV1 hosting our two migrated 

users. 


10. At the top of the Results pane, click the Send Upgrade Notifications 

button. The Upgrade Message form appears, as shown in the following 

picture: 

11. Click Address on the action bar. You are presented with a window 

displaying users, groups and other entries from the Domino Directory 

you selected (we chose ILICDOM’s Address Book): 

12. Select the users you want to send the upgrade message to and click on 

the To button. You will see the users and groups receiving the Upgrade 

Notification in the Recipients box. 

Tip If you added users to a “Migration” group when you registered 

them, address the message to the group name. 


13. Click OK to close the Select Addresses window. You are returned to the 

Upgrade Message window: 

14. In the Administrator Setup section, select “Send out cc:Mail/MS 

Mail/MS Exchange convert local information notices.” 

15. In the Mail Conversion Utility Path section, enter the path to the network 

copy of the Upgrade Wizard, if your users are not running a local copy 

of the wizard. Since we installed the Upgrade Wizard locally when we 

installed Susi Switch’s Notes client, we left this field blank. 

16. In the Mail Conversion Options section, click on the arrow and select 

“cc:Mail” as the mail system users are migrating from. 

17. Now we are going to enter some gateway mapping information as 

follows: 

• We entered “SMTPGATE” in the “Convert the following cc:Mail POs 

from” field, because we had a SMTP gateway with that PO name in 


• We typed “ILICDOM” in the “To the following Notes Domains:” 

field, because we ran an SMTP MTA in our Domino domain. 

The Upgrade Wizard will replace occurrences of cc:Mail gateway names 

in the addresses of migrated messages and in migrated personal 

addresses with the specified Domino domain names. 


For example, let’s assume Susi Switch has an address “micky@ 

disney.com@SMTPGATE” in her cc:Mail Personal Mailing List. The 

Upgrade Wizard will change that address to “micky@disney.com@ 

ILICDOM”. So when Susi as a Notes user sends something to this 

Internet address, the SMTP MTA in Domino will pick it up and deliver it 

to the Internet. The same scenario enables her to reply to messages she 

saved in cc:Mail, using her Notes client. 

18. The Additional Information section displays the text that will be 

included in the upgrade notification that users receive. Administrators 

can edit this text to include additional information about the migration. 

We decided to simply use the default text provided with the message 

form. 

19. The Upgrade Form is now completed, and you are ready to send it to 

your end users. Take another look at our completed form, which is 


20. When you are ready, click the Send button on the action bar to send the 

upgrade message to each user you specified. 

21. You might want to check the Domino server console to see if your 

upgrade messages were actually delivered to your Notes clients. 

22. Let’s have a look at Susi Switch’s Inbox to see if the message arrived, and 

how it looks. The following picture shows a snapshot of the open 

upgrade notification message in Susi’s Inbox: 

This completes the steps required to create and send an Upgrade 

Notification message to users. 


Running the Upgrade Wizard 

Users can launch the Upgrade Wizard by opening the Upgrade Notification 

message received after migration and by clicking a button in the message 

body. The Upgrade Wizard must have been installed either locally, as part 

of the user’s Notes client, or on a shared network directory. Upgrade 

Notification messages must have been sent to users’ Notes mail files after 

migrating their mailboxes using the upgrade tools that are provided by the 

Domino Administrator. We have now finished all the preparation work, as 

described in the earlier sections of this chapter. 

After a user launches the Upgrade Wizard, it automatically checks for a 

Notes installation on the user’s workstation. If a Notes program directory is 

not found, the wizard fails to load. 

The Upgrade Wizard obtains information about the Notes environment from 

the active NOTES.INI file in the Notes data directory and from the Upgrade 

Notification message. For users migrating from cc:Mail Release 2.x and 

Release 6.x, the Upgrade Wizard also obtains information from PRIVDIR.INI 

on the user’s workstation. 

Note Users must run the Upgrade Wizard from a Notes client that is either 

installed on the same computer as the cc:Mail data they want to migrate, or 

at least has access to this data. 


Starting the Upgrade Wizard 

Now let’s go to Susi Switch’s workstation and finally run the Migration 

Wizard. The following steps guide you through the process of running the 

Migration Wizard: 

1. Start the Notes client on your Notes workstation and open the mail file 

of a user you have migrated from cc:Mail to Notes. We have started Susi 

Switch’s workstation and opened her mail file as shown in the following 

picture: 

2. In the open mailbox, you will see a list of all the migrated cc:Mail mail 

messages. The second-last message was created by the Domino Upgrade 

Services and has a copy of the user’s temporary Personal Address Book 

attached (CCPMLIST.NS4). The last message you see in the list is the 

Upgrade Notification message, which was created and sent by the 

Domino administrator. 


3. Double-click on the Upgrade Notification message. The message opens, 

and you can see the contents of the message, as shown in the following 

picture: 

4. Read the Upgrade Message and click on the “Convert Local Data to 

Notes” button to start the Upgrade Wizard. 

Note The last sentence in the Upgrade Message reads “Press the button 

below to convert your cc:Mail DB6 local information to Notes.” You can 

ignore the DB6 part of the sentence, as this upgrade message is the same 

no matter what DB-version of cc:Mail you are going to migrate. 


The Notes Upgrade Services - cc:Mail to Notes part — window is 

displayed: 

When the Upgrade Wizard started, it obtained the information it needs 

to run successfully from the following sources: 

1. Information obtained from the Upgrade Notification message: 

• The type of mail system being migrated (cc:Mail, Microsoft Mail, or 

Microsoft Exchange) 

• The name of the user’s Notes mail server 

• Mapping between cc:Mail post office gateways and Domino 

domains (cc:Mail users only) 

• A message ID; for the cc:Mail to Notes Upgrade Wizard, the 

message ID is used to find the message in the user’s mail file so 

that it can read gateway mapping information for processing 

archives and private addresses. 

2. Information obtained from the NOTES.INI file, found in the Notes 

data directory on the user’s workstation (if not found there, first the 

program directory will be searched, then the system path): 

• Personal Address Book (first entry in “NAMES=”) 

• Location of the Notes data directory (value of “Directory=”) 

• Notes mail file name (value of “MailFile=”) 

• User credentials (for example, password; value of 

“KeyFileName=”) 


Selecting your user name 

Follow these steps to select the cc:Mail user to be migrated. 

1. Click Next to continue with the Lotus Notes Upgrade Services. The 

following window appears, letting you select your cc:Mail user name 

from a list: 

2. Click the down arrow and select your cc:Mail user name, if it is not 

already displayed. In our scenario, we selected Susi Switch. 

Selecting an upgrade method 

Follow these steps to select an upgrade method: 

1. Click Next to Continue. The following window is displayed, giving you 

two choices on how you want the upgrade done: 


2. The Upgrade Wizard lets a user migrate up to three types of personal 

data, as shown in the following list: 

• Private mailing lists 

• Private addresses 

• Archives 

When a user runs the Upgrade Wizard using the default Express 

method, it processes all the available messaging data using the default 

settings. When a Custom upgrade is selected, users can independently 

migrate each of the available data types. 

For example, during a Custom upgrade, a user migrating from cc:Mail 

can independently select private addresses, private mailing lists, and 

archives. The Upgrade Wizard reports an error if it cannot locate or 

convert any of the data types. 

3. We chose the Custom upgrade method for our scenario. 

Selecting upgrade options 

Follow these steps to choose the personal information items you want to 

migrate to Notes. 

1. Click Next to continue. The Upgrade Options dialog box appears: 

2. Users you migrated to Notes may want to retain personal address book 

information from cc:Mail after they switch to Notes. The Upgrade 

Wizard lets users migrate personal address book information to a Notes 

Personal Address Book (PAB). 


There are two types of personal address book entries users can migrate: 

• Personal addresses for users not listed in the public address book; for 

example, Internet e-mail addresses 

• Personal mailing lists for distributing e-mail to multiple addresses at 

one time 

3. When migrating personal address book information, the Upgrade 

Wizard converts private addresses to Contact entries in the PAB. 

Note Users migrating from the cc:Mail Release 8.x client cannot migrate 

private addresses. The reason is that in cc:Mail R2.x and R6.x, private 

addresses are stored in the file PRIVDIR.INI on the user’s workstation, 

and private lists are stored with the user’s mailbox on the server. The 

cc:Mail R8.x client does not use PRIVDIR.INI, so the Upgrade Wizard 

cannot migrate personal addresses for R8.x users. 

4. Personal mailing lists are converted to multi-purpose groups in the PAB. 

5. The Upgrade Wizard copies information from message attachments and 

data files to the PAB on the user’s Notes client. 

6. When migrating cc:Mail personal address book information, the 

Upgrade Wizard extracts some personal address book information from 

a message attachment and some from a data file on the user’s 

workstation. 

7. The Upgrade Wizard obtains a user’s private mailing lists, which are 

stored with the user’s cc:Mail mailbox, from a PAB attachment in the 

user’s Notes mail file. 

Note To update a user’s Notes Personal Address Book with 

information migrated from the cc:Mail user’s private mailing lists, the 

Upgrade Wizard copies personal address book information from a 

temporary Public Address Book sent to the user in an upgrade message. 

The Upgrade Wizard detaches the temporary PAB (CCPMLIST.NS4) 

from the upgrade notification message and copies the data from this 

database to the user’s regular Personal Address book (NAMES.NSF). 

Important At the time of writing this redbook, we used the Upgrade 

Wizard within the Lotus Notes R5.0.1a client. During our tests, we found 

that this version of the Upgrade Wizard will not copy the data from the 

temporary PAB to the user’s standard PAB. We found that the 

temporary PAB coming from the Domino Upgrade Services contained 

all the migrated data from the user’s cc:Mail private mailing lists. 

There are plans to fix this issue with the Upgrade Wizard in a future 

release. 


Tip If you are going to perform a migration using the Upgarde Wizard 

with the Notes R5.0.1a client, and if you run into the same problem as 

explained in the preceding Important section, you can use the following 

workaround for the problem: 

Tip Open the temporary PAB (CCPMLIST.NS4) from your 

NOTES\DATA directory. Select all the entries within the Contacts 

view (remember — entries from the cc:Mail user’s Private Mailing 

List become Contacts in Notes), and copy them to the clipboard. 

Close the temporary PAB and open your own Personal Address Book. 

Make sure you are in the Contacts view, and paste the entries from the 

clipboard into this view. This way you (the end user) have manually 

done what the Upgrade Wizard will be able to do in a future release. 

We performed exactly those same steps to bring the Contacts entries 

from the temporary PAB into Susi Switch’s PAB, as you will see later in 

this chapter. 

Because we were migrating users from cc:Mail R8.x, we unchecked 

Private Addresses in the Upgrade Options dialog box as shown in the 

previous picture. The Upgrade Wizard will not migrate Private 

Addresses for cc:Mail R8.x for reasons we already explained earlier in 

this step. 

Selecting archive conversion options 

Follow these steps to specify archive conversion options: 

1. Click on Next to Continue. The Archive Conversion Options window 

appears, as shown in the following picture: 


2. The options in this window let you specify what archive files you want 

to convert and in what location you want the Notes archive database to 

be stored. The cc:Mail Archives box lets you choose one of the following: 

• Migrate all archive files specified in WMAIL.INI 

• Select archive files to migrate 

If you select “Migrate all archive files specified in WMAIL.INI,” the 

Upgrade Wizard will migrate all .CCA files in the location specified in 

the [cc:Archives] section of WMAIL.INI. If you choose “Select archive 

files to migrate,” you can click Select Files… and select archive files from 

a location in the file system. 

Note The cc:Mail Release 8.x client does not store information in the file 

WMAIL.INI. As a result, when users of the Release 8.x client perform an 

Express upgrade, the Upgrade Wizard does not migrate any archive 

files. To migrate archives, cc:Mail Release 8.x clients must use the 

Custom migration option and specify the location of archive files to 

migrate. 

3. Because we were using a cc:Mail Release 8.x client, we had previously 

selected “Custom — select items to convert to Notes” as the Upgrade 

method and “Select archive files to migrate,” which enabled us to 

specify the location of the cc:Mail archive files ourselfes. 

4. Click on Select Files… to continue. The Select Archive Files window 

appears, as shown in the following picture: 


5. Browse through your file system and select the archive files you want to 

be converted to Notes archive databases. In our scenario, we selected 

one cc:Mail archive file (SAV0830.CCA), which was located on the C: 

drive in CCMAIL\CLIENT\SUSI SWITCH. 

6. Click Add to add the files you chose to the Selected files box, then click 

Done to close this window. You are returned to the Archive Conversion 

Options screen, as shown in the following picture: 

• The Notes Archives box lets you select the following: 

• The Notes mail file template to be used in creating the Notes archive 

database 

• The directory in which to create the resulting Notes mail archive 

database 

7. The mail template specified in the “Template name” field will be used 

by the Upgrade Wizard in order to create a Notes archive database. By 

default, this is the template specified by the “DefaultMailTemplate” 

variable in the user’s NOTES.INI file. This variable should not be 

changed in most instances. 

8. In the “Folder” field, you can specify where the Upgrade Wizard will 

store the resulting Notes archive database. By default, the Upgrade 

Wizard migrates all archives into a single Notes mail file database. By 

default, the database is created in the MAIL subdirectory of the user’s 

Notes data directory, as specified in NOTES.INI. 

9. This location could also be a mapped drive pointing to a user’s home 

directory somewhere on a LAN resource. 


10. Specify what archive files you want to convert and in what location you 

want the Notes archive database to be stored. Leave the default name 

MAIL50.NTF in the Template name field, unless you have a reason to 

change it. 

11. We chose to leave the defaults for the fields in the “Notes Archives” box. 

Performing the upgrade 

Follow these steps to finally perform the upgrade to Notes. 

1. Click Next to continue. The Begin Upgrade window is displayed, as 


2. Click the Finish button to start the upgrade process. You are presented 

with a window where you must enter the Notes user’s password, so that 

the Upgrade Wizard is able to create the archive database. We entered 

Susi Switch’s password because we are using her Notes ID for this 

migration. 


3. Enter the proper password and click OK to continue. The Upgrade in 

progress window appears. 

4. You can watch the upgrade progress by looking at the contents of the 

window, as shown in the previous picture. 

5. When the Upgrade Wizard has finished processing the data you had 

selected, you are presented with the following window: 

The previous picture shows us that the Upgrade Wizard has completed 

converting our cc:Mail mailing lists and cc:Mail archives. It is now time 

to verify the results of the migration and check the logs for any possible 

errors. 


Checking if the migration was successful 

If the Upgrade Wizard encounters errors while processing archive files or 

directory information, it skips to the next record and continues. Failures are 

logged, and after the wizard finishes processing all of the information, it 

displays a status message reporting the number of messages processed. 

Users may find that the message count of the migrated archive is lower than 

the message count in the original archive. If there were multiple copies of 

one message in the original archive, or in different archives, only one copy of 

the message is migrated. 

After the Upgrade Wizard finishes converting data from cc:Mail into Notes 

data, users should complete the following tasks: 

• Check the Miscellaneous Events in the Notes log (LOG.NSF) to find out 

whether there were any problems that might require further attention. 

• Verify that all messages in the source archive migrated successfully to 

the Notes mail archive. 

• Remove the obsolete cc:Mail files from the user’s workstation. Before 

users delete any data, it is recommended that they back up their old mail 

files. 

Every Notes user who performed a migration of his or her cc:Mail personal 

address book and/or cc:Mail archive files using the Upgrade Wizard would 

typically check the logs for errors and verify that all the data have arrived in 

Notes and are complete. 

The following steps will show you how we made these checks for Susi 

Switch, the Notes user for whom we migrated the cc:Mail data: 

1. Start the Notes client. 

2. Select File - Database - Open from the menu bar. 

3. Double-click on the log file for the user (LOG.NSF). The log file is 

opened. 

4. Select the Miscellaneous Events view. 


5. Look for the document with the date and time when the migration 

process was performed. You should see log entries related to the 

migration you performed as displayed in the following picture: 

6. The log shown in the previous picture represents Susi Switch’s log, and 

we can see that the Upgrade Wizard successfully processed Susi’s 

cc:Mail Private Address lists as well as her cc:Mail archives. 

7. Now that we know, according to the log file, that the data have been 

migrated successfully, let’s have a look at the contents in Notes. 

8. Open the user’s Public Address Book (PAB) in Notes and select the 

Group view. You should see the groups the user had in cc:Mail 

displayed in the view, as shown in the following picture: 


9. The previous picture shows that Susi had one private mailing list in 

cc:Mail, which got migrated over to Notes as a group. 

In order to verify the contents of the migrated groups, double-click on a 

group entry. This is the contents of Susi’s group “Team:” 

The following picture shows how this private mailing list looked in 

cc:Mail: 


10. Open the Contacts view in the user’s Personal Address book. You should 

see all the contacts which were manually transferred from the temporary 

PAB using copy and paste. We described the reason for this manual 

process earlier in this chapter. The following picture show the three 

contacts as they appear in Susi Switch’s PAB: 

11. For reference, the following picture shows how these three entries 

looked in Susi Switch’s personal address book in cc:Mail: 


12. Now let’s have a look at how the cc:Mail archives have been converted 

into a Lotus Notes archive database. 

As described earlier in this chapter, the Upgarde Wizard will migrate all 

cc:Mail archives selected into a single Notes mail file database. This 

database is stored into the MAIL subdirectory in the user’s Notes data 

directory. 

The Notes archive database derives an eight-character name from the 

Notes name of the migrated user, to which a prefix A_ is added. So the 

name of Susi Switch’s Notes archive file should be A_SSWITC.NSF. 

13. To open the Notes archive database, select File - Database - Open from 

the menu bar on the Notes client desktop. 

14. Double-click on the MAIL subdirectory to open it. You should see an 

archive database that looks similar to this: 


15. In our scenario, we double-clicked on a_sswitc (cc:Mail Migrated 

Archive) in order to open the database with Susi Switch’s migrated 

cc:Mail archive files. The following window appeared: 

This window displays the contents of the Notes archive mail file, which 

was converted over from an archive file created in cc:Mail. 

This concludes the steps neccessary to look at the migrated user’s log file, 

mailing list data and archive files in order to verify that the migration was 

successful. 


Summary 

In this chapter, we first gave an overview of the user-based Upgrade Wizard 

tool and its functions. 

Then we described which cc:Mail data are migrated by the Upgrade Wizard 

and which data are not migrated. 

Next, we explained the steps required to install the Notes client, including 

the Upgrade Wizard. 

We documented how the Notes client is set up, as well as the steps 

neccessary for the administrator to send an upgrade notification message to 

end users. 

Then we showed you how to run the Upgrade Wizard in order to migrate 

local data from cc:Mail to Lotus Notes. 

Finally, we looked at the end user’s log file and the converted data in Lotus 

Notes to find out if the migration was successful. 


Chapter 6 

Migrating Organizer data with the user migration tool 

This chapter discusses the migration of stand-alone Organizer data. 

Stand-alone Organizer users are defined as people who use Organizer 

but do not connect in any way to other Organizer users. 


• An overview of the migration process 

• Configuring the general settings 

• Migrating Organizer data 

• Summary 

An overview of the migration process 

The migration tool for stand-alone Organizer is provided as part of the 

Notes R5 client. It is an end-user based migration tool. 

A copy of the migration database is located on the Domino server where the 

administrator configures the general settings. The database is then 

distributed to the users. In their own time, users can enter their personal 

Organizer details and migrate the required information to Lotus Notes. 

The following information can be migrated from Organizer to Notes: 

Organizer 

Calendar 

To Do 

Address 

Calls 

Planner 

Notepad 

Anniversaries 

Lotus Notes 

User’s mail database, as appointments 

User’s mail database, as tasks 

Personal Address book 

User’s mail database, as tasks 

User’s mail database, as events 

Personal Journal database 

User’s mail database, as anniversaries 

155

Configuring the general settings 

A number of general settings need to be configured by the administrator. 

Once these are set, users will be able to use the database to migrate their 

local Organizer files. 

To configure the settings, follow these steps: 

1. From your Lotus Notes client, open the database called cs2notes50.nsf. 

This database is installed as part of the Notes client install. 

2. From the main view, select Lotus Organizer. 

3. Choose Settings from the navigator. If no settings document exists, a 

new Settings for Organizer Migration document will appear. Edit this 

document if it already exists. 


The Organizer migration document looks like this: 

4. The first setting in this document is Users’ Organizer directory. Enter the 

path where the user has Organizer installed. 

Tip Think of this path as if you were sitting at the user’s desk. 

5. Selecting the check box for Repeat Anniversaries will add any repeating 

anniversaries from Organizer to the user’s Notes calendar. You can also 

specify how long to repeat these anniversaries. 

6. In the section, Do you have a Group Scheduling installation of 

Organizer?, select one of the four options provided. 

Note The No (PIM only) option is the same as stand-alone Organizer. 

7. In the section, Where your copy of Organizer is installed, click 

Workstation if the user is running Organizer from his or her own 

machine. If the Organizer client is installed on a file server, click Server. 

Chapter 6: Migrating Organizer data with the user migration tool 157

If you click Server, the document will change to display the following: 

The button that is provided will install the required API files into the 

correct directory on the server. To ensure that the files have been 

installed correctly, check the status bar at the bottom of your Notes 

client. 

Note For this to work, the administrator will require write access to the 

Organizer directory on the server. 

8. The last setting in the migration document lets you specify who can 

modify this document. We recommend that the administrator’s group 

be added to this list. 

Note Everybody in this list has edit access to the document. 

Migrating Organizer data 

The Organizer migration tool is an end-user based tool. This means that 

users wishing to migrate their Organizer data will need to enter information 

relating to their Organizer setup. 

Once the users have access to the Calendar and Schedule Migration database 

located on the Domino server, they can migrate their personal Organizer 

information. 


Follow these steps to migrate your Organizer data: 

1. Open the Calendar and Schedule Migration database (cs2notes50.nsf). 

The following screen is displayed: 

2. Click on Lotus Organizer. The following screen is displayed: 

3. Select Click Here to Create or Modify Migration Document. This 

displays the user migration document. 


Define Source section 

In the first step, you need to provide your personal Organizer information. 

The Define Source section of the migration document looks like this: 

1. Select what version of Organizer you are using. Organizer 2.1 is selected 

by default. 

2. In the Organizer directory field, select the path to the Organizer 

executable files. If you are running from a node install of Organizer, you 

need to enter the path to the local information. 

3. To select the Organizer filename, use the Browse button if required. 

4. The Organizer Login Name is only required if you have group 

scheduling installed. In this case, add your name as it is known in 


Click the Button to Export section 

Once the correct user information has been entered, it is time to export the 

information out of the Organizer file. 

1. Click the Export Organizer File button, as shown in the following figure: 

2. A dialog box is displayed that lets you choose what sections of 

Organizer you want to migrate. By default, all options are selected. Click 

OK to continue. 


When the export is completed, the following screen is presented: 

3. Click OK to proceed to the next step. 

Define Destination section 

In this stage of the process, you need to define the destination of the 

information you have just exported. The following figure shows the Define 

Destination section where you specify that information: 

1. Click the Find my mail file button to complete the Mail File information 

field. The relevant information is retrieved from the NOTES.INI file. 


You may want to click the Verify mail button to open the mail file. This 

enables you to confirm that this is indeed your mail file. The following 

message is displayed before the mail file is opened. 

2. Click OK. Once the mail file has opened successfully, close it to return to 

the migration document. 

3. By default, the second field in the document titled Your Local Name and 

Address Book is automatically filled in. Click the Verify NAB button to 

ensure that the correct Personal Address Book is being used. The 

following message is displayed: 

4. The last field in the Define Destination section asks you to enter the 

name of your Personal Journal. You can leave this blank since a personal 

journal will be created if it is required. For the tool to create the personal 

journal, it requires access to the journal.ntf file. 

Note When using the Notes R5 client, the personal journal database is 

not created. 


Click the Import Button 

With all of the information correctly added, it is now time for the user to 

click the Begin Import button. This adds the information that was exported 

from Organizer into Lotus Notes. 

You can check the status of the import process in the status bar. 

When the import is completed, the following message appears: 

Reopen this document to see statistics section 

Now that the process is complete, you can view the statistics of what has 

been migrated. To do this, first close the current migration document and 

then reopen the same document. 

You can find the migration statistics at the end of the document. It looks like 

this: 


Summary 

This chapter described the steps involved in migrating stand-alone 

Organizer data using the end-user based migration tool provided with the 

Notes R5 client. 

First, we gave an overview of the migration process. We listed the Organizer 

data that is migrated by the tool, and how it appears in Notes. 

Then, we covered the general settings that need to be configured by the 

administrator, before showing the steps that the users need to perform to 

migrate their Organizer data. 


Special notices 

This publication is intended to help cc:Mail and Lotus Domino 

administrators migrate users and data from cc:Mail and Organizer to Lotus 

Domino R5. 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’s product, program, or service may 

be used. Any functionally equivalent program that does not infringe any of 

IBM’s 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, North Castle Drive, Armonk, 

NY 10504-1785. 

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 vendor 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 

Special notices 165

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. 

This 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 Organizer® 

Lotus® NotesSQL 

Lotus Domino Notes/FX 

Lotus Notes Reporter Phone Notes® 

Lotus Notes® Phone Notes Mobile Mail 

Video Notes SmartIcons® 

Word Pro 

The following terms are trademarks of other companies: 

C-bus is a trademark of Corollary, Inc. in the United States and/or other 

countries. 

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 in the United 

States and/or other countries 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. 

UNIX is a registered trademark in the United States and/or other countries 

licensed exclusively through X/Open Company Limited. 

SET and the SET logo are trademarks owned by SET Secure Electronic 

Transaction LLC. 

Other company, product or service names may be the trademarks or service 

marks of others. 

Special notices 167

168 Book Title

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.” 

 

 

 

 

 

 

 

 

A Roadmap for Deploying Domino in the Organization, IBM form number 

SG24-5617, Lotus part number CT6P8NA 

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 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 

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 

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 

The Next Generation in Messaging: Moving from Microsoft Mail to Lotus 

Notes and Domino, IBM form number SG24-5152, Lotus part number 

CT7SBNA 

The Next Generation in Messaging: Moving from Novell GroupWise to Lotus 

Notes and Domino, IBM form number SG24-5321, Lotus part number 

CT7NNNA 

Lotus Domino R5.0 Enterprise Integration: Architecture and Products, IBM 

form number SG24-5593, Lotus part number CT6QUNA 

169

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 

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 

12996 

Lotus Solutions for the Enterprise, Volume 5. NotesPump, the Enterprise Data 

Mover, IBM form number SG24-5255, Lotus part number CT69DNA 

Lotus Domino R5.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.6: Installation, Customization & 

Administration, 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 (soft copy only) 

Using ADSM to Back Up Lotus Notes, IBM form number SG24-4534 

NetFinity V5.0 Database Support, IBM form number SG24-4808 

Lotus Approach to DB2, IBM form number SG24-4685 

Related publications 171

Redbooks on CD-ROMs 

Redbooks are also available on the following CD-ROMs. Click the CD-ROMs 

button at http://www.redbooks.ibm.com/ for information about all the 

CD-ROMs offered, updates and formats. 

CD-ROM Title 

Lotus Redbooks Collection 

Tivoli Redbooks Collection 

Application Development Redbooks Collection 

RS/6000 Redbooks Collection (BkMgr) 

RS/6000 Redbooks Collection (PDF Format) 

AS/400 Redbooks Collection 

Transaction Processing and Data Management Redbooks Collection 

Networking and Systems Management Redbooks Collection 

System/390 Redbooks Collection 

Netfinity Hardware and Software Redbooks Collection 

IBM Enterprise Storage and Systems Management Solutions 

Collection Kit 

Number 

SK2T-8039 

SK2T-8044 

SK2T-8037 

SK2T-8040 

SK2T-8043 

SK2T-2849 

SK2T-8038 

SK2T-6022 

SK2T-2177 

SK2T-8046 

SK3T-3694 


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 by e-mail including information from the redbooks fax order form to: 

e-mail address 

In United States: 

Outside North America: 

usib6fpl@ibmmail.com 

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 1-403-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 may be found at the redbooks Web site. 

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 access MyNews at http://w3.ibm.com/ for redbook, 

residency, and workshop announcements. 

173


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. 

175

176

Index 

A 

Adding the MTA as a server task, 38 

ADE propagation changes, 31 

ADE relationships, 4 

Admin utility, 4 

Administration tools, 4 

Administrator access to the 

mail file, 81 

Administrator-based migration 

tool, 49 

Advanced MTA design, 11 

Aliases, 6, 32 

Archives, 51, 117, 143, 144 

Automatic Directory Exchange, 4 

Automatic restart of the MTA, 26 

B 

Backing up data, 39, 58, 148 

Bad message queue, 29 

Basic cc:Mail concepts, 1 

Broadcaster, 19 

Bulletin boards, 42, 76, 105 

C 

Call password, 19 

Calling the post office, 20 

calllists, 5 

cc:Mail basics, 1 

cc:Mail MTA configuration, 21 

cc:Mail MTA, installation, 7, 8 

cc:Mail MTA, operation, 37 

cc:Mail Post Office Server 

document, 18, 29 

cc:Mail Release 6.3, 75, 78 

cc:Mail Router, 4, 16 

cc:Mail subnet, 19 

CCPOMS, 3 

Checking the Domino log, 40 

Checking the logs, 99, 100, 148 

CLANDATA, 3 

Cleaning up the directories, 39 

Comments field, 90 

Configuration Assistant, 10 

Configuring the Domino server, 11 

Configuring the MTA, 21 

Connection document, 32 

Conversion types, 17 

Creating a calllist entry, 38 

Custom installation, 54 

D 

DB6 post office, 3, 30, 50 

DB8 post office, 3, 30, 50 

Designer access, 7 

Directory conversion, 17 

Directory entry, 5 

Disk space, 54 

Division propagation type, 19 

Domino Administrator client, 58 

Domino domain name, 7 

Domino Upgrade Services, 49 

Downloading the cc:Mail MTA, 8 

Duplicate group names, 84 

E 

Enterprise propagation types, 19 

F 

File-sharing, 2 

Foreign cc:Mail Domain document, 

34 

G 

Gateways, 6 

H 

Hub post office, 8, 18 

I 

Inactive accounts, 55 

Included sections, 91 

Installing the Administrator client, 58 

Installing the cc:Mail MTA, 7, 8 

Installing the Notes client, 124 

Installing the Upgrade Wizard, 118 

Invalid names, 56 

L 

load ccmta, 37 

Location types, 5, 79, 101 

M 

Mail file, administrator access, 81 

Mailing-list titles, 31 

Meeting invitations, 52 

Message conversion, 17 

Message size limit, 27 

Message store, 3 

Migrated data, 50, 52 

Migrating bulletin boards, 105 

Migrating Organizer data, 90, 155 

Migrating personal cc:Mail data, 117 

Migrating private mailing lists, 115 

Migrating public mailing 

lists, 84, 102 

Migrating users, 66 

Migration tools, 49, 58, 155 

MLANDATA, 3 

Mobile users, 118 

MSGMGR, 54 

MTA calling Router, 33 

MTA Server form, 15, 24 

MTATBLS.NSF, 7, 10 

Multi-domain Notes backbone, 27 

Multiple Connection documents, 33 

Multiple Router sessions, 5 

N 

Nested folders, 51 

Nested groups, 88 

Network drive, 16 

Notes backbone, 27 

Notes group names, 31 

Notes Named Network, 19 

177

O 

Operating the cc:Mail MTA, 37 

Organizer, 6, 32, 90, 155 

Organizer calls, 109 

P 

Passwords, 57, 80 

Pending mail messages, 7 

Pending meeting notices, 91 

Performance, 53, 54 

Personal address book 

information, 141 

Polling time interval, 43 

Port 21, 16 

Port CC0, 16, 38 

Post office mail queues, 58 

Post office structure, 2 

Pre-installation tasks for MTA, 7 

Preparation tasks, 53, 55 

Private mailing lists, 

51, 75, 115, 117, 142 

PRIVDIR.INI, 51 

Propagating Notes groups, 47 

Propagating public mailing lists, 47 

Propagation types, 19 

Protocols, 16 

Public Address Book, 13 

Public Mailing Lists, 23, 47, 84 

T 

tell ccmta q, 38 

Testing mail transfer, 115 

To Do section, 110 

Types of Notes groups, 87 

U 

Upgrade notification message, 130 

Upgrade Wizard, 51, 117 

Using the Configuration 

Assistant, 10 

V 

Verification tasks, 99, 148 

VIM applications, 6 

W 

Work path, 16 

Workaround, 143 

R 

Registration Server, 69 

Release 8.x client, 142, 144 

Repeating items, 52 

Restart timer field, 25 

Router utility, 4 

Routing tasks field, 24 

Running the Upgrade Wizard, 136 

S 

Scheduled meetings, 107 

Selecting the MTA server, 14 

Setting up the Notes client, 124 

Short name, 28 

Single-copy message store, 3 

Stand-alone Organizer, 155 

Starting the MTA, 37 

Stopping the MTA, 38 

Subnet, 19 

Synchronizing the directories, 39 


ITSO redbook evaluation 


SG24-5649-00 

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 this form 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 

179

180

xii Lotus Domino Release 5.0: A Developer’s Handbook

Printed in the U.S.A. 

SG24-5649-00 

Part No. CT6Q9NA 

Moving from cc:Mail to Lotus Domino R5 SG24-5649-00

Moving from cc:Mail to Lotus Domino R5 Moving ... - IBM Redbooks

Create successful ePaper yourself

Delete template?

Save as template?