SMTP 451 4.4.1: no answer from host (connection timed out)
A 451 4.4.1 reply means the sending server could not get an answer from the destination host, so the message is deferred for retry. RFC 3463 defines X.4.1 as "No answer from host": the outbound connection was not answered because the far system was busy or unable to take the call. As a 4.x code it is temporary, and a healthy sender retries on its own.
The enhanced status code 4.4.1 is defined by RFC 3463 as "No answer from host": the outbound connection attempt got no response because the remote system was busy or could not accept the connection. RFC 3463 marks this as a persistent transient error, so it is meant to be retried.
Common causes
The destination mail server is overloaded and not accepting new connections right now.
A network problem or firewall is dropping the connection on port 25.
The host is mid-restart or briefly offline.
What to do
Usually nothing on the sending side, since a 4.x defer stays queued and retries automatically. If every attempt fails for hours, check that the MX host for the recipient domain is reachable on port 25 and that no route between you and them is blocking it. When the retry window finally expires, the message escalates to a permanent 5.4.x bounce.
Common questions
Is 451 4.4.1 permanent?→
No. The 4 marks it transient. The message stays queued and your server retries until the host answers or the retry window expires.
What makes a host stop answering?→
An overloaded or restarting mail server, or a network or firewall issue dropping connections on port 25.
Do I need to do anything about 451 4.4.1?→
Usually not. Retries are automatic. If it fails for hours, check that the MX host for the recipient domain is reachable on port 25.
What happens if 451 4.4.1 never clears?→
When the retry window expires, the server gives up and returns a permanent 5.4.x bounce for the same message.