421 4.7.0 Our system has detected an unusual rate of unsolicited mail originating from your IP address

Gmail is throttling the sending IP. The message is not rejected for good; the server is told to come back later, and a well-behaved MTA will retry for hours or days. The same code also appears with "Try again later, closing connection" and "TLS required for RCPT domain", which are different temporary conditions.

What the server replies

421-4.7.0 [203.0.113.10 15] Our system has detected an unusual rate of 421-4.7.0 unsolicited mail originating from your IP address. To protect our 421-4.7.0 users from spam, mail sent from your IP address has been temporarily 421-4.7.0 rate limited. Please visit 421 4.7.0 https://support.google.com/mail/?p=UnsolicitedRateLimitError to review our Bulk Email Senders Guidelines.

Sent by
Gmail
Type
TemporaryRetry helps
About
Rate limits and quotas
Enhanced code
4.7.0

Who sends it

Gmail inbound servers, usually right after RCPT TO or at the start of the session, when an IP's recent volume or complaint rate crosses a threshold. It is the first warning before the permanent 550 5.7.1 block.

Why it happens

  • A sudden jump in volume from an IP that has little sending history with Gmail.
  • A burst of complaints or bounces from a single campaign.
  • Several unrelated customers sharing one IP, one of whom is misbehaving.
  • Opening too many parallel connections to Gmail from one host.
  • For the "TLS required" variant: the sending server offered no STARTTLS and the recipient domain enforces it.

How to fix it

  1. Let the queue drain

    Do not clear or resend the queue. Leave the messages to retry; Gmail lifts the limit on its own when the rate falls. Resending from a second IP spreads the damage.

  2. Cut concurrency and rate

    Limit connections to Gmail to a handful at a time and messages per connection to around twenty. Most MTAs have a per-destination transport setting for this.

  3. Find the campaign that caused it

    Compare the moment the deferrals began with your send log. Pause whatever list or customer started sending just before, and check its complaint rate in Postmaster Tools.

  4. Warm up properly

    For a new IP, start at a few hundred messages a day to Gmail and double every two or three days, sending to engaged recipients first.

Check it yourself

These free tools show the records and connections behind this code for your own domain or server.

Related codes

Sources

Fewer bounces to look up.

Faivelo queues temporary failures and retries them on a schedule receivers accept, then tells your application once, in plain words, if a message finally cannot be delivered.

Send with Faivelo

Free tier included. No card needed.

Questions people ask