A new Exchange Server 2016 is introduced in the organization. The organization does have an Exchange 2010 running. After migrating the mailboxes to the new Exchange Server 2016, an issue was detected. The issue is that the email is not being delivered to the Exchange 2010 mailboxes. In this article, you will learn why Exchange 2016 internal mail flow is not working.
The organization does have Exchange Server 2010. A new Exchange Server 2016 is installed and configured in the organization. The first test mailboxes are being migrated. Also, new test mailboxes are directly made on the Exchange 2016 databases. Emails that are being sent from Exchange 2016 to Exchange 2010 mailboxes are not delivered.
Troubleshoot Exchange 2016 internal mail flow not working
Let’s send some emails between the Exchange Server mailboxes. The following results are showing:
- Email sent from Exchange 2010 to Exchange 2016 – working
- Email sent from Exchange 2016 to the external recipient – working
- Email sent from Exchange 2016 to the internal recipient – NOT working
It does not matter if the mailbox is migrated to Exchange 2016 or if it’s a newly created mailbox on the Exchange 2016 database. Both are having the same problem. Sending from Exchange 2016 mailbox to Exchange 2010 is not working. The email is not being delivered.
Let’s have a look at the queue on the Exchange Server 2016. Run Exchange Management Shell as administrator. Run the Get-Queue cmdlet.
Identity DeliveryType Status MessageCount Velocity RiskLevel OutboundIPPool NextHopDomain
-------- ------------ ------ ------------ -------- --------- -------------- -------------
EX02\3 SmtpRelayToMailboxDeliveryGroup Retry 25 0 Normal 0 site:eu-london; version:14
EX02\Submission Undefined Ready 0 0 Normal 0 Submission
The emails are stuck in the queue. The SmtpRelayToMailboxDeliveryGroup is showing that 25 emails are in the queue. Those are the test emails sent from Exchange 2016 to Exchange 2010 mailboxes.
Solution Exchange 2016 internal mail flow
The problem is that the receive connector on the Exchange 2010 is not correctly configured. Have a look at the Exchange 2010 receive connectors. You can open the receive connector from Exchange 2010 or Exchange 2016. It’s recommended to work from Exchange Server 2016.
Important: Get the IP address of the Exchange Server 2016. Run command prompt and run the command ipconfig. Write down the IP address.
Have a look at the default receive connector on the Exchange 2010. Click scoping on the left side and have a look at the IP Addresses. The default receive connector will look like the below image.
Have a look at all the other receive connectors. Open the receive connectors and click scoping. Look for the IP address of the Exchange Server 2016. In my example, a connector was configured for relaying email. The IP address of the Exchange Server 2016 was added to the list of IP addresses. Remove the Exchange 2016 IP address. Click Save. It’s also possible that an IP address range is added to the list, instead of a single IP address. Adjust the IP address range and make sure that the IP address of the Exchange Server 2016 is not on the list.
Restart the service Microsoft Exchange Transport on the Exchange Server 2010. The emails in the queue are being delivered.
How did this happen?
It’s possible, that the IP address was configured for a different machine. For example, a printer. The printer was physically removed from the office. The IP address was deleted from DHCP, but not from the Exchange 2010 receive connector. Before the new Exchange Server 2016 is installed, an IP address needs to be reserved. If an IP address is not registered or reserved, it can be taken. The administrator didn’t know that the IP address is configured in the receive connector.
In this article, you learned why Exchange 2016 internal mail flow is not working. Check the receive connectors on the Exchange Server 2010. Don’t forget to restart the Microsoft Exchange Transport service. Always check the receive connectors on the already installed Exchange Servers, before installing a new Exchange Server. Did you enjoy this article? If so, you may like the article Change Users UPN with Powershell. Don’t forget to follow us and share this article.