Link to home
Start Free TrialLog in
Avatar of itwarlord
itwarlord

asked on

Only receiving some email in Recently moved Exchange 2016

Exchange 2016 Environment, Server 2016.  Moved the server over the weekend and had some trouble with Email delivery.  It seems to be working except for some email from the outside get queued and never delivered.  I have not received an NDR yet.  250 2.6.0  Queued Mail for Delivery.

It truth the email is not in any queue on the Exchange 2016 server.  Email from GMail and other domain does go through.  Any help greatly appreciated.

Just for Clarity, I do have an Exchange 2010 server on site that is not participating in mail routing (or should not be)  There is nothing in the queues there either.

This was working fine at the old location for several years.  During the move, I had added a Public DNS server to the network card and that caused NO mail flow.  I fixed it, but I also noted that the fix did not stay fixed.  I had to go into the properties of the server and select "Custom Dns Lookup" and add the local AD server IP for DNS.  This has got the mail partially flowing.

I have read that ISP can effect email delivery with TLS settings but I have not seen the entire process to investigate if that is the cause here.
Bob
Avatar of Kimputer
Kimputer

Either read through all the log files (various transport logs), or use packet capturing to see if mail gets to you at all, gets accepted or rejected, see smtp error codes etc.
If it gets accepted but it's not in the mail box, read the logs why it's not getting inside the mailbox
Expanding Kimputer's comment, also use the SWAKS tool to manually connect to + send a message to your Exchange's IP, so you can see 100% of both sides of your SMTP conversation.

Way easier to debug this using SWAKS than any other way.
It occurs to me that the MX records may have not yet been fully propagated and some senders aren't getting the correct mail server address.  That is, if you had to change the mail server in this process.  Patience....
Suspend and retry the Q and check if there are any errors generated against those , try sending out emails to those from any external domain and see
Avatar of itwarlord

ASKER

I am having trouble finding the logs files.  I have gone into the receive connectors and enabled logging.  I ran a powershell command to get the path of the logs and they are not there!  Any idea why the logging would not start?  I have restarted the transport service.
There's a slight delay after enabling it. The delay continues till after really receiving real mails. So please send a few test mails from gmail, and after 5-10 minutes the logs should be there.
Then finally, start sending from the "problem" domain, because then you're finally a step further in solving this problem.
@david
I looked at SWAKS but it is a little out of my league.  I will try to get it going but it looks like I need to have Pearl Installed?  If you have more information I would certainly try..
@pradip
There is nothing in the queues to suspend.  email does go out to the problem domain.
@kimputer
I enabled it yesterday.  just sent email from GMail and it goes through.  still not log files.  I used the command Get-TransportService  and scrolled down to ReceiveProtocolLogPath.  Unfortunately it is not there.
I am looking at other log paths.
@fred
I think that is all done.  I used the telnet to try to send the message and it still says it is queued.
ASKER CERTIFIED SOLUTION
Avatar of Kimputer
Kimputer

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Ok, I think I found the right logs.  but it is not clear.  
2019-03-04T12:11:05.175Z,SERVERNAME\Default Frontend SERVERNAME,08D69F64CA94B0A7,12,127.0.0.1:25,127.0.0.1:61567,>,"250 2.6.0 <174d5186-f1dc-4953-b84a-37aedc7b71cb@SERVERNAME.DOMAIN-NAME.local> [InternalId=80766860001309, Hostname=SERVERNAME.DOMAIN-NAME.local] 1681 bytes in 0.102, 15.954 KB/sec Queued mail for delivery",
I found the log file and it says the same thing for email that actually goes through.  So that means that the server is getting the email, right?
I think it is working now.  Conducting more tests.