What the message looks like
550 5.4.1 Recipient address rejected: Access denied. AS(201806281) [DB3EUR04FT012.eop-eur04.prod.protection.outlook.com]Common causes
- The recipient address has a typo, or the person or alias was removed or never created.
- The domain is set to "Internal Relay" in Exchange Online, but the mailbox lives on another server, and no connector sends the mail on.
- The mailbox was just created or renamed, and the change has not spread yet.
- The MX of the domain points to Microsoft 365, but the mailboxes are hosted somewhere else, for example after a migration.
- For a distribution group, it accepts only authenticated senders, or the group was deleted.
Check
- Where does the MX of the recipient domain point?
- Find the bounce in your own Postfix log
- Does the recipient exist in the tenant? (Exchange Online PowerShell, as admin)
Get-Recipient user@example.com | Format-List PrimarySmtpAddress,RecipientType - What type is the accepted domain? (Exchange Online PowerShell, as admin)
Get-AcceptedDomain | Format-Table DomainName,DomainType
Fix
- Check the address letter by letter with the recipient, and test with the primary address.
- If the mailbox or alias is missing, create it or add the address to the right user. Wait a short time for it to spread.
- If mailboxes are still on-premises, set the accepted domain to Internal Relay and create the outbound connector, or keep the domain Authoritative when all mailboxes are in Exchange Online.
- After a migration, move the MX record to the system that now holds the mailboxes.
- Send the test again from outside and compare the new bounce, if any.
Typical scenario
After migrating to Microsoft 365, a customer writing to sales@example.com gets the bounce 550 5.4.1 Recipient address rejected: Access denied together with AS(201806281). The mailbox was created in the old environment, but its address was never synced with the directory. First check in Exchange Online with Get-Recipient sales@example.com whether the address exists as a recipient, before you look at MX or SPF.
FAQ
How is this different from 550 5.1.1?
5.1.1 says the user is unknown. 5.4.1 with Access denied is the answer of Exchange Online's directory-based edge blocking, which also hides whether an address exists. The cause is still, most of the time, that the recipient is not found.
Can the sender fix this alone?
The sender can check the spelling and ask the recipient to confirm the address. If the address is right, only the recipient's admin can fix it in the tenant.
What is Directory Based Edge Blocking?
Exchange Online checks incoming mail against the directory at the edge and rejects unknown recipients immediately. That protects against harvesting of valid addresses. An address that exists only on-premises or in another tenant is therefore refused with 5.4.1.
How long until a new alias takes effect?
After creating or syncing it, the directory replication needs some time until the address is known everywhere. Test again after a wait instead of making further changes right away. In the meantime check that the address is listed among the recipient's email addresses.
What is different in a hybrid setup?
If some mailboxes remain on-premises, the accepted domain in Exchange Online must be configured as InternalRelay rather than Authoritative. Exchange Online then forwards mail for unknown recipients instead of rejecting it, and the on-premises server can deliver it.