Need a second SMTP Connector Help

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?
Network_PadawanAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

tigermattCommented:
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

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Network_PadawanAuthor Commented:
Thanks for that answer. It has cleared up alot about exchange send connectors. Awesome thankyou I appreciate it.

Regards
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.