1. Domino to Exchange. You will create a new Foreign Domain, called Exchange, and use Dir Sync to import the Exchange mailbox addresses into the Domino Address Book. They will appear in the Domino Address Book under the new Domain Exchange, with an internal Domino user name of “/Exchange” , and a forwarding address of “alias@exchange.contuso.com@exchange”. Then when someone emails that address from Domino the email is sent to the Exchange Foreign Domain, which you created, and the “Exchange” part is stripped off as the email is routed through the connector to Exchange, leaving the normal SMTP address to match up to the Exchange mailbox.

2. Exchange to Domino. Setup the Transporter Suite Directory Connector to stamp the Domino addresses in Exchange with alias@notes.contuso.com. Then in Exchange you have a Send Connector with that Address Space to route to Domino. Domino is set to receive mail for that address space in the Global Domain document.

The Microsoft Transporter document covers this is good detail.

I have further customised the Transporter TBL files to use firstname.lastname@exchange.contuso.com as well, as it is more clear when emails are being addressed by users. I will post the configuration details shortly.

Thanks for this post.it is really awesome.

I will appreciate if you can provide the complete mail routing from domino to exchange and vice versa using sub domain architecture.
for ex. when a client sends a mail from lotus client to exchange user it will check the domain part of the email address and will check the foreign SMTP domain document for the virtual domain of the user and will redirect the mails to the Exchange server which is listed in the connection document.

please provide the detailed step from bit the ends.

This is the known issue surrounding changes to repeating meetings between Domino and Exchange. When repeating meetings are modified using SMTP mail between Domino and Exchange, there is are significant problems associated with these changes not being properly reflected on the other platform. this is due to the fact when Notes clients see any form of SMTP address, they perform iCal and MIME Conversions at the workstation level. With differing versions of workstation client implementations within a signal company you get differing results.

Additionally when messages are sent between the platforms as well as to external entities, these internal subdomains are also sent to the external people. As a direct result when the external entity performs a reply to all, they receive non delivery failures for the people listed with the sub domain values. They only way to circumvent this is to establish MX Records for the specific sub domains on the dirty side of the firewall.

Additionally you have no solution for work-flow enabled messages generated from applications. More often than not in complex Domino infrastructures, you will encounter applications that send programmatic objects to users that were on Notes. When the server or the user sends these, the workstation changes the message to mime immediately, thereby removing and code that was intended to be sent to the user.

I would suggest that you take these into consideration when considering any Enterprise level migration or you will leave the customer with a very poor and half thought coexistence solution.

Thank you.

@notes.cuntaso.com
@exchange.cuntaso.com

how to achieve a solution with only one namespace at both the ends. i.e @cuntaso.com