SMTP: 550 5.4.1 Recipient address rejected: Access denied. AS(201806281) [DB5EUR03FT015.eop-EUR03.prod.protection.outlook.com]
Microsoft 365 / Exchange Online rejected the message because the recipient address does not exist in that tenant (Directory Based Edge Blocking).
550 5.4.1 Recipient address rejected: Access deniedRecipient address rejected: Access denied. ASDBEB Directory Based Edge Blockingprotection.outlook.com 550 5.4.1550 5.4.1 Recipient address rejected Meaning
Since 2018 Exchange Online rejects mail for unknown recipients at the edge. The address is misspelled, deleted, not yet synced from on-premises Active Directory, or the mail flow connector is wrong. Ask the recipient for the correct address, or fix the sync.
Common causes
- Typo or non-existent recipient address
- User deleted or never licensed in Microsoft 365
- Hybrid sync (Azure AD Connect) not yet replicated the mailbox
- Accepted domain set to Internal Relay without a connector
- Distribution group restricted to internal senders
⚡ Quick fix
- Verify the exact address with the recipient
- Admins: confirm the mailbox exists in the Microsoft 365 admin centre
- Check accepted domain type (Authoritative vs Internal Relay)
Detailed fix by platform
PowerShell
Get-Recipient user@contoso.comin Exchange Online PowerShell confirms whether the address exists
How to diagnose
- Address — Spelled correctly?
- Tenant — Mailbox exists and is licensed?
- Sync — Hybrid/AD sync complete?
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
- 421 4.7.0 Try again later (rate limited) SMTP: 421 4.7.0 Our system has detected an unusual rate of unsolicited mail originating from your IP address. Mail sent from your IP address has been temporarily rate limited
- 450 4.7.1 Greylisted, please try again later SMTP: 450 4.7.1 <user@example.com>: Recipient address rejected: Greylisted, see http://postgrey.schweikert.ch/help/example.com.html
- 451 4.3.0 Local error in processing SMTP: 451 4.3.0 Error: queue file write error / 451 Requested action aborted: local error in processing
Most viewed in Email / SMTP
- 550 5.7.26 550 5.7.26 This mail has been blocked because the sender is unauthenticated (SPF/DKIM/DMARC)
- SES: Maximum sending rate exceeded Amazon SES: Throttling — Maximum sending rate exceeded (454 Throttling failure)
- DKIM: body hash did not verify DKIM: dkim=fail (body hash did not verify) / signature verification failed
Other ways to find it
Where this error sits
Origin: Network. Errors that are often confused with or caused by this one (click to open):
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
💬 What worked for others
No tips yet — did something else fix this for you?
Share what worked for you
Tips are checked by an editor before they appear. Links are removed.
Report a correction or suggest an improvement
Last updated 4 Nov 2026