Discussion Locked

Custom Recipient Routing

0 helpful
8 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Using Exchange Server 5.5 SP3, with the following configuration:

Two sites, Boston and Wilmington
The two are connected by a site connector (with piggybacked Directory Services Connector)

I have a custom recipient configured on site Boston. For example, a custom recipient named "testuser" which forwards to SMTP:max@foo.com. I add an additional e-mail address to this recipient of SMTP:max@ourcompany.com.

When I send an e-mail from outside the company to max@ourcompany.com, the message comes in through the Boston Internet Mail Service. It then goes to the Boston MTA which inexplicably routes the message to the Wilmington MTA. From there, the Wilmington MTA routes the message (properly addressed to max@foo.com) to the WilmingtonInternet Mail Service.

This did not occur before the Wilmington site existed. It also does not occur if the message is sent to testuser from within the organization. In the latter case, the message is routed as one would expect: it goes from the Boston MTA directly to the Boston Internet Mail Service.

Any ideas would be extremely helpful.

8 replies

by cosmit

Look in GWART. It could be that the cost of sending SMTP traffic is set to a lower cost in Wilmington than Boston. (If Wilmington is set to a lower cost than Boston it would try that route first.)

by mweinstein

The GWART is correct. It shows both routes to the Internet, but the cost is lower via the Boston IMS. This makes sense, since any other message sent to the Internet from within the Boston site goes out through the Boston IMS.

by james_randy

Since your question is so old, you might as well just reload the latest versions of all software, and you'll have a new set of problems to deal with. Heck, update all your hardware and operating systems while you're at it. Have a real party.

This discussion is closed to new replies.