Exchange On Prem shared smtp domain loop

Stefano Colombo 221 Reputation points
2024-07-12T14:35:39.34+00:00

We have 2 AD domains with 2 exchange 2016 organization which shares the domain.com smtp domain, we're migrating from domainA to domainB.

We set up the 2 exchange domains to share the domain.com by adding it as accepted domain on both the organization as "internal relay".

The we configured the send connector for the shared domain to forward the "unkown email" to the other Org.

To cope with the unknown recipient issue, which would create a loop, we followed the advice from this article https://ibrahimnore.wordpress.com/2012/09/10/configuring-smtp-namespace-sharing-between-two-exchange-forests-part-3/ creating the transport rules on each organization.
All seems to be running correctly, but we noticed that:

  • the user is not getting any NDR for non-existant recipient
  • In the server queue "submission" we noticed emails for "local loop" that should not exist because of the transport rules

can anyone help us on this ?

thanks

Exchange Server
Exchange Server
A family of Microsoft client/server messaging and collaboration software.
1,335 questions
Exchange Server Management
Exchange Server Management
Exchange Server: A family of Microsoft client/server messaging and collaboration software.Management: The act or process of organizing, handling, directing or controlling something.
7,662 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Jake Zhang-MSFT 6,385 Reputation points Microsoft Vendor
    2024-07-15T03:02:39.48+00:00

    Hi @Stefano Colombo,

    Welcome to the Microsoft Q&A platform!

    Based on your description, it sounds like you have done a lot of the setup correctly, but you are running into some issues with non-delivery reports (NDRs) and local loop errors.

    After my research, I suggest that you can follow the steps below to troubleshoot:

    1. NDRs for non-existent recipients:
    • Make sure the transport rules you created are configured correctly to handle messages for non-existent recipients. This may involve setting up custom NDRs or making sure the rules cover all possible scenarios.
    • Double-check the internal relay configuration on both Exchange organizations to confirm that they are set up correctly.
    • Verify that all connectors and transport rules are scoped and ordered correctly to avoid conflicting rules or configurations that may suppress NDRs.
    1. Local loop errors:
    • Transport rules: Review the transport rules for both organizations to ensure that they explicitly prevent email from looping back. Check the conditions and actions to ensure that they are defined correctly.
    • Accepted domains: Confirm that the accepted domain is still configured as "internal relay" rather than "authoritative". If the organization is authoritative for a domain, unknown recipients will not be forwarded, which may cause loops.
    • Connectors: Make sure both the Send connector and the Receive connector are configured correctly. The Send connector should point to the correct destination, and both organizations should know where to route email.
    • MX records: Confirm that the MX records in DNS are accurate and properly directing traffic to the correct Exchange organization without confusion or misrouting.
    • Mail flow logs: Check the mail flow logs for both organizations to see where the loop is occurring. This will help determine if the problem is with the transport rules, connector settings, or other configuration.

    Please feel free to contact me if you have any queries.

    Best,

    Jake Zhang


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.