Exchange routing

Dovad
Dovad used Ask the Experts™
on
I have one exchange 2010 server.   I have a domain let's say it is ABC.com.   The requirement is to have the ability to relay email for a recipent to a specific smarthost.  

For example,  any mail received for John@abc.com needs to go to smarthost 10.1.1.1  any mail received for dirck@abc.com need to go to 10.1.1.2 any mail for skippy@abc.com needs to go to smarthost 10.1.1.3.
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
I don't think it is possible to create a "Send Connector" based on email address. You can create a "Send Connector" based email domain name (abc.com) then forward to smart host.

Author

Commented:
I know in Exchange 2010 you can setup shared address space.  

The document states "An organization may have to share the same SMTP address space between two or more different e-mail systems. For example, you may have to share the SMTP address space between Exchange and a third-party e-mail system, or between Exchange environments that are configured in different Active Directory forests. In these scenarios, users in each e-mail system have the same domain suffix as part of their e-mail addresses."

The key words I focus on is two or more.  I can get all mail for forward to one server if the email address is not my exchange server, I just can't get a third to work. or specifically send a specific email to a specific server.

Commented:
What are the smarthosts going to do with the email?  

You might try creating contacts for the forwarded email accounts (with different smtp suffixes) and use forwarding to take care of getting the email routed to the different smarthosts.  In this case, you would use three different send connectors that would send to the different smarthosts (authoritative for different domains for the contacts).
HTML5 and CSS3 Fundamentals

Build a website from the ground up by first learning the fundamentals of HTML5 and CSS3, the two popular programming languages used to present content online. HTML deals with fonts, colors, graphics, and hyperlinks, while CSS describes how HTML elements are to be displayed.

Author

Commented:
I have considered the option you are referring to, but I need to have the option so I can forward by recipient email to a production, QA and DEV server.
The routing is based on send connector which can be distinguished only by domain names.

The internal routing depends on the site and services topology. If the internet receiving site is Site 'A' and the email is for user at Site 'B' it will be transmitted using AD routing topology.

Author

Commented:
So is there an answer to sending based off of recipent instead of domain?
Commented:
The method I mentioned should work.  So if you have produser@yourdomain.com; QAUser@yourdomain.com and DEVUser@yourdomain.com, you'd setup forwarding addresses and contacts for each (such as produser@produser.com), setup a send connector which would be authoritative for each domain (such as *.produser.com) and set that connector to use the appropriate smarthost designated for the Prod, QA and Dev smarthosts.;  you could also use a Transport Rule on the Hub Transport page or the Org to rewrite your address if you don't want to create the forwarders.

The difficulty in your scenario is that your Exchange server is authoritative for @abc.com and Exchange is not designed to route mail to other mail servers (unless you have other Exchange servers in the org).  In that case, it aligns with Active Directory Sites and Services to move the mail.

Your other option is to write a transport agent - which would definitely meet your needs; however, writing one is a moderately complex software job.  See here:

http://blogs.technet.com/b/exchange/archive/2008/06/25/3405650.aspx

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial