421: sending IP blocked by a Blocked Senders policy
The recipient company’s Mimecast account has a Blocked Senders policy covering your sending IP, so Mimecast refuses the connection until that entry is removed.
- Mimecast
- Provider
- Temporary (4xx)
- Class
- Sources checked
- Author
At a glance
- Code
- 421
- Provider
- Mimecast
- Temporary or permanent
- TemporaryThe sending server keeps the message and tries again later.
- Who has to act
- The recipient's side. Their mail admin has to change something; you can tell them.
- What the server says
421 Sender address blocked.
What it means
Mimecast answers mail for the company you are writing to, and that company’s administrators decide what its policies block. Mimecast documents this reply for a Blocked Senders policy that matches the IP address of the server delivering your message. The code starts with 4, so your server treats it as temporary and keeps retrying, but each attempt meets the same policy. Nothing changes until someone on the recipient side edits or deletes the entry. The block sits in one customer’s configuration, so mail from the same IP to other Mimecast customers is not affected by it.
Common causes
- An administrator at the recipient company added your IP address, or a range containing it, to a Blocked Senders policy.
- You send from shared infrastructure, such as a bulk sending platform, whose IP was blocked because of someone else’s mail.
- An old block from an earlier incident was never removed.
How to fix it
- 01Note the IP address your mail left from; the bounce or your sending platform’s logs will show it.
- 02Contact your recipient through another channel and ask their IT team to remove that IP from their Mimecast Blocked Senders policy.
- 03If the IP is shared and you cannot get it unblocked, send from a different, well-kept IP or provider.
- 04Stop retrying in bulk until the entry is gone, since every attempt is refused the same way.
Sources
What this page rests on, checked on 20 Oct 2026. The explanation is ours; the reply text is the server's.
- Policies - Mimecast SMTP Error Codes (Mimecast support)mimecastsupport.zendesk.com
Related codes
- 421Service not available.The receiving server is closing the connection and will not take mail right now. The reply is temporary, so the sending server keeps the message and tries again later.
- 550Blocked by the company’s Blocked Senders policy.An administrator of the recipient’s Mimecast account set a Blocked Senders policy that matches your From or envelope sender address, so the message is refused.
421 at other providers
- 421 [RP-001]Outlook.com rate limit for the sending IP.Outlook.com is limiting how fast your IP can send to it because of the IP or domain's reputation; it is temporary and your server should retry.
- 421 [RP-002]Outlook.com rate limit on this connection.Your IP has sent more over a single connection than Outlook.com allows, a limit Microsoft ties to IP and domain reputation.
- 421 [RP-003]Outlook.com connection limit.Your IP has opened more connections to Outlook.com than it is allowed, a limit Microsoft links to IP and domain reputation.
- 421Temporary error or deferral.Yahoo or AOL refused your message for now with a 421, one of its two temporary error codes. Your server should keep it and retry; repeated deferrals point to reputation or complaints.
- 421Try again later.Xfinity turned the message away for now with a generic 421. Treat it as temporary and let your server retry: Xfinity uses it for several reasons it does not spell out.
- 421Reverse DNS lookup failed.Xfinity could not complete a reverse DNS lookup for your sending IP. It treats this as temporary, so your server should retry, but a broken DNS setup keeps it failing.
All 19 Mimecast codesEvery code in the wikiPaste your own bounce