What is “421 RP-001” (Microsoft rate limit)?
Still have a question, spotted an error, or have a better explanation or a source we should cite?
You're mid-send, volume is climbing, and suddenly Outlook starts bouncing everything back with a 421 RP-001. No permanent rejection, no blacklisting. Just Microsoft telling you to slow down.
A 421 RP-001 is a temporary deferral. Your sending IP has hit the rate limit Microsoft assigned to it for this session. The message isn't lost. It's queued. Back off the pace and Microsoft will accept it.
The RP series covers three flavors of the same problem. RP-001 is general rate limiting (you're sending too many messages per unit of time). RP-002 is connection rate limiting (too many simultaneous SMTP connections from your IP). RP-003 is recipient rate limiting (too many different recipients hit in a short window). Most senders run into RP-001 first, but if you're opening dozens of parallel connections you'll see RP-002 show up fast too.
Microsoft doesn't publish the exact thresholds, so there's no formula to punch numbers into. What it does is assign limits based on your IP's reputation tier. A fresh or warming IP gets a tight budget. An established IP with clean engagement history gets more room. When you blast volume before building that trust, the 421 gates you.
The practical way to figure out where your ceiling is: ramp slowly and watch your acceptance rate. Start with a few hundred messages per hour, check the SMTP logs, and increase from there until deferrals appear. That threshold is your current limit. It moves over time as your reputation grows.
Still when you're already getting hammered with RP-001 errors, the fix is straightforward. Reduce your send rate immediately. Build in exponential backoff so your ESP waits longer between retries rather than hammering the same connection. Spread the volume across a longer window. Most ESPs let you throttle messages per hour at the job or stream level. Use it.
Longer term, the limit rises when your reputation does. That means consistent volume (not spikes), low complaint rates, clean bounce handling, and engaged recipients who actually open and click. Microsoft's filters notice all of it.
If the deferrals aren't clearing after a few hours of backing off, it's worth checking whether your domain or IP has landed on a blocklist. Our free Blocklist Checker can tell you in seconds. Or if the situation feels urgent, the RME SOS hotline is free and we actually pick up.
Contributors
Who worked on this answer
Every name links to their profile. Every company links to their site. Real people, real accountability.
