|
CONFIGURE THE NOTES
CONNECTOR FOR DIRECTORY SYNCHRONIZATION
We will use the Microsoft Exchange Connector for Lotus Notes (or Notes
Connector) to perform directory synchronization between Exchange and
Notes/Domino while routing mail via SMTP.
As stated previously, we recommend creating a secondary directory to
store Exchange recipient addresses in Notes rather than updating the
primary directory. We’ll name the secondary directory file EXCHANGE.NSF.
By default, the Notes Connector requires all messages routing between
the two systems to funnel through the Notes Connector itself using the
Notes Remote Procedure Call (NRPC). The Notes Connector updates
EXCHANGE.NSF with the NOTES proxy addresses pulled from the Exchange
directory (the specified Active Directory containers).
To circumvent using the Notes Connector for mail routing, we modify the
mapping tables used by the Notes Connector to write SMTP addresses
(instead of NOTES addresses) to the Notes secondary directory,
EXCHANGE.NSF. As a result, when Notes users address the Exchange
recipients found in EXCHANGE.NSF, they use their SMTP addresses. Notes
recognizes the recipients as SMTP addresses and routes messages using
SMTP.
After modifying the mapping tables, delete any recipient entries created
by the Notes Connector default installation from both EXCHANGE.NSF and
the specified Notes Connector Import Container (an AD Contacts container
storing the Notes recipient entries). Restart the Notes Connector
service and commence a full rebuild of the directories, both from
Exchange to Notes and Notes to Exchange.
Send some email tests for functional assurance, set the Notes Connector
directory synchronization schedule as desired, and we’re done. The
Notes Connector should now write Notes recipients to the AD Contacts
container and Exchange recipients to the Notes secondary directory using
SMTP proxy addresses. Notes users, as well as external/Internet mail
users, should be able to route mail to Exchange users (and vice versa)
using SMTP.
Jayme Bowers
is a Solutions
Architect with Mesa Software and Services specializing in Lotus/IBM and Microsoft messaging
and application migration and coexistence.
Steve Bryant and
Jason Sherry, Pro Exchange Infrastructure Architects, also
contributed to this article.
Appendix A: Email
Tests for Quality Assurance
Test the configuration by sending mail to and from Exchange users,
external users and invalid mail addresses (to test NDR generation).
Perform the following tests for quality assurance. Send from:
-
ExchUser to
NotesUser@finance.abc.com
-
ExchUser to
NotesUser@banking.abc.com
-
ExchUser to User@ExternalDomain.com
-
ExchUser to
InvalidUser@finance.abc.com
-
ExchUser to
InvalidUser@banking.abc.com
-
ExchUser to
InvalidUser@insurance.abc.com
-
NotesUser to
ExchUser@finance.abc.com
-
NotesUser to
ExchUser@insurance.abc.com
-
NotesUser to User@ExternalDomain.com
-
NotesUser to
InvalidUser@finance.abc.com
-
NotesUser to
InvalidUser@banking.abc.com
-
NotesUser to
InvalidUser@insurance.abc.com
-
User@ExternalDomain.com
to ExchUser@finance.abc.com
-
User@ExternalDomain.com
to ExchUser@insurance.abc.com
-
User@ExternalDomain.com
to NotesUser@finance.abc.com
-
User@ExternalDomain.com
to NotesUser@banking.abc.com
-
User@ExternalDomain.com
to InvalidUser@finance.abc.com
-
User@ExternalDomain.com
to InvalidUser@banking.abc.com
-
User@ExternalDomain.com
to InvalidUser@insurance.abc.com
-
(if applicable)
User@ExternalDomain.com to First_MI_Last@banking.abc.com
-
(if applicable)
User@ExternalDomain.com to First_MI_Last@finance.abc.com
|
