421.4.4.2 connection dropped exchange

Camilo Quintero 20 Reputation points
2023-09-21T17:13:52.3433333+00:00
Good afternoon

I appreciate that you can help with this problem, I have an Exchange 2019 server installed locally, the problem I have is specifically with some domains, most of them work fine, however occasionally it happens to me with some domains that the emails stay in the sending queue generating this message:

421.4.4.2 Broken Connection Exchange

The error occurs in certain domains when an email is sent to more than one recipient, however, if you delete the email queue and send the email to the affected domain again, leaving only one recipient, the email goes out without a problem.

Please could you help me with what validations I can do to determine the cause.

Thank you so much
Exchange Server
Exchange Server
A family of Microsoft client/server messaging and collaboration software.
1,258 questions
Windows Server 2019
Windows Server 2019
A Microsoft server operating system that supports enterprise-level management updated to data storage.
3,700 questions
Exchange Server Management
Exchange Server Management
Exchange Server: A family of Microsoft client/server messaging and collaboration software.Management: The act or process of organizing, handling, directing or controlling something.
7,599 questions
0 comments No comments
{count} votes

Accepted answer
  1. Jarvis Sun-MSFT 10,191 Reputation points Microsoft Vendor
    2023-09-22T02:54:34.0566667+00:00

    Hi @Camilo Quintero

    Thanks for posting in our Q&A forum.

    The error message you’re seeing, “421.4.4.2 Broken Connection Exchange,” indicates that there is a problem with the connection between your server and the recipient’s server.

    Based on the information you’ve provided, it seems that the issue occurs when an email is sent to more than one recipient. One possible solution is to create a new send connector for the affected domains and set ForceHELO to true. You may also need to restart the Microsoft Exchange Transport service. You can also try enabling TLS 1.2 on your server if it isn’t already enabled.

    107886-10.png

    If the issue persists, you may want to check if your server’s Public IP is listed in any blacklist DNS, which could cause delays in message delivery.


    If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment". 

    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.

    1 person found this answer helpful.
    0 comments No comments

0 additional answers

Sort by: Most helpful

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.