Enhanced Status Code 4.7.0: Other Security or Policy Status - Temporary
Enhanced Status Code 4.7.0 means “Other Security or Policy Status - Temporary.” The receiving server has temporarily rejected your email for security or policy reasons. This is heavily used by Gmail and Microsoft for IP reputation-based throttling. Repeated 4.7.0 responses indicate a sender reputation problem that needs attention.
421-4.7.0 [203.0.113.10] Our system has detected that this message is suspicious due to the very low reputation of the sending IP address. To best protect our users from spam, the message has been blocked. Please visit https://support.google.com/mail/answer/188131 for more information. - gsmtp
What does 4.7.0 mean?
Enhanced status code 4.7.0 is one of the most important codes for email senders to understand. Gmail uses "421-4.7.0" when it detects suspicious sending patterns or low IP reputation. Microsoft uses it for similar reputation-based throttling. Yahoo returns temporary security blocks with equivalent codes.
When Gmail returns 4.7.0, it typically includes messages like "Our system has detected that this message is suspicious" or "IP not in whitelist for RCPT domain." This means Google is not blocking you permanently but is flagging your sending as potentially problematic. Your MTA should retry, and the message may go through, but repeated 4.7.0 responses are a serious warning.
If you consistently receive 4.7.0 from a major provider, it means your sending reputation needs improvement. Check Google Postmaster Tools for your domain reputation, verify all authentication records, review your sending patterns for spammy behavior, and ensure your lists are clean.
How 4.7.0 plays out
4.7.0 replyWhere 4.7.0 sits: soft vs hard bounce
| Soft bounce (4xx) | Hard bounce (5xx) | |
|---|---|---|
| Nature | Temporary | Permanent |
| SMTP class | 4xx | 5xx |
| What to do | Let it retry | Suppress the address |
| Recoverable? | Often | No |
| 4.7.0 is | ✓ this code |
Common causes of 4.7.0
- IP address has low or unknown reputation with the receiving provider
- Sending volume spike triggered throttling
- New IP without established sending history (cold IP)
- Previous spam complaints from recipients at this provider
- Sending patterns match known spam behavior
- IP was recently removed from a blacklist but reputation has not recovered
How to fix 4.7.0
- Check your IP reputation using Sender Reputation Checker
- Review Google Postmaster Tools or Microsoft SNDS for provider-specific reputation data
- Warm up new IPs gradually over 2-4 weeks
- Reduce sending volume temporarily to allow reputation to recover
- Verify SPF, DKIM, and DMARC are correctly configured
- Clean your email list of invalid addresses and unengaged recipients