Chat now with support
Chat with Support

Coexistence Manager for GroupWise 1.7 - User Guide

About the CMG documentation suite Introduction CMG Directory Connector
Directory Connector overview Installation and configuration DC Management Console Connector Creation Wizard Connector Advanced Settings Running and stopping the Directory Connector service
CMG Mail Connector CMG Free/Busy Connector The Log Viewer Appendix A: Known limitations Appendix B: Troubleshooting Appendix C:Configuring CMG logging

Coexistence mail routing basics

Email coexistence, with or without CMG, can be configured within a single domain ("single namespace"), or can be accomplished by differentiating the two environments with different domains or subdomains—for example, vs. The CMG Mail Connector integrates easily into either method.

By the multi-domain/subdomain method, GroupWise 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 the DNS configuration. To insert CMG’s Mail Connector into this scheme, point the outbound traffic from each server to the CMG Mail Connector server, and point the CMG Mail Connector’s outbound mail to the appropriate GroupWise or Exchange server, depending on the domain/subdomain name in the address.

The multi-domain/subdomain methods are straightforward, but configuration is more complicated than with single-namespace methods. Single-namespace mail coexistence is accomplished by using smart hosts in both directions.

Single-namespace message routing without CMG

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

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

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

Again, the step numbers correspond to the numbers in the diagram:

Message sent from one native GroupWise user to another. Delivered locally: GroupWise recognizes the recipient’s valid local (GroupWise) address, so routes it internally rather than sending to the smart host.
Message sent from native GroupWise user to Exchange user. Two possibilities: The Exchange user either is unknown to GroupWise, or is represented in GroupWise only as an external contact. In either case, GroupWise 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 Novell directory, then GroupWise 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.

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

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).
Message sent from native Exchange user to GroupWise user. Two possibilities: The GroupWise 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 GroupWise, where it is delivered to the appropriate mail file. In the second case, the message is still routed to GroupWise via the Send Connector, but GroupWise will be able to deliver it only if the appropriate mail file exists.

Email coexistence before and after CMG

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., vs. The CMG 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 CMG Mail Connector integrates into a single-namespace coexistence between GroupWise and Exchange. Round-robin traffic distribution can be used for load balancing and redundancy among multiple CMG servers.

SMTP mail routing within a single domain is accomplished using smart hosts in both directions, as shown in the illustration below. Exchange can be configured to route mail to a smart host (the Exchange Send Connector) if Exchange determines the recipient isn’t in its local Internet domain. Exchange reads the target­Address attribute in AD to route mail for such recipients to the Send Connector. Meanwhile, GroupWise is configured to do the same thing in reverse for a recipient whose local internet domain address is not defined in the Novell directory.

The step numbers here correspond to the numbers in the diagram above.

The step numbers correspond to the numbers in the diagram.

Any of CMG’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 records can be created, each with a different IP. See this Microsoft article for more information about DNS round robin.

NOTE: If coexisting with GroupWise 7: Note that inbound external (internet) mail delivered to GroupWise 7 cannot be routed to Exchange users, due to the way the proxy GWIA receives messages and the way messages are written into the production GWIA. To avoid this problem, you could direct inbound internet mail to Exchange instead.

Mail Connector deployment options

Several deployment options are summarized in separate sections below.

A single instance of CMG’s Mail Connector may connect through a single GroupWise server and a single Exchange server, or between multiple mail servers on either or both sides of the CMG service. Regardless of the number of servers or your preferred routing scheme, all mail servers on both sides must be defined in the CMG Mail Connector configuration file. Inbound and outbound servers may be specified to CMG by their DNS names, IP addresses, or MX record notations. For receipt of inbound messages (from the Internet), CMG distributes the traffic among multiple mail servers on either side in a round-robin array.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating