Some emails are not received from external domains

Hello community,

Since I migrated from Exchange 2010 to Exchange 2013. I noticed that some emails from external domains are not received. Users do not receive NDR.

Tried to disable all agents and nothing works.

Any idea?

Cheers
Steven MatzAsked:
Who is Participating?
 
AlanConsultantCommented:
Hi Steven,

This seems odd.

If a new users consistently receive the emails, but migrated users do not, that would seem to imply there was a configuration issue during the migration - an Exchange issue.

However, if the emails are not even getting to the Exchange server (nothing at all showing in the Exchange Message Tracking Logs), then that would lead us to think it cannot be an Exchange configuration issue.

Can you examine firewall logs, and see the emails (that fail) coming in there?

What is your full (email) setup?


In terms of the tests, please start by running:

Internet Email Tests - Inbound SMTP Email

When it asks for the address to send to, please use one that is not receiving the external emails (a migrated account).

Please post the results of that test back here (expand the results when it is done), and whether the user receives that email (probably not from what you said above, but you never know!)


Thanks,

Alan.
1
 
Pushpakumara MahagamageVPCommented:
Have you test with MS remote connectivity analyzer.  What is the out come.  

https://testconnectivity.microsoft.com/
0
 
AlanConsultantCommented:
Hi Steven,

Given the lack of NDRs, what was it that alerted you to this?  I am thinking that you may be able to use that catalyst to track what is happening, back to the source of the issue.

Do your firewall logs show incoming connections from the correspondent?

What do your Message Tracking Logs show?

Use this form of PowerShell command (Exchange Management Shell) to get those:

Get-MessageTrackingLog -Resultsize "Unlimited" -Start "10/28/2017 09:46:01" -End "10/28/2017 09:48:59" -Sender "username1@example.com" -Recipient "username2@example.com" | Export-CSV C:\Temp\ZZ_MessageTrackingLog.csv -NoTypeInformation

Open in new window


Change the start and end dates / times to narrow it down (reduce the data to check.  You can omit the sender or recipient if you aren't sure, and change the C:\Temp\ to whatever suits.

Open the file in Excel (say).

Thanks,

Alan.
0
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

 
Steven MatzAuthor Commented:
Hi,


The strange thing comes that if the recipient is a new user,it works. He received the email but migrated users do not receive email from some external domains.


@Pushpakumara Mahagamage: Which test do I need to perform?

@ Alan: I noticed because some external users told us. Message Tracking shows no results. It is not arriving to Exchange but if i created a new user, he receives the email.

Cheers
0
 
Md. MojahidCommented:
Hi,

As you currently have issues with incoming email, please check the following:

1) Your MX records are configured to point to the public IP of Exchange

2) Check that you can connect using telnet and send an email through each MX record from the internet

3) Ensure that your NAT rule and port forward is correct

4) Check that the default front end receive connector has anonymous authentication enabled and that it's set to accept connections from all public IPs i.e. default settings of 0.0.0.0 to 255.255.255.255

5) Test sending an email using telnet internally onto the internal IP of the server

6) Check that the receive connector is set to listen on the correct IP in cases where Exchange has multiple IPs

7) Check the NDR sent back to the sender

8) If no NDR, enable verbose logging on your receive connectors and run another telnet test

Let me know how it goes.

Thanks.
0
 
Steven MatzAuthor Commented:
Thanks for all the response. It was blocked in the smarthost
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.