SMTP error 421, what it means and what to do
Error 421 is the receiving server saying "not now" and hanging up: RFC 5321 defines it as service not available, closing the transmission channel. Because it is a 4xx temporary failure, properly configured mail servers queue the message and retry automatically, and most 421 episodes end in successful delivery without any human action. It earns attention when it persists, because a persistent 421 indicates rate limiting of the sender, a resource problem on the receiving server, or a middlebox interfering with the connection.
The fix, in order
- If you sent one message from a client: wait and resend later. A single 421 during a busy period or a provider's maintenance window resolves itself. Thirty to sixty minutes is a fair interval before treating it as a fault.
- If you run the sending server: let the queue work. Confirm the messages are queued with retry scheduled rather than bouncing. A healthy queue retries with backoff, and the receiving server usually accepts within a few cycles. Do not force fast retries; hammering a server that asked for a pause extends the pause.
- Reduce connection rate and parallelism. A frequent 421 cause is the receiving server's limit on simultaneous connections or messages per connection from one IP. Lower the sending concurrency for that destination in the mail server's configuration; bulk senders hit this long before personal senders.
- Check whether it is destination-specific. Mail flowing to every other domain while one destination returns 421 means that destination is limiting or struggling. Mail to all destinations failing with 421 points instead at the sender's own network or a firewall interfering with outbound SMTP.
- If you run the receiving server: look at connection counts, queue load, CPU and memory pressure, and any rate-limit rules recently enabled. A 421 storm after a configuration change usually traces to connection limits set lower than real traffic needs.
- Rule out middlebox interference for odd patterns. 421 responses that arrive instantly, identically, even against known-good servers can be generated by firewalls doing SMTP inspection. Testing from a different network separates that from genuine server responses.
If it still happens
Greylisting sometimes presents within the 4xx family as a temporary refusal, though it more often uses 450; a first-time sender receiving temporary errors that succeed on the automatic retry an hour later is usually experiencing greylisting or load management, both of which are the system working as designed. The human error with 421 is forcing instant retries or, worse, deleting queued mail that would have delivered itself.
Common questions
Does a 421 mean my email was lost? No. 421 is a temporary failure, and sending servers queue and retry after it. The message is delayed, not rejected; it only fails permanently if retries exhaust over days, at which point the sender gets a delay-expired notice.
Can my IP be rate limited even if I send little mail? Yes, if the IP is shared. On shared hosting and cloud platforms, many senders share one outbound IP, and the receiving server limits the IP, not the individual sender.
Related errors