There is an implicit send connector created on the HT server to the Edge server when you create an edge subscription that is most likely overrriding your new send con.
On Tue, Apr 8, 2008 at 11:28 AM, Campbell, Rob <[EMAIL PROTECTED]> wrote: > > > > I have a situation where I need to send all outbound email from an Exchange > 2007 Hub Transport server to a third party MTA for examination and > processing (encryption) before it goes on to the internet. > > > > The current configuration is a HT server on the internal network, and a pair > of Edge servers in the DMZ.. > > > > I'd like to be able to have the HT send all outbound mail to this MTA and > then have it returned to the Hub Transport server from there, and then onto > the Edge servers for delivery. That eliminates the need for more firewall > rules, gives me better message tracking in Exchange, and hopefully reduces > the potential for mail loops. > > > > I can set up a new Send Connector with an address space of * and point it at > the third party MTA, and I can set up a new Receive Connector linked to the > existing Send Connector going to the Edge server for delivery. > > > > What I can't seem find a way to do is force the HT to use the Send Connector > going to the third party MTA before sending the returned mail to the Edge > servers. > > > > I can set a higher cost on the Edge send connector so that it will prefer to > use the third party MTA connector, but that's about it. > > > > There just doesn't seem to be any way to control routing to a particular > Send Connector except by address space. > > > > If I can't get this to work, it means I have to configure additional Receive > Connectors on the Edge servers, punch more holes in the firewall, get SSL > set up between the Edge server and that third party (Linux) box, and have to > switch to the third part MTA for message tracking of internet email. > > > > Anybody know a way to control routing to a Send Connector? > > > > > ************************************************************************************************** > Note: > The information contained in this message may be privileged and confidential > and > protected from disclosure. If the reader of this message is not the intended > recipient, or an employee or agent responsible for delivering this message > to > the intended recipient, you are hereby notified that any dissemination, > distribution or copying of this communication is strictly prohibited. If you > have received this communication in error, please notify us immediately by > replying to the message and deleting it from your computer. > ************************************************************************************************** > > > > ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja ~
