I'm stumped. I am doing a 2003 to 2010 migration between two forests. There will be a period of co-existence between the 2, so the need for the shared namespace. I have SMTP connectors setup at both 2003 and 1010 orgs. I've configured all accepted domains to not be authorative. 2010 -> 2003 mail flows fine over the connector using the share name space. Don't see any issue on this side. 2003 ->2010 mail goes over the connector for names dedicated to 2010, but not for shared ones. I get an NDR back generated from the 2003 server. I thought I had an understanding how this works. Mail comes from internet to 2003 right now. So it can not be authoritative for any shared domains, which it's not. I have the domains all specified in the connector properly as well. I'm hoping I'm missing something obvious? Very frustrating. Again the connector from 2003 -> 2010 works fine when sending emails to domains dedicated to 2010, so it seems at a base level the connector is working. Thanks in advance.

Hi, The NRD is coming for mail which are from internet & the mailbox is on exchange 2010, since as I remember the internet mail flow should be from 2010 to 2003Ripu Daman Mina | MCSE 2003 & MCSA Messaging

Hi, The NRD is coming for mail which are from internet & the mailbox is on exchange 2010, since as I remember the internet mail flow should be from 2010 to 2003 Ripu Daman Mina | MCSE 2003 & MCSA Messaging Hello. Actually for testing I'm and sending from between accounts located directly on each server. Sending directly from 2003 to an account on 2010 causes a NDR to be generated from from the 2003 box. For some reason it doesn't appear to recognize the connector for the shared domain. That said, is there actually a requirement that mail flow from the internet has to hit 2010 first?

Always post the NDR. What you're trying to do can be made to work, but it's often less troublesome, especially if you're going to have intermediate-to-long-term coexistence, to use two separate e-mail domains and a directory synchronization solution like IIFP. Check your recipient policy to ensure that your Exchange 2003 server doesn't think it's authoritative for the e-mail domain in question. -- Ed Crowley MVP "There are seldom good technological solutions to behavioral problems." . "Jeff061" wrote in message news:0812d5f7-08d9-480c-bdf8-5ffcbce7caad... I'm stumped. I am doing a 2003 to 2010 migration between two forests. There will be a period of co-existence between the 2, so the need for the shared namespace. I have SMTP connectors setup at both 2003 and 1010 orgs. I've configured all accepted domains to not be authorative. 2010 -> 2003 mail flows fine over the connector using the share name space. Don't see any issue on this side. 2003 ->2010 mail goes over the connector for names dedicated to 2010, but not for shared ones. I get an NDR back generated from the 2003 server. I thought I had an understanding how this works. Mail comes from internet to 2003 right now. So it can not be authoritative for any shared domains, which it's not. I have the domains all specified in the connector properly as well. I'm hoping I'm missing something obvious? Very frustrating. Again the connector from 2003 -> 2010 works fine when sending emails to domains dedicated to 2010, so it seems at a base level the connector is working. Thanks in advance. Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Politics make purchasing and configuring a new domain difficult. In any case this is short term, hopefully less than a week. I've checked the recipient policy what feels like dozens of times(and the address space on the connector as well). Exchange Organization is responsobile for all email to this address is unchecked. Here's the NDR, not much to it, didn't cross my mind it would help beyond my initial description. Your message did not reach some or all of the intended recipients. Subject: test email Sent: 7/20/2010 7:54 PM The following recipient(s) could not be reached: 2010User@shareddomain.com on 7/20/2010 7:54 PM The e-mail account does not exist at the organization this message was sent to. Check the e-mail address, or contact the recipient directly to find out the correct address. <2003Exchangeserver.mail.com #5.1.1>

