exchange 2019 send and receive mails

Question

Hi Team,

I want to configure exchange server 2019 to send and receive mails outside the domain.
Not sure where to begin, because I configured the public domain only with MX record.

When I log into owa with user account I get the following error message from outlook:

Subject: test 3
This message hasn't been delivered yet. Delivery will continue to be attempted.
The server will keep trying to deliver this message for the next 1 days, 19 hours and 53 minutes. You'll be notified if the message can't be delivered by that time.

Diagnostic information for administrators:
Generating server: hostname.contoso.com
Receiving server: outlook.com (104.47.59.161)
test1234outlook.com
Server at outlook.com (104.47.59.161) returned '400 4.4.7 Message delayed'
11-6-2021 15:56:14 - Server at outlook.com (104.47.59.161) returned '451 4.4.397 Error communicating with target host. -> 421 4.2.1 Unable to connect -> SocketConnectionRefused: Socket error code 10061'
Original message headers:
Received: from hostname.contoso.com (10.209.30.31) by
hostname.contoso.com (10.209.30.31) with Microsoft SMTP Server
(version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id
15.2.221.12; Fri, 11 Jun 2021 13:59:42 +0200
Received: from hostname.contoso.com ([::1]) by
hostname.contoso.com ([::1]) with mapi id 15.02.0221.012; Fri, 11 Jun
2021 13:59:41 +0200

Answer 1

Hi anonymous user,

According to your error message above, looks like you have encountered issues when sending emails to your Outlook.com email account, right?
Can you successfully send emails out to other external email accounts?
Are you able to receive inbound emails properly?

11-6-2021 15:56:14 - Server at outlook.com (104.47.59.161) returned '451 4.4.397 Error communicating with target host. -> 421 4.2.1 Unable to connect -> SocketConnectionRefused: Socket error code 10061'

I did some research about this specific error, most of the related information says the 25 port is the key of this issue. So, please try to check the firewall and make sure that all ports required by Exchange are opened, especially 25. For more information, please check: Network ports required for mail flow (no Edge Transport servers).

Besides, you could also try the Microsoft Remote Connectivity Analyzer tool to check the process of your Outbound SMTP Email and Inbound SMTP Email(if necessary).

Hope this can be useful.

---

If an Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 2

Hi anonymous user,

Thanks for your reply. Sorry to hear that the issue still continues.

I have on the DC and exchange server all required ports open. Public dns and mx record is configured.

In order to make sure that you have made all the necessary settings configured properly, it is suggested for you to check all your settings and compare with the steps in this document: Configure mail flow and client access on Exchange servers to see if there is any difference.

Besides, according to my experience, if you have enabled mail gateways in your environment, issues like this might indeed occur as well. So, please try to check your mail gateways and turn them off to test (if there is indeed exist).

Besides, you could also try the Microsoft Remote Connectivity Analyzer tool to check the process of your Outbound SMTP Email and Inbound SMTP Email(if necessary).

Have ever tried the Microsoft Remote Connectivity Analyzer tool I mentioned before? If not, it is suggested for you to give it a shot and see if we could get more diagnostic information about your issue for further research.

If you have any updates, please feel to post back.

---

If an Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.