What the bounce says
Exact wording as it appears in the rejection or NDR. Placeholders such as x.x.x.x and example.com stand for your own address and domain.
451 4.7.500 Server busy. Please try again later 451 4.7.500 Server busy. Please try again later from [x.x.x.x]. (S77719)
A 451 4.7.500 is a temporary deferral from Exchange Online: the service asked the sender to try again later. Most occurrences are transient and clear on retry; a pattern of them points at throttling of the sender.
Most common causes
- Transient load on Microsoft’s inbound infrastructure
- The sending IP is being throttled for volume or reputation
- Too many simultaneous connections from the sender
- A temporary backend condition
What to verify next
- Let the queue retry with backoff; this is temporary
- If it persists for hours, review sending volume and reputation for the IP
- Reduce concurrent connections to Microsoft
- Check 4.7.650 and 4.7.651 variants which name reputation explicitly
Transient versus throttling
Microsoft uses this code both for genuine backend load and for softly rate limiting connections it does not want to accept quickly. A single occurrence on an otherwise healthy path is noise. Repeated occurrences over hours for one sending IP indicate throttling.
Throttling is usually tied to IP reputation, connection concurrency or a sudden volume increase. The reputation variants have their own codes — 4.7.650 and 4.7.651 — which state the cause directly.
- Single deferral: retry and ignore.
- Repeated deferrals for one IP: throttling.
- Look for 4.7.650/651 nearby for the reputation signal.
What to change on the sending side
Reduce concurrent connections to Microsoft, spread volume over time, warm new IPs, and confirm PTR, HELO and authentication. If the IP is on a shared range, the range’s reputation may be the limiting factor.
When to escalate
If deferrals continue for more than a day with normal volume and a clean configuration, use Microsoft’s sender support for Outlook.com and check SNDS for the IP’s status.
Best diagnostic path
Mail Failure Doctor
Classify the complete rejection and preserve provider-specific diagnostic context.
Open analysis → Live analysisEmail Infrastructure Digital Twin
Map the domain’s public mail infrastructure and provider relationships before remediation.
Open analysis →Known limits
- Microsoft does not publish its throttling thresholds.
- Retry timing is decided by the sending server.
Common questions
Should I resend manually?
No. The queue retries automatically; manual resends create duplicates.
Is 4.7.500 a block?
No. It is a temporary deferral. Persistent deferrals indicate throttling, not a block.
What is the S77719 tag?
An internal reference Microsoft attaches to some deferrals. It does not change the meaning.
Why the exact message matters
The same status family can be triggered by different conditions, and providers frequently add diagnostic text that narrows the issue. Use the complete rejection text rather than treating the numeric code as a complete diagnosis.
Provider reference
For the provider-defined meaning and current requirements, review Microsoft Exchange Online NDR reference.