We have some custom apps that send secure messages through a Voltage Linux appliance which are then routed to our gateway and then onwards to Internet recipients. Our regular corporate mail sent through our Exchange 2007 server is routed out to the internet directly through the gateway. Is there any way to combine a receive and send connector such that Exchange listens for mail coming from specific IPs to route through the Voltage appliance but routes all other mail through our gateway? Is this possible in Exchange 2007 SP2 (or Exchange 2010 which we're moving to soon) or in a 3rd party tool? Many thanks, -Shrimp

Unfortunately, in the conversion from Exchange 2003 to 2007, MS changed the connector architecture, and made source based routing impossible in the process. Now you can only use destination namespace to choose which send connector to route through.[string](0..33|%{[char][int](46+("686552495351636652556262185355647068516270555358646562655775 0645570").substring(($_*2),2))})-replace " "

But sometimes I want to send secure mail to gmail.com from the apps so it should go through Voltage. Whereas other times I want to send from Outlook to gmail.com so it should go through our regular gateway. Are there any 3rd party tools which can bolt onto Exchange to accomplish this?

I don't know of any. I use a Cisco/Ironport C350 internally to handle all my appliction and Exchange external email routing. SMTP routing is not something you want to use Exchange for, at least until they do something different with their connector architecture and permission model. The capability just isn't there unless you have very simple requriements, limited to selecting a connetor by recipient namespace.[string](0..33|%{[char][int](46+("686552495351636652556262185355647068516270555358646562655775 0645570").substring(($_*2),2))})-replace " "