none
Mailflow on Cross Forest migration

    Question

  • Hi all.  I am working on a cross forest (inter forest) migration project.  Basically I need to migrate all AD user and Exchange 2013 mailboxes from the old AD forest (old.com) to new AD forest (new.com) that is also running on Exchange 2013.  Both the old and new AD forest will be using the same SMTP name space.  This is what I've done:

    a) Created the accept domain in new Exchange forest (share.com)
    b) Created the shared SMTP name space (share.com) and set it as "Internal Relay"
    c) Created the Send and Receive Connector on both old and new Exchange environment
    d) Ran the Prepare-MoveRequest.ps1 PowerShell script and set the TargetDevlieryDomain to "new_domain.test"
    e) Ran the ADMT User Migration wizard to migrate the SIDHistory (I also excluded all msExch attributes, if I don't exclude them, it will corrupted the account created by the Prepare-MoveRequest PowerShell script)

    Checked both the user account attributes, the "TargetAddress" attribute on both of them is set to "xxx@new_domain.test"

    This is the result:

    1.       Email send from TEST (brand new user in new forest) to TEST2 (migrated account) is NOT working
    2.       Email send from  TEST2 (migrated account) to TEST (brand new user in new forest) is working
    3.       Email send between TEST (brand new user in new forest) and MYSELF (user in old domain) is working
    4.       Email from TEST2 (migrated account) to MYSELF (user in old domain) is working
    5.       Email from MYSELF (user in old forest) or external emails send to TEST2 (migrated account) IS NOT working. 
    6.       Email from external to TEST (new user in new forest) is working 

    So my problem is the migrated user account is not able to accept emails from any body.

     I am seeing this error on the email send from the TEST user in the new forest to this migrated user account (they both reside in the new forest).

    You aren't authorized to send to this recipient.<br>For more information about this issue see <a href="http://go.microsoft.com/fwlink/?LinkId=389365">DSN code 5.7.1 in Exchange Online</a>.

    Looks like the email is received by the new Exchange server in the new forest, then it got passed over to the old Exchange server in the old forest by using the Send Connector I've configured (there is only one Send Connector in the new Exchange forest, which will pass everything to the old Exchange server).  That seems little bit odd as the recipient is in the same Exchange forest, I don't expect it to send the email out to the old Exchange server 

    Then I am seeing this error from the returned email that send from my account (in the old Exchange forest) to this migrated user (in the new Exchange forest)

    Remote Server returned '554 5.4.6 Hop count exceeded - possible mail loop'

    Any suggestions?  Thanks you. 


    Thursday, May 5, 2016 3:40 PM

Answers

  • Hi.  Not sure why I got two different Microsoft accounts. Anyhow, after a bit of troubleshooting, it is not the  existing Send and Receive connectors that is causing the problem.  Looks like one of the Exchange server in the old Exchange forest is acting up.  Although I've created a brand new receive connector and tried to allow open relay on it, the PowerShell keep reporting the specific receive connector is not found.  I ended up removed this old Exchange server from the Smart Host list on the new Exchange forest, and email flow now working as expected.  Thank you for the input. 
    • Proposed as answer by Tinha9413 Tuesday, May 10, 2016 6:11 PM
    • Marked as answer by jim-xuModerator Monday, May 16, 2016 2:10 PM
    Tuesday, May 10, 2016 6:11 PM

All replies

  • Then I am getting this error while sending from old Exchange to migrated user in the new Exchange.


    TEST
    Your message wasn't delivered due to a permission or security issue. It may have been rejected by a moderator, the address may only accept email from certain senders, or another restriction may be preventing delivery.<o:p></o:p>

    The following organization rejected your message: OldExchange.old.domain.<o:p></o:p>

    Generating server: NewExchange.new.domain

    Remote Server returned '<OldExchange.old.domain #5.7.1 smtp;550 5.7.1 Unable to relay>'

    Thursday, May 5, 2016 4:16 PM
  • Hi Tinha, 

    Welcome to our forum.

    Please run the following command to make sure mailbox was migrated to new domain:

    Get-Mailbox <username> | FL *servername*

    For a test, please remove internal relay (share.com) to check if the issue persist. If not, please create a new user in old domain, then migrate it to new domain to have a try.

    Exchange cross domain migration could be referred to the following link:

    https://blogs.technet.microsoft.com/meamcs/2011/06/10/exchange-2010-cross-forest-migration-step-by-step-guide-part-i/ 

    Best Regard,

    Jim Xu

    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Jim Xu
    TechNet Community Support

    Friday, May 6, 2016 7:04 AM
    Moderator
  • Hi Tinha, 

    Is there any update for this thread?

    If the above suggestions are helpful to you, please mark it as answer so that someone who has similar issue could find this thread as soon as possible.

    Best Regard,

    Jim Xu

    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Jim Xu
    TechNet Community Support

    Monday, May 9, 2016 8:01 AM
    Moderator
  • Hi.  Not sure why I got two different Microsoft accounts. Anyhow, after a bit of troubleshooting, it is not the  existing Send and Receive connectors that is causing the problem.  Looks like one of the Exchange server in the old Exchange forest is acting up.  Although I've created a brand new receive connector and tried to allow open relay on it, the PowerShell keep reporting the specific receive connector is not found.  I ended up removed this old Exchange server from the Smart Host list on the new Exchange forest, and email flow now working as expected.  Thank you for the input. 
    • Proposed as answer by Tinha9413 Tuesday, May 10, 2016 6:11 PM
    • Marked as answer by jim-xuModerator Monday, May 16, 2016 2:10 PM
    Tuesday, May 10, 2016 6:11 PM
  • Hi Tinha, 

    Please mark it as answer instead of proposed so that someone who has similar issue could find this thread as soon as possible.
     
    Best Regard,

    Jim Xu

    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Jim Xu
    TechNet Community Support

    Tuesday, May 10, 2016 11:35 PM
    Moderator