Assume that there are multiple accepted domains configured in a Microsoft Exchange Server 2016 environment. When the default accepted domain isn't the primary SMTP address in the Default Policy email address policy, messages for the health mailboxes are stuck in the Shadow and Outbound SmarHostConnect queues.
Note This issue also occurs in Microsoft Exchange Server 2013, and you can follow the Workaround section to fix the issue for Exchange Server 2013.
This issue occurs because the managed availability probe for incoming messages uses the default accepted domain and the health mailboxes don't contain an SMTP address that uses this domain.
To fix this issue, install Cumulative Update 4 for Exchange Server 2016 or a later cumulative update for Exchange Server 2016.
To work around this issue in Exchange Server 2013, use one of the following methods:
Add the default accepted domain as a secondary SMTP address to the Default Policy email address policy.
For more information, see Edit an email address policy.
Change the default accepted domain to match the primary SMTP address in the Default Policy email address policy.
For more information, see Set-AcceptedDomain.
For more information about how to change email address policies, see Set-EmailAddressPolicy.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Learn about the terminology that Microsoft uses to describe software updates.