Have you tried adding the IP address of the 2003 server as an allowed relay host on the hub transport servers?
From: Michael B. Smith [mailto:[EMAIL PROTECTED] Sent: 08 February 2008 23:30 To: MS-Exchange Admin Issues Subject: RE: Exchange 2003/2007 email routing problem. Excellent! Let us know what it takes/took... Regards, Michael B. Smith MCSE/Exchange MVP http://TheEssentialExchange.com From: Campbell, Rob [mailto:[EMAIL PROTECTED] Sent: Friday, February 08, 2008 4:26 PM To: MS-Exchange Admin Issues Subject: RE: Exchange 2003/2007 email routing problem. Right now I have it down to an authentication problem of some sort. I don't have it all sorted out yet, but I've got enough to convince myself I'm going to get it to work. ________________________________ From: Michael B. Smith [mailto:[EMAIL PROTECTED] Sent: Friday, February 08, 2008 3:23 PM To: MS-Exchange Admin Issues Subject: RE: Exchange 2003/2007 email routing problem. <sigh> I'm sorry. I'll take a look again tomorrow. I'm slammed today. Regards, Michael B. Smith MCSE/Exchange MVP http://TheEssentialExchange.com From: Campbell, Rob [mailto:[EMAIL PROTECTED] Sent: Friday, February 08, 2008 2:18 PM To: MS-Exchange Admin Issues Subject: RE: Exchange 2003/2007 email routing problem. Thanks, Michael. That appears to be the procedure to use 2007 Edge servers as SMTP relays if you don't have a Hub Transport server. I'd rather get it working through the Hub Transport server if I can. ________________________________ From: Michael B. Smith [mailto:[EMAIL PROTECTED] Sent: Thursday, February 07, 2008 1:41 PM To: MS-Exchange Admin Issues Subject: RE: Exchange 2003/2007 email routing problem. This is the official process: http://technet.microsoft.com/en-us/library/bb124011(EXCHG.80).aspx Regards, Michael B. Smith MCSE/Exchange MVP http://TheEssentialExchange.com 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. ************************************************************************ ************************** ************************************************************************ ************************** 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. ************************************************************************ ************************** This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the email by you is prohibited. ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja ~
