What 421 4.7.500 Means
Microsoft 365's MX returned 421 4.7.500 to signal it's busy or rate-limiting your connection. Per Microsoft's documentation, 4.7.500 is the catch-all 'server busy, try later' enhanced code. The 4xx prefix means it's transient — your sending server should retry.
Microsoft 365 / Office 365 tenants and Outlook.com. The 4.7.500 enhanced code is Microsoft-specific.
Microsoft is rate-limiting your sending IP (most common in cold email); Microsoft's MX is temporarily overloaded; your IP has soft-reputation issues that throttle but don't block; or you've opened too many concurrent connections from one IP.
How to Fix 421 4.7.500
- 1
Let your sending platform retry
4.7.500 is transient. Standard exponential backoff (15 min, 30 min, 1 hr, 2 hr) catches most 4.7.500 events. Don't manually re-send aggressively.
- 2
Check concurrent connection count
Cap concurrent SMTP connections from one IP to Microsoft at 1-2. Microsoft tolerates more than Gmail (typically 3-5 is OK), but high concurrency from a new IP triggers 4.7.500 reliably. Reduce concurrency in your sending platform's settings.
- 3
Check IP reputation in SNDS
sendersupport.olc.protection.outlook.com/snds shows Microsoft's view of your IP. Yellow tier means you're already in soft-throttle territory; sustained sending pushes you to Red (5.7.501).
- 4
Spread sends across the day
200 messages sent in 5 minutes from one IP to Microsoft trips 4.7.500. Same 200 spread over 4 hours doesn't. Configure send-time spread in your platform.
- 5
Reduce per-mailbox daily volume
If 4.7.500 persists for the same mailbox across days, that mailbox is over its reputation tier's volume budget. Drop to 2-5/day per mailbox. Add more mailboxes if you need higher total volume.
References
421 4.7.500 in the Cold Email Context
Microsoft's 4.7.500 is the Outlook-side equivalent of Gmail's 4.7.28 — a transient rate-limit warning. The structural fix is identical: dedicated IPs (so you're not competing with other tenants for connection budget), conservative per-mailbox volume, and authentication that's all-three-green (SPF, DKIM, DMARC). ColdRelay's dedicated-per-customer IPs eliminate cross-tenant contention; the 2/day/mailbox cap keeps you under Microsoft's reputation thresholds; and ColdRelay's automated DNS configuration ensures authentication is correct from the start.
Frequently Asked Questions
How long does 4.7.500 last?
Short bursts: minutes. The next retry typically succeeds. Sustained over-rate sending: hours to days. If it persists, the cause is structural — too much concurrency or volume.
Does 4.7.500 hurt my reputation?
Mildly. Microsoft tracks 4xx-to-2xx conversion. Most 4.7.500 events resolve on retry, which is reputation-neutral. Sustained 4.7.500 without resolution gradually pushes you from Green to Yellow tier.
Is this the same as 451 4.7.500?
Different severity. 421 4.7.500 closes the entire connection — try later for the whole session. 451 4.7.500 defers just the current recipient; you can attempt other RCPT TOs in the same session. Both are transient and resolve similarly.
Should I just bypass Microsoft and send direct?
You're already sending direct. Microsoft 365 MX is the recipient's mail server — you can't bypass it. The throttle is from Microsoft's MX. The fix is on your sending side: throttle volume, reduce concurrency, fix reputation.