0

I am in the process of deploying and configuring an on-premise exchange 2016 server. My inbound/receive connector is not working. When I telnet into my server on port 25 from a computer on an external network, I get:

220 Row3Exch.Slowservers.com Microsoft ESMTP MAIL Service ready at Mon, 25 Oct 2021 16:57:57 -0400

However, I am unable to receive emails. I ran the inbound connectivity analyzer to see if there was something that I am missing. The results say that port 25 is blocked, not listening, or producing the expected response. Looking at my DNS records and my telnet results I am a bit confused on what it can be. Here is a screenshot of the results

Jacob Harrand
  • 1
  • 1
  • Your external telnet test confirms that your server is reachable via port 25. It seems to me that your MX records are probably misconfigured. Right now they point to mx1.forwardemail.net and mx2.forwardemail.net. – joeqwerty Oct 25 '21 at 22:09
  • You probably looked at it when my coworker was trying a forwarding program to forward emails temporarily – Jacob Harrand Oct 27 '21 at 18:22

2 Answers2

0

I want to confirm if you can receive mails from internal?

According to the error messages, here's a solution provided in a blog to resolve the issue: restart Microsoft Exchange Frontend Transport service. Then you could check if this issue continues.

If above solution cannot work for you, here are some troubleshooting steps for your reference as well:

  1. Could you check the configurations of DNS records? enter image description here Then you could follow this guidance to check the Public DNS records: Check the Public DNS records

  2. In addition, is there a firewall in your environment? If so, you also need to check the firewall configuration.

Joy Zhang
  • 1,057
  • 1
  • 5
  • 5
0

I figured it out. It has nothing to do with the exchange setup. On our firewall I have my external address on a white-list for SMTP. Removing the white-list and allowing all traffic solved the problem.

Jacob Harrand
  • 1
  • 1
  • Glad that you have resolved this issue, you could mark the solution as best answer if someone encounters the same issue, they could find the solution quickly:) – Joy Zhang Oct 28 '21 at 08:02