NRPC Routing Issue

Hi all,

I have the following situation:

There are two Domino Domains: EXT and INT. The Domino servers in EXT accept mail from the internet and should route it to the inteded recipient’s home server in the INT domain via NRPC using the appropriate connection document. Instead of doing this, the EXT servers route mail always to one server ignoring the home server entries in the person documents.

As the server OUs are cross certified in both directions and the connection docs are identically prioritized, I have no clue to solve this.

Is there anything to consider regarding the server configuration docs?

Do I have to add certain domain documents for the INT domain in the EXT environment?

Or may it be something else?

Thanks in advance!

Subject: NRPC Routing Issue

Hi Lars,

I will do my best the information provided. I might be able to provide a better answer if you provided some more information like:

  1. Does the directory for the EXT domain contain the person documents for users in the INT domain? I assume so based on your description but want to make sure.

  2. Do you have an Adjacent domain doc set up between EXT and INT domains?

  3. Do you have a Local Domain Internet Smart Host configured in the Config doc for the EXT servers?

If you have a Local Domain Smart Host specified, remove it, since this may force the messages to route via SMTP rather than NRPC.

If you have an Adjacent domain doc in this situation, it should be removed. The connection documents will provide enough information on how to get from EXT to INT. You mentioned that the Connection documents are all prioritized the same way. As long as the servers in EXT know what server they are trying to route to and the costs are the same, the router should always pick the least cost route (which would be a direct route from a server in EXT to INT).

Please post any progress and the issue and I will try to help.

-Trey

Subject: RE: NRPC Routing Issue

Hi Trey,

thanks for the reply.

As for your questions, I’ve copied the person documents from the INT domain into the DD of the EXT domain. There is neither a smart host defined in any of the configuration documents nor there is an Adjacent Domain Document.

Meanwhile I came to the conclusion that the EXT servers are not able to deliver mail to the persons’ home servers since they are in different Domino Domains. In that case the router ignores the home server fields in the person docs. The server only looks for a connection document pointing at the EXT domain. If one is found, the mail is routed to the server listed in the connection document. All other connection documents are ignored, also.

The only solution that comes to my mind to set up this kind of “intelligent” mail routing is to create two Domino Organizations within one Domino Domain.

Subject: RE: NRPC Routing Issue

A more logical and correct way to deal with your requirement would be to use Directory Assistance. Create a directory assistance on your EXT domain with the INT address book acting as the secondary address book. Then create connection documents to the servers in the INT domain and your mails should get routed to the servers in the INT domain

Subject: NRPC Routing Issue - DA does not resolve this issue

Our internal tests seem to confirm that only the domain field is taken in account for routing mail to an external domain even if you use Directory Assistance.