In the Exchange 2003 organization, have you ensured that "Recipient Filtering" is configured properly? How about "Forward all mail with unresolved recipients to host "? http://technet.microsoft.com/en-us/library/aa997316(EXCHG.65).aspx -- Ed Crowley MVP "There are seldom good technological solutions to behavioral problems." . "Jeff061" wrote in message news:a7e0a128-3b51-4f18-8b5c-5b3536571f6d... Politics make purchasing and configuring a new domain difficult. In any case this is short term, hopefully less than a week. I've checked the recipient policy what feels like dozens of times(and the address space on the connector as well). Exchange Organization is responsobile for all email to this address is unchecked. Here's the NDR, not much to it, didn't cross my mind it would help beyond my initial description. Your message did not reach some or all of the intended recipients. Subject: test email Sent: 7/20/2010 7:54 PM The following recipient(s) could not be reached: 2010User@shareddomain.com on 7/20/2010 7:54 PM The e-mail account does not exist at the organization this message was sent to. Check the e-mail address, or contact the recipient directly to find out the correct address. <2003Exchangeserver.mail.com #5.1.1> Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

What am I looking for in recipient filtering? Nothing is configured there, no recipients listed and not set to filter names not in the directory. "Forward all mail with unresolved recipients to host" is my last resort. There are other unrelated SMTP connectors that are in use and I believe this would take priority over them, correct? If i can't figure out the cause of this issue I may just have to recreate all the connectors on the 2010 side and enable that setting. I should add this is not my environment, so I am trying to be as unobtrusive as possible. Thanks for the Help Ed, appreciated.

Comments inline below. -- Ed Crowley MVP "There are seldom good technological solutions to behavioral problems." . "Jeff061" wrote in message news:5ce218e0-0501-4c61-b9c5-d9679b4cb338... What am I looking for in recipient filtering? Nothing is configured there, no recipients listed and not set to filter names not in the directory. >>> You're looking for nothing, so that's okay. "Forward all mail with unresolved recipients to host" is my last resort. There are other unrelated SMTP connectors that are in use and I believe this would take priority over them, correct? If i can't figure out the cause of this issue I may just have to recreate all the connectors on the 2010 side and enable that setting. >>> Fair enough. Do you have an SMTP Connector with your domain as the address space and the Exchange 2010 server as a smart host? I should add this is not my environment, so I am trying to be as unobtrusive as possible. Thanks for the Help Ed, appreciated. Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Yes, I have a SMTP Connector with the shared domain listed as an address space and Exchange 2010 listed as the smart host, selected proper bridgehead as well. This connector works for domains dedicated to 2010(not being shared), but not with the shared ones. Configuring the connector and unchecking the authorative setting on the recipient policy was all that was needed I had thought.

I'm with you. All I can think of at this point is to restart the Exchange 2003 transport service. -- Ed Crowley MVP "There are seldom good technological solutions to behavioral problems." . "Jeff061" wrote in message news:30b4b219-6f74-477c-ac2a-9cc624c93a21... Yes, I have a SMTP Connector with the shared domain listed as an address space and Exchange 2010 listed as the smart host, selected proper bridgehead as well. This connector works for domains dedicated to 2010(not being shared), but not with the shared ones. Configuring the connector and unchecking the authorative setting on the recipient policy was all that was needed I had thought. Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

For those wondering. I ended up going the forward all unknown recipients to the 2010 server route. Worked like a charm and all recreated connectors worked as desired with no problems. No idea what the issue was, which bothers me some. I have 2 more Exchange orgs I'll need to configure as part of this consolidation. Though they are much smaller than this one.

Hi, Did you follow the KB321721 to implement the settings for the Exchange 2003? http://support.microsoft.com/kb/321721 You need to restart Routing Engine and Transport Protocol service. Thanks Allen

Hi, Did you follow the KB321721 to implement the settings for the Exchange 2003? http://support.microsoft.com/kb/321721 You need to restart Routing Engine and Transport Protocol service. Thanks Allen Very well may have been something as silly as that. As painful as it is to type, there would have been a lot of red tape to even restart those two services. Other orgs are smaller and more simple though, I'll verify this there.