Edge Transport servers reject messages sent to valid recipients
Microsoft Exchange Server 2016 Edge Transport servers reject messages that are sent to valid internal recipients when the following conditions are true:
- Exchange Server 2016 Cumulative Update 1 (CU1) is installed on the server.
- Recipient validation is enabled on the server.
When an Edge Transport server rejects a message because of this problem, the sender receives a non-delivery report (NDR) that has the status code 5.1.10. Additionally, the sender receives the following error message:
Recipient not found by SMTP address lookup.
Note The recipient doesn't receive the message that was sent.
To work around this problem, do one of the following:
- Disable recipient validation on the affected Edge Transport servers by running the following command:
Set-RecipientFilterConfig -RecipientValidationEnabled $False
- Configure your firewall or external mail exchanger (MX) DNS record to send mail to an Edge Transport server that doesn't have Exchange 2016 CU1 installed. You might have to configure your firewall to let TCP port 25 connect to the new Internet-facing server.
- Configure your firewall or external MX DNS record to send mail to an Exchange 2016 Mailbox server. You might have to configure your firewall to let TCP port 25 to connect to the new Internet-facing server.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For important information about how to successfully deploy Exchange Server 2016, see the Release notes for Exchange 2016 topic on the TechNet website.
Article ID: 3152396 - Last Review: 03/31/2016 23:52:00 - Revision: 1.0
Exchange Server 2016 Enterprise Edition
- kbexpertiseinter kbprb kbsurveynew KB3152396