The following will help you understand how the Notes and GroupWise connector works using X.400, synchronizes contacts and addresses free/busy.
Note that the use of the MTS-IN and MTS-OUT always means you are using X.400 when addressing Exchange 2003 and 2000. In the case of using the Notes or GroupWise connectors, contacts are again created in Exchange representing the Notes or GroupWise user. However the contacts target address is that of Notes or GroupWise type formatting as opposed to SMTP. The primary address which would be shared on all contacts and Mailboxes in the Exchange environment would be that of the acquiring corporation known as Corp1.com. In addition the contacts would have the original SMTP address of their respective former corporate domain names such as Corp2.com and Corp3.com. Corp1.com Exchange servers would have the respective MX records of Corp2.com and Corp3.com changed to point to the SMTP internet Gateways of Corp1.com. A recipient policy could be configured to stamp all of Corp2.com and Corp3.com contacts in Corp1.com with their former SMTP Corp2.com or Corp3.com SMTP addresses in addition to the new someone@Corp1.com.
Inbound mail from the Internet to Corp2.com or Corp3.com
If a message was received from the Internet for Corp2. Com or Corp3.com addresses the repointing of the external MX records would now have directed the message to Crop1.com SMTP gateway. Upon receiving the message the Corp2.com or Corp3.com would be resolved to one of the two corporations contacts via the old address. Once resolved the Exchange would look at the target address of the contacts and interpret that this message must be bond for either the Notes or GroupWise connector. It would then be translated by way of the connector into either a format compatible for Notes or GroupWise respectively and forwarded on from the attached respective Notes or GroupWise Bridgehead or Gateway if you would be way of the internal Notes or GroupWise routing mechanisims. See diagram for more details.
Outbound mail to the Internet from Corp2.com or Corp3.com
Outbound mail to the Internet having started from the Notes or GroupWise messaging environment would see their respective internet gateways targeted at the Exchange servers. Moe specifically any mail destined for the internet would be routed to the Exchange server specifically hosting either the Notes or GroupWise connector. Upon arrival it would be translated into a format understood by Exchange where it would then be routed on via SMTP. The message would be sent out with the primary SMTP address of the associated contact which represented the original Notes or GroupWise user as seen in the Exchange 2003 / Active Directory environment which hosted the Internet Gateway.
Connector for Lotus Notes Architecture
Addresses Mail Routing and Directory Synchronization
http://www.microsoft.com/technet/prodtechnol/exchange/Guides/E2k3TechRef/106aff2e-d966-4e3c-93d0-c6ccfb57001e.mspx?mfr=true
Directory Synchronization for Lotus Notes with Exchange 2003
The following figure depicts the directory connection between Exchange Server 2003 and Lotus Domino. As mentioned in the table above, the Lsdxa.exe process is responsible for controlling the actual directory synchronization processes Dxamex.dll and Dxanotes.dll. Lsdxa.exe is started automatically when the Microsoft Exchange Connector for Lotus Notes service starts.
Connector for Lotus Notes creates mail-enabled contacts in Active Directory for recipients in the Lotus Notes messaging system. The legacyExchangeDN address (that is, the X.500 address of the Exchange user in Exchange 5.5 format) matches in its first part the legacyExchangeDN of the connector. The first part is that portion of the X.500 address that identifies the connector’s administrative group (that is, /O=<name of organization>/OU=<name of administrative group>).
Directory synchronization between Lotus Domino and Exchange Server 2003
Connector for Novell GroupWise Architecture
Addresses Mail Routing and Directory Synchronization
GroupWise Directory Synchronization with Exchange 2003
Directory synchronization with Novell GroupWise follows a pattern similar to directory synchronization with Lotus Notes. The Lsdxa.exe process is responsible for controlling the actual directory synchronization processes. However, instead of Dxanotes.dll, the LSDXA process uses Dxagwise.dll (that is, the Novell GroupWise DX Agent) for directory synchronization with Novell GroupWise. Dxagwise.dll communicates with Novell GroupWise by means of Novell GroupWise API Gateway, the Exchange Router for Novell GroupWise service, and GroupWise administrator messages (Msg-Type= Admin).
Connector for Novell GroupWise creates mail-enabled contacts in Active Directory for recipients in the Novell GroupWise messaging system. The legacyExchangeDN address (that is, the X.500 address of the Exchange user in Exchange 5.5 format) matches in its first part the legacyExchangeDN of the connector. The first part is that portion of the X.500 address that identifies the connector’s administrative group (that is, /O=<name of organization>/OU=<name of administrative group>).
Connector for Novell GroupWise performs the following steps to synchronize directories with Novell GroupWise:
1. | Dxamex.dll communicates with Active Directory through ADSI to extract the recipient information from the export containers specified in the connector configuration. |
2. | Dxamex.dll maps the recipient attributes as defined in Amap.tbl and Mapmex.tbl and places the results in the form of a temporary file named Dxagwise.txt in message interchange format (MIF) in the Program FilesExchsrvrConndataTogwise directory. The following is an example of a Dxagwise.txt: |
Calendar Connector Architecture for Notes and GroupWise
Addresses Free busy
Calendar Connector supports synchronization of free/busy information between Exchange Server 2003 and Lotus Notes or Novell GroupWise, so that users in these messaging systems can query each other’s free/busy information when they create meeting requests.
