451 4.4.1
No answer from host / connection timeout
The connection to the next hop timed out before the message could be handed off.
451 4.4.1 No answer from host
What it means in practice
4.4.1 means the sending server reached the point of handing off the message and the next hop never answered. The address and the content are fine; the network path or the receiving server isn't.
Most sending services, AWS SES included, keep retrying deferred messages on their own for hours before they report a bounce, so a single 451 4.4.1 in your logs is rarely something to act on. What is worth checking is a pattern: the same recipient domain timing out for every message. Look up its MX records with dig or nslookup. An MX pointing at a host that no longer exists, or at a firewall that drops port 25, produces exactly this code.
If you run your own MTA, also check outbound port 25. Many cloud providers block it by default, and the symptom is a timeout to every destination, not just one.
Common causes
- Network issue between sending and receiving infrastructure.
- Receiving server is down or unreachable.
What to do
- →Retry - usually resolves on its own. Persistent timeouts to one domain suggest a routing or DNS issue worth checking (MX records resolve correctly).