4.4.1 means the sending server could not connect to the receiving one — no answer, or a timeout. It is written by the sender’s own queue, and it is temporary: delivery is retried.
| Code | 4.4.1 |
| Meaning | No answer from host |
| Kind | Temporary failure — the sender tries again |
| Sent in reply to | In the sender’s own delay notices and bounces |
| What the sender does | Keeps retrying until the queue gives up |
| Defined in | RFC 3463 |
Paste your bounce
Paste the line with the code — or the whole bounce: we explain each code in it, say whether the sender will try again, and link the service’s own page where it has one. It is read in your browser; nothing is sent.
What causes it
- The receiving server is down or unreachable.
- A firewall — or the hosting provider — blocks outbound port 25.
What to do
- Check that the recipient’s MX records point at a server that answers on port 25.
- Check that your own server may connect out on port 25: many cloud providers block it by default.
What each provider means by it
| Who | What they say |
|---|---|
| Exchange Server | 4.4.1 Connection timed out — transient network problems, or firewall or ISP restrictions on TCP port 25. |
| Microsoft 365 | Its connection failures are 4.4.316 (connection refused) and 450 4.4.317 (the receiver’s certificate chain was not trusted). |
Sources
Checked on 27 September 2026 against these official sources:
- Simple Mail Transfer Protocol (SMTP) Enhanced Status Codes Registry — iana.org
- DSNs and NDRs in Exchange Server — learn.microsoft.com
- Email nondelivery reports (NDRs) and SMTP errors in Exchange Online — learn.microsoft.com