By the registry, x.4.1 is a connection that was not answered, and meant only as temporary. Microsoft 365 uses 5.4.1 for something else: “Recipient address rejected: Access denied” — directory-based edge blocking refused an address it does not know, or a server that does not accept mail for the domain refused to relay.
| Code | 5.4.1 |
| Meaning | No answer from host |
| Kind | Permanent failure — the sender gives up |
| Sent in reply to | With 550, at RCPT |
| What the sender does | Returns the message to the sender |
| 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
- The recipient’s address does not exist in the Microsoft 365 organisation.
- The domain is set up in Microsoft 365, but its mail should be routed elsewhere — or its MX points at a server that does not take mail for it.
What to do
- Check the recipient’s address.
- For the domain’s administrator: if a whole domain bounces, switch its accepted domain from Authoritative to Internal relay and back, and check the MX; in hybrid setups allow up to 24 hours for the directory to update.
What each provider means by it
| Who | What they say |
|---|---|
| Microsoft 365 | 550 5.4.1 Recipient address rejected: Access denied — directory-based edge blocking; also “Relay Access Denied”. |
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.4.1 “Recipient address rejected: Access denied” — support.microsoft.com