By the registry, 5.1.8 means the sender’s domain does not exist or cannot receive replies. Microsoft 365 uses it for something else entirely: “Access denied, bad outbound sender” — your account has been blocked from sending, usually because it was compromised and sent spam.
| Code | 5.1.8 |
| Meaning | Bad sender’s system address |
| Kind | Permanent failure — the sender gives up |
| Sent in reply to | With 550 or 501 |
| What the sender does | Returns the message; at Microsoft 365, the account can send nothing until released |
| Defined in | RFC 3463 |
Paste your bounce
Paste the line with the code — or the whole bounce: we explain each code in it, say whether the sender will try again, and link the service’s own page where it has one. It is read in your browser; nothing is sent.
What causes it
- At Microsoft 365: the account exceeded sending limits, typically after being hacked.
- Elsewhere: a sender domain with no DNS, so a reply could not be delivered.
What to do
- At Microsoft 365: secure the account — reset its password, check its sign-ins and rules — then have an administrator release it on the Restricted entities page.
- Elsewhere: make sure the sending domain exists and has MX or A records.
What each provider means by it
| Who | What they say |
|---|---|
| Microsoft 365 | 550 5.1.8 Access denied, bad outbound sender — the account was blocked for sending too much spam, usually because it was compromised. Restrictions are usually removed within an hour of release. |
| Yahoo | Checks that the From domain resolves; answers 451 while its DNS fails and 554 when it does not exist. |
Sources
Checked on 27 September 2026 against these official sources:
- Simple Mail Transfer Protocol (SMTP) Enhanced Status Codes Registry — iana.org
- Email nondelivery reports (NDRs) and SMTP errors in Exchange Online — learn.microsoft.com
- NDR error code “550 5.1.8 Access denied, bad outbound sender” — support.microsoft.com
- DSNs and NDRs in Exchange Server — learn.microsoft.com
- SMTP Error Codes — senders.yahooinc.com