Not that easy.
I've got several other smtp connectors on that bridgehead that are going to involve re-configuring other appliances and servers to change their mail routing. To complicate it further, the HT server sits in a different network than the 2003 bridgehead (vlan/network segmentation project), so I can't just move the IP address. ________________________________ From: Kennedy, Jim [mailto:[EMAIL PROTECTED] Sent: Thursday, February 07, 2008 12:49 PM To: MS-Exchange Admin Issues Subject: RE: Exchange 2003/2007 email routing problem. Can you eliminate the 2003 bridgehead and have the remaining 2003 servers route through the hub? When I did ours there was no bridgehead, but as soon as I put up a 2007 hub the 2003 server instantly started routing via the hub on its own....I remember that very clearly because I was not expecting that and had to do a quick fix up on the outbound IP address mapping so the rDNS was valid..... From: Campbell, Rob [mailto:[EMAIL PROTECTED] Sent: Thursday, February 07, 2008 1:30 PM To: MS-Exchange Admin Issues Subject: Exchange 2003/2007 email routing problem. I'm in the process of upgrading our environment from Exchange 2003 to 2007. I have an immediate need to eliminate the email relays in the DMZ that are being used by Exchange 2003. I have an Exchange 2007 Hub Transport server in the site, and a pair of Edge Transport servers in the DMZ that I would like to use as the internet mail transport for the Exchange 2003 environment. Currently I have all inbound internet email going through the Edge and Hub servers and then being sent on the the Exchange 2003 bridgehead, and working fine. Outbound is more problematic. There is a Send connector defined for internet email on the Hub and Edge servers, but the Exchange 2003 bridgehead can't seem to use it. Any attempt to send outbound internet email from the 2003 bridgehead to the 2007 Hub Transport results in "Unable to relay.". I can get it to work by adding * as an accepted domain on the 2007 side, but that makes the Hub server an open relay. I can mitigate that by restricting the default receive connector to only accepting a connection from the 2003 bridgehead, but the edge synchronization propagates that setting the Edge servers, and they become open relays. I think I can get it to work by eliminating the edge subscriptions and manually configuring send and receive connectors on the Edge servers, but it seems like there ought to be a better way. Anyone have any expertise in this kind of configuration? ************************************************************************ ************************** 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. ************************************************************************ ************************** ************************************************************************************************** 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 ~
