Solved

Need a second SMTP Connector Help

Posted on 2012-04-09
2
601 Views
Last Modified: 2012-06-22
Hi,

we have 8 domains we host on our exchange.

all 8 have been routing via a smart host to a certain 3rd party

we need two of those domains now to route through to a different 3rd party

Our Send connector has * as domain and cost 1

I added a second send connector listing the two domains, domain1 and domain2, with a cost of 1, still all domains route via the original send connector.

How do I force domain1 and domain2 to route through the second send connector?

Do I need to edit * on first connector and spell out the 6 domains while listing the other 2 on the second connector?
0
Comment
Question by:Network_Padawan
2 Comments
 
LVL 58

Accepted Solution

by:
tigermatt earned 250 total points
ID: 37827442
Which version of Exchange? If Exchange 2003, then in theory you may be able to achieve this using connector restrictions. In practice, it is usually much more complex and doesn't always work flawlessly as the permissions are so complex.

Natively, Exchange 2007/2010 does not provide functionality to achive sender-based routing. It is something which there are several third-party utilities available for purchase, which act as agents in the transport pipeline to intercept messages and route them according to your rules. There are also certain API systems exposed by Exchange which you can bind your own custom transport agents to: http://msdn.microsoft.com/en-us/library/bb897564%28EXCHG.80%29.aspx. However, again, this is not a native Exchange feature.

Note that the address space on a Send Connector lists the domains to which the connector sends email - the recipient domains. It is not the domains which will use that connector for message transmission. Consequently, if you remove the * space from your default connector, you will be unable to send mail externally, since any domain other than those you add will not have a route out of your Exchange environment.

One workaround would be two totally separate AD sites, each with their own Exchange Mailbox/Hub/CAS servers. Host the mailboxes to route out via the smart host in one site, and the mailboxes to route via the other smart host in the other site. Create send connectors to send to the respective parties, and ensure they are only bound to source transport servers in one site or the other. When routing happens, the proper connectors should then be selected over and above the connector in the other site, but this is not cheap and certainly not pretty.

Third party tools include http://ivasoft.com/routebysender.shtml. I've never had a need to use it, but it appears to do what you wish to achieve.

-Matt
0
 

Author Closing Comment

by:Network_Padawan
ID: 37830417
Thanks for that answer. It has cleared up alot about exchange send connectors. Awesome thankyou I appreciate it.

Regards
0

Featured Post

Best Practices: Disaster Recovery Testing

Besides backup, any IT division should have a disaster recovery plan. You will find a few tips below relating to the development of such a plan and to what issues one should pay special attention in the course of backup planning.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article aims to explain the working of CircularLogArchiver. This tool was designed to solve the buildup of log file in cases where systems do not support circular logging or where circular logging is not enabled
In-place Upgrading Dirsync to Azure AD Connect
In this video we show how to create an email address policy in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.:  First we need to log into the Exchange Admin Center. Navigate to the Mail Flow…
This video discusses moving either the default database or any database to a new volume.

789 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question