Why Exchange 2010/2013/2016 is Not Receiving External Emails?

A common problem that administrators might encounter while installing and configuring MS Exchange Server is ‘Exchange is not receiving external emails’ in exchange 2010/2013/2016.

Scenario: In this situation, users are able to send and receive all the mails locally without any problem, but Exchange 2010 server is not receiving emails from the external email addresses and create issues while email is received by the server.

Possible causes: Forced reboot / abrupt shut down / Power down

Solution: In order to resolve this issue, the initial step that probably followed by all administrators is to check the problems occurring with e-mails, which are received. If you are also facing the same issue, check it by sending a test mail from any random external email address to your internal e-mail address. Now go to the EMC (Exchange Management Console), and select Toolbox from the right menu, and click twice on Message Tracking option. You will be able to view a new window, which will prompt you for a login. After completing this login process follow the below mentioned steps

  • Search for messages you’ve received from
  • Select user
  • Enter the address from where the test mail was generated
  • Click OK

After receiving the search results, now to get the details double click on the test message. In case the delivery report shows a failed message, follow the next step. Failed mail report looks like:

Exchange 2010/2013/2016 Not Receiving External Emails

 

Go to Start menu and choose services.msc and press enter:

Exchange 2010/2013/2016 Not Receiving External Emails

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

When you will be able to view the Services window, start looking for Microsoft Exchange Transport, and then right-click on this option and choose restart.

Exchange 2010/2013/2016 Not Receiving External Emails

After service is restarted repeat the external mail test process and this time it should be fine.

 Fix the Exchange 2013 Not Receiving External emails Issue

In case you are using Exchange 2013 server and the same problem occurs while receiving. In such case when you send the mails for testing, then the Microsoft remote connectivity tool will show few errors in incoming SMTP emails. In order to verify the problem you can simply check your server’s incoming SMTP emails status with the help of Microsoft’s remote connectivity analyzer. It will show an error at last, which indicates receiving external email issues on Exchange 2013.

To troubleshoot this problem follow the below mentioned steps:

  1. Firstly set the local DNS server in external DNS lookups.
  2. You can find it under ‘servers’ settings and then put the local DNS server IP for external DNS lookups.
  3. Now restart the MS Exchange transport and Front end transport service.
  4. Apart from this you can also modify the Host file, this might help you to fix this issue. To do this, open the host file of Exchange 2013 server and enter below mentioned host entries.

10.10.10.100         mailserver

10.10.10.100         mailserver.yourdomain.com

  1. Most to the times this modification in the host file resolves the problem and restarts the Exchange external transport services.

In case the above mentioned solution doesn’t work for you and you are still facing the same issue, then check (MSRCA) Microsoft remote connectivity analyzer, the transport logs, Firewall logs and Exchange server event viewer. It can provide you hint to fix exchange 2013 not receiving external emails issue.

Hopefully, the above mentioned solutions will help you to resolve the Exchange external email transportation issues in both Exchange 2010 and 2013 versions.

Edited:

If you’re facing external email receiving issue in Exchange Server 2016, I suggest you use Test-Mailflow cmdlets to diagnose the email status sent or delivered to mailbox. This cmdlets tests mail submission, transport, and delivery. It also verifies that each mailbox on server is able to send itself a test message. But this cmdlet is only available in on-premises Exchange Server 2016, it means you can’t use this on Exchange 2013 and 2016. Check here to know more about Test-Mailflow cmdlet.

Administrator’s Choice: Being an Exchange server administrator if you encounter corrupt database issue on Exchange server, try Exchange database recovery tool by Stellar . The software not only just recover database, but also lets you migrate them back to a new server or Office 365 account.

Stellar Repair for Exchange Video Tutorial:

 

18 Comments

  1. Dewis Chinoy September 22, 2015
    • admin September 22, 2015
      • John Balcer December 2, 2015
        • Admin December 11, 2015
  2. Digam Forrest October 20, 2015
    • admin October 26, 2015
  3. vijay panchal June 18, 2016
    • Admin June 20, 2016
  4. motiar August 24, 2016
    • Admin August 26, 2016
      • Brian October 13, 2016
        • Admin October 19, 2016
  5. Afsal August 22, 2017
  6. Sameer August 22, 2017
  7. Maria October 15, 2018
    • Admin October 15, 2018

Leave a Reply

Your email address will not be published. Required fields are marked *