지금 지원 담당자와 채팅
지원 담당자와 채팅

Coexistence Manager for Notes 3.8.4 - User Guide

About the CMN Documentation Suite Introduction CMN Directory Connector
Directory Connector overview Installation and configuration DC Management Console Connector Creation Wizard Connector Advanced Settings Starting and stopping the Directory Connector service
CMN Mail Connector
Mail Connector features overview Coexistence mail routing basics Deployment of CMN Mail Connector Installation Configuration Mail Connector Management Console
CMN Free/Busy Connector The Log Viewer Appendix A: Known limitations Appendix B: Troubleshooting Appendix C: CMN Logs

Coexistence mail routing basics

Email coexistence, with or without CMN, can be configured within a single domain ("single namespace"), or you can differentiate the two environments with different domains or subdomains—for example, domino.sitraka.com vs. exchg.sitraka.com. CMN’s Mail Connector integrates easily into either method.

NOTE: When coexisting with Office 365: Direct free-busy lookups from Office 365 to Notes are not possible with a single-namespace configuration, in either a hybrid or non-hybrid implementation, due to access/permission restrictions to the remote Microsoft servers. Bi-directional free/busy features with Office 365 can be configured only with routing domains (e.g., coexist.sitraka.com).

By the multi-domain/subdomain method, Domino and Exchange are assigned different subdomains to differentiate the two internally (within your network), so email can be routed between the two servers by SMTP addressing and your organization's DNS configuration. To insert CMN’s Mail Connector into this scheme, point the outbound traffic from each server to the Mail Connector server, and point the Mail Connector’s outbound mail to the appropriate Notes or Exchange server, depending on the domain/subdomain name in the address.

The multi-domain/subdomain methods are straightforward, but configuration is somewhat more complicated than with the single-namespace methods. A subdomain routing method may also introduce a risk that the assigned subdomain names will escape your organization’s internal communications, which in turn can cause bounce-backs on replies to those addresses. To prevent this, set the Notes forwarding address attribute to user@subdomain@notesdomain, which tells Domino to set the reply address for external email to the user's primary SMTP address (internet address field value).

A single-namespace mail coexistence is accomplished by using smart hosts in both directions.

Single-namespace message routing without CMN

Email coexistence, with or without CMN, can be configured within a single domain ("single namespace"), or you can differentiate the two environments with different domains or subdomains—for example, domino.sitraka.com vs. exchg.sitraka.com. CMN’s Mail Connector integrates easily into either method.

NOTE: When coexisting with Office 365: Direct free-busy lookups from Office 365 to Notes are not possible with a single-namespace configuration, in either a hybrid or non-hybrid implementation, due to access/permission restrictions to the remote Microsoft servers. Bi-directional free/busy features with Office 365 can be configured only with routing domains (e.g., coexist.sitraka.com).

By the multi-domain/subdomain method, Domino and Exchange are assigned different subdomains to differentiate the two internally (within your network), so email can be routed between the two servers by SMTP addressing and your organization's DNS configuration. To insert CMN’s Mail Connector into this scheme, point the outbound traffic from each server to the Mail Connector server, and point the Mail Connector’s outbound mail to the appropriate Notes or Exchange server, depending on the domain/subdomain name in the address.

The multi-domain/subdomain methods are straightforward, but configuration is somewhat more complicated than with the single-namespace methods. A subdomain routing method may also introduce a risk that the assigned subdomain names will escape your organization’s internal communications, which in turn can cause bounce-backs on replies to those addresses. To prevent this, set the Notes forwarding address attribute to user@subdomain@notesdomain, which tells Domino to set the reply address for external email to the user's primary SMTP address (internet address field value).

A single-namespace mail coexistence is accomplished by using smart hosts in both directions.

Single-namespace message routing without CMN

The next three diagrams illustrate email routing in a single-namespace mail coexistence between Notes and Exchange—without CMN. This is native functionality and does not involve any Quest product.

The step numbers here correspond to the numbers in the diagram:

Inbound traffic is routed to Notes first in this example, but could just as easily be routed to Exchange first.

The step numbers here correspond to the numbers in the diagram:

1
 Message sent from one native Notes user to another. Delivered locally: Domino recognizes the recipient’s valid local (Notes) address, so routes in internally rather than sending to the smart host.
2
Message sent from native Notes user to Exchange user. Two possibilities: The Exchange user either is unknown to Notes, or is represented in Notes only by a person document. In either case, Notes cannot find a local mail file for the recipient, so routes the message to the smart host for relay to Exchange, where a recipient lookup permits delivery to the appropriate mailbox. If the recipient is present in the Domino directory, then Notes found the forwarding address in the contact document (mail system is also set to "Other Internet Mail") and sent it with the message to the smart host.

This diagram labels the Exchange smart host as the "Send Connector," which is the Exchange brand of smart host.

The step numbers here correspond to the numbers in the diagram:

1
Message sent from one native Exchange user to another. Delivered locally: Exchange recognizes a valid local mailbox for the message, so routes it internally (doesn’t send it to the Send Connector for external delivery).
2
Message sent from native Exchange user to Notes user. Two possibilities: The Notes user either is represented in Active Directory as an external contact, or is simply unknown to Exchange. In the first case, Exchange finds a forwarding address associated with the contact ("targetaddress" attribute in AD), and sends the message via the Send Connector to Domino, where it is delivered to the appropriate mail file. In the second case, the message is still routed to Notes via the Send Connector, but Notes will be able to deliver it only if the appropriate mail file exists.

Email coexistence before and after CMN

Remember that email coexistence can be configured either within a single namespace, or by differentiating the two environments with different domains (or subdomains—e.g., domino.sitraka.com vs. exchg.sitraka.com). The CMN Mail Connector is easily integrated into either strategy, but most admins prefer the single-namespace approach because it is usually simpler to configure.

The sections below explain and illustrate how Quest's CMN Mail Connector integrates into a single-namespace coexistence between Notes and Exchange. Round-robin traffic distribution can be used for load balancing and redundancy among multiple CMN servers.

SMTP mail routing within a single domain is accomplished using smart hosts in both directions, as shown in the illustration here. Exchange can be configured to route mail to a smart host (the Exchange Send Connector) if Exchange determines the recipient is not in its local Internet domain. Exchange reads the targetAddress attribute in the AD object record to route mail for such recipients to the Send Connector. Meanwhile, Domino is configured to do the same thing in reverse for a recipient whose local internet domain address is not listed in any Domino person documents.

The step numbers here correspond to the numbers in the diagram:

NOTE: When coexisting with Office 365: Direct free-busy lookups from Office 365 to Notes are not possible with a single-namespace configuration, in either a hybrid or non-hybrid implementation, due to access/permission restrictions to the remote Microsoft servers. Bi-directional free/busy features with Office 365 can be configured only with routing domains (e.g., coexist.sitraka.com).

The step numbers correspond to the numbers in the above diagram:

Any of CMN’s defined outbound servers may in turn point to a load balancer, in which case multiple DNS host records can be created, each for a different IP address, but the same host name. For example, three cmn.sitraka.com records can be created, each with a different IP. See this Microsoft article for more information about DNS round robin.

관련 문서

The document was helpful.

평가 결과 선택

I easily found the information I needed.

평가 결과 선택