Mailflow problems with Exchange 2003 & 2010 Coexistence
Posted on 2010-09-22
I recenlty introduced a new Exchange 2010 server into my existing exchange 2003 environment. My only issue is when sending mail from a mailbox on the 2003 server to a test mailbox on the 2010 server. Messages sent in any other direction are working properly.
I inherited a single exchange 2003 server environement with an Ironport appliance facing the public side for mail relay and antispam/antivirus.
For some reason the messages being sent from the 2003 mailbox to the 2010 mailbox are getting hung up in the routing group connector queue (automatically created when 2010 was installed). The 2003 mailbox will receive a delivery status notification delay with a 4.4.7 message from my exchange 2003 server. I've checked the mail logs on my Ironport and found that the messages are actually being sent to the Ironport instead of directly to my exchange 2010 server. I believe this is because my exchange 2003 server is sending the message out on the default SMTP virtual server after it sees that the mailbox is not local to the 2003 server. The default SMTP virtual server is set to forward to my Ironport. Is there anyway to get around this? I only have 1 nic/IP setup on the exchange 2003 server now, so I can't setup a second SMTP virtual server.
Exchange 2003 is running on windows server 2003 sp2
Exchange 2010 (rollup 4) is running on windows server 2008 sp2
My AD forest is at a 2003 functional level, but the resource domain that the exchange servers are in is windows server 2008 enterprise sp2 w/2 DC's that are both Global Catalog servers.
Any help would be greatly appreciated.