Messages with Lotus Notes format addresses in "cc:" are not sent through/by the connector

We have an MS Exchange server and a Lotus Notes (Domino) server in the same domain. When mails are sent from Exchange to LN and vice versa, using the standard mail addressing the Exchange connector for Lotus Notes seems to work like a charm.
So, when a LN user sends a message to an Exchange user with other LN users addresses in the CC: field, then all the addressed users get the message correctly (whether the message passes the connector or not). BUT.. When the Exchange user whishes to ReplyToAll, then the messages for the LN-users that were in the cc:-field bounce (btw, exchange addresses are delivered correctly because they do not pass the connector, evidently). The cc: LN addresses (that appear in the received message as <username>/<originating mail domain>@<destination> are not or incorrectly converted by the connector.
What is causing this, and more important, how to solve it.

Thanks for your advice.

Who is Participating?
qwaleteeConnect With a Mentor Commented:
In the connector, do you have the namespace listed as @dom2? You should change it to *@*, so that all domains are routable through the connector. At that point, it should be willing to pass it off to Notes (which is in the dom2 domain, but should understand how to route through to dom1).
Did you have a look at the headers in the bounced emails? Was the addresses correct or truncated? It's a bug in the connector. Read more here:
That knowledgebase article is completely irrelevant. It only applies to the Notes side of the mail system, not the Exchange side, And I hope he doesn't still use 5.5!

The problem here PROBABLY isn't that the ocnnector gets confused when trying to deliver these messages. It is probably that the connector is mangling the addresses it creates when it inserts the original into Exchange for routing.  Here's what happens:

Notes has a message with some Exchange recipipents
It drops off a copy of the message, with a list of routing instructions relevant only to the Exchange recipients, in a place where the ocnnector can pick them up.
The connector retrieves the message.
****It then converts every address (sender, To, CC, BCC, current Exchange recipients) into Exchange-interpretable addresses. Finally, it creates an Exchange version of the message with all those addresses replacing those in the original message.
Connector drops off message in Exchange queues.
Exchaneg delivers message(s)

The **** part is ver important. If the addresses are not translated correctly, then Exchaneg can't use them.  In your case, it appears that it translated the routing instructions (Exchange addresses used to send the mesage, which is not the same as to/CC/BCC addresses), so the message got delievered. It also looks like the sender address got translated correctly, since the connector is able to deliver replies to that Notes user. However, all the other addresses are subjectto getting mangled here, and only Exchange addresses among them are OK.

One thing you shouyld look at. Open up the oriiginal message in an Exchange recpients mailbox (the message sent by the NOtes user, before it was rpelied to). Right click a "bad" address, and view its properties. You might post here all information contained there. I would also search ADUC for the address listed, and see if it matches any mail-enabled object, and if so, post details about that object (contact or account).
Easily manage email signatures in Office 365

Managing email signatures in Office 365 can be a challenging task if you don't have the right tool. CodeTwo Email Signatures for Office 365 will help you implement a unified email signature look, no matter what email client is used by users. Test it for free!

dirkvdoAuthor Commented:
Gwaletee, here are the results (masked for confidentiality) of the try :

The properties of name in the From field when a message arrives from LN :

Display name : <lastname><blank><firstname>/<dom1>@<dom1>@<dom2>
E-mail address : <lastname><blank><firstname>/<dom1>@<dom1>@<dom2>
E-mail Type : NOTES
Internet Format : Send using Outlook Rich Text Format.

When reply-ing, this user actually receives the mail.

The cc-field contains one or more addressees in with the following properties ;

Display name : <lastname><blank><firstname>/<dom1>@<dom1>
E-mail address : <lastname><blank><firstname>/<dom1>@<dom1>
E-mail Type : NOTES
Internet Format : Let outlook decide the best sending format.

As you notice, there are two differences. First, the second domain name isn't there in the cc-addresses, and secondly, the Internet format differs.

Any idea ?


dirkvdoAuthor Commented:

Thanks for the suggestion, I had one of my team members change the configuration, and do some testing, even with users, and it works like a charm. Strange though, that we had several 'Specialists' taking a look at the problem before, and none of them found the reason.

I gladly accept your solution and award you the points.

We still have other problems with the functioning of the connector itself, or with the setup of the communication : a mail from Exchange is sent to Lotus Notes, over the internet, and Lotus Notes sends notifications for these mails; and these notifications aren't picked up by the connector (in fact they are sent from the main LN server (at dom1) to a LN Server that is setup to be the liaison with the Exchange server and LN Connector (at dom2).

Greetings, and thanks again.
dirkvdoAuthor Commented:
Thanks again. Sincerely !!!
I'm not visualizing your new scenario. You may also want to open a new question in case other experts have insites, who may not be monitoring this thread any more.
All Courses

From novice to tech pro — start learning today.