When a Lotus Notes user, who has not been migrated to Exchange, sends a meeting invite to a Notes user, who has already been migrated to Exchange, recipient receives a bounced NDR in Outlook Client stating error in resolving recipient address, even when recipient's correct Forwarding Address has already been populated in Domino Directory.
Coexistence Manager for Notes (CMN) Mail Connector functions only as a passive SMTP interface, so emails are simply passing through CMN with no change in delivery routes & no conversion of user email addresses, which means that even with or without CMN in place, proper mail routing should still need to get established between Domino and Exchange as a first baseline.
Since CMN Mail Connector possesses neither mail delivery routing table nor mapping / translation table for user email addresses, it is just an extra hop between Domino and Exchange, so all messages which are sent out from Domino environment must contain email address format which Exchange environment can resolve for its recipients.
For this email address "华文名/CONSOTOB@contoso.com@contosobex.contoso.com", it is in "mixed up" format which Exchange is unable to understand, which is clearly obvious from the bounced NDR generated by Domino that this recipient has somehow been interpreted to become 0xHexNumber/CONSOTOB@contoso.com. Hence this recipient format will need to be presented in standard SMTP address at its origin by Domino, because CMN will not intervene to convert it to something valid for Exchange.
Domino might happen to use "Alternate Name" field with Chinese characters, instead of using "Forwarding Address" field with proper SMTP address, for redirecting messages, when Lotus Notes Client User is automatically using his old recent contacts cache information of the recipient when sending a meeting notice.
A Domino Policy can be applied to push down to Lotus Notes Client to close its function of adding recent contacts, then subsequently user should be notified to delete all his existing recent contacts.
