421 4.7.0: try again later, closing connection
The receiving server is not refusing your mail for good. It closed the connection for a security or reputation reason, and expects your server to try again later.
Updated 3 min read
On this page (7)
421 4.7.0 is a temporary SMTP reply: temporary refusal, connection closed. This page is part of our SMTP error code reference, where every code links to the RFC and to what Gmail, Outlook and Yahoo publish about it.
- Kind
- Temporary: the sending server keeps the message and retries
- Retry by hand
- No, retries are automatic
- In Mailbay
deferred, thenfailedif retries run out
What 421 4.7.0 means
421 is "<domain> Service not available, closing transmission channel" [1]. The server ends the session, and the sending server keeps the message and retries later.
X.7.0 is "Other or undefined security status": "Something related to security caused the message to be returned, and the problem cannot be well expressed with any of the other provided detail codes" [2]. The 4 in front makes it temporary.

What Gmail, Outlook and Yahoo say
- Gmail
- Has eight 421 4.7.0 rows, including "Try again later, closing connection.", "TLS required for RCPT domain, closing connection.", a sending IP without a PTR record, and "This message is suspicious due to the very low reputation of the sending IP address" [3].
- Yahoo
- "A 421 or 451 SMTP error indicates a temporary problem blocking the delivery of your message", and you "may retry sending at a later time" [4].
Outlook and Microsoft 365 does not list 421 4.7.0 on the error pages we read, so we do not guess what it means by it.
Sources, read on October 14, 2026
- [1]RFC 5321, Simple Mail Transfer Protocol, section 4.2: www.rfc-editor.org/rfc/rfc5321#section-4.2
- [2]RFC 3463, Enhanced Mail System Status Codes: www.rfc-editor.org/rfc/rfc3463
- [3]Google, Gmail SMTP errors and codes: knowledge.workspace.google.com/admin/support/troubleshooting/gmail-smtp-errors-and-codes
- [4]Yahoo Sender Hub, SMTP error codes: senders.yahooinc.com/smtp-error-codes/
Prices change. If something here is out of date or wrong, email hello@mailbay.dev and we will fix it.
Common causes
- Low reputation of the sending IP or domain, often a new IP sending too much too soon.
- No TLS when the receiving domain requires it.
- A sending IP without a matching PTR record.
- Too many errors in one session, such as many recipients that do not exist.
How to fix it
- Let your server retry. A 421 is temporary, and most mail servers retry on their own for hours or days.
- If it keeps happening, check the reason text: TLS, PTR (550 5.7.25) and authentication (550 5.7.26) are quick to fix, and the deliverability test shows authentication and spam scoring for one real message.
- Slow down. Spread sends from a new IP or domain over days, and stop sending to addresses that bounce.
How Mailbay reports it
When a recipient's server answers 421 4.7.0 to mail you send through Mailbay, our mail server keeps the message and retries on its own. The recipient shows as deferred, and you get a message.deferred event with the server's reply in response. If the retries run out, the message becomes failed with a message.failed event. The message statuses page lists every state.
Mailbay's receiving and submission servers send 421 4.7.0 in two cases: Too many connections from your address, and Too many errors, closing connection after 20 failed commands in one session, the case in the session below.
Related codes
- 451 4.7.1: deferred: rate limit or policy, temporary.
- 550 5.7.25: no reverse DNS for the IP, permanent.
- 550 5.7.26: failed SPF, DKIM or DMARC, permanent.
- 550 5.1.1: mailbox does not exist, permanent.
- 535 5.7.8: login rejected, permanent.
- 530 5.7.0: sign in first, permanent.
Seeing an API error rather than an SMTP code? Mailbay's own errors, each with a fix, are on the errors page.
Questions
Do I need to resend after 421 4.7.0?
Usually not by hand. The sending server keeps the message and retries. With Mailbay the message shows as deferred while retries run, and as failed if the mail server gives up.
What is the difference between 421 4.7.0 and 550 5.7.1?
421 4.7.0 is temporary and the connection is closed; the same message may be accepted later. 550 5.7.1 is a permanent refusal of that message.
Why does Gmail say TLS required for RCPT domain?
The receiving domain's administrator requires encrypted connections. Your sending server has to use STARTTLS when it delivers to that domain.
Read next
- 451 4.7.1: try again laterThe receiving server is asking your server to come back later. Rate limits and greylisting are the usual reasons, and a normal mail server handles it without you.
- 550 5.7.25: reverse DNS check failedThe receiving server looked up the name of the IP address your mail came from and found none, or found one that does not resolve back to that IP.
- SMTP error codesWhat a bounce or deferral code means, what Gmail, Outlook and Yahoo say about it in their own words, and how to fix it. Each page shows a real SMTP session.
Join the beta
Mailbay is in private beta and free while the beta runs: inboxes, sending, your own domains and MCP. We invite people in small batches and read every note on the form.