Fix the Exchange Error “Recipient Deferred Because There Is No Mailbox Database”
Question details
Identify and correct the mail-routing issue behind the recipient deferred mailbox database error.

- Product
- Microsoft Exchange Online and Dynamics 365
- Device & OS
- not provided
- Scenario
- A message is sent to recipients whose mailboxes may be hosted on an on-premises or third-party mail system rather than Exchange Online.
- Observed behavior
- Dynamics CRM or Microsoft 365 returns “420 4.2.0 Recipient deferred because there is no mailbox database.”
Gather an affected recipient address, the approximate message time, and the full error text. Sign in with an account that can access the Exchange admin center and confirm where the recipient mailbox is hosted.
Check Recipient Hosting and Exchange Mail Routing
Use this approach when recipients have on-premises or third-party mailboxes and messages may pass through Microsoft 365.
Ask the mail administrator to check the recipient address in the on-premises Exchange or third-party mail system and confirm whether the organization uses a hybrid Exchange setup.
Run a DNS lookup such as `nslookup -type=mx example.com`, replacing example.com with the recipient domain. Note whether the records point to Microsoft 365, an on-premises server, or another mail provider.
In the Exchange admin center, open Mail flow > Accepted domains and Mail flow > Connectors. Verify that the domain configuration and connectors match the intended route to the on-premises or third-party mail system.
In the Exchange admin center, open Mail flow > Message trace. Search by recipient and the approximate send time, then review the status and events to identify where routing failed.
Use the trace and connector details to coordinate changes with the mail administrator, then resend a test message to the affected recipient and check its delivery status.

Work With Office Files in WPS Office
WPS Office is a free, lightweight alternative with a familiar interface and Microsoft Office format support for an easier transition. It does not fix Exchange routing or mailbox errors.

Frequently Asked Questions
Does this error mean the recipient needs an Exchange Online mailbox?
Not necessarily. The mailbox may be hosted on an on-premises or third-party system. Confirm its location and verify that Microsoft 365 is configured to route mail to that system.
Where can I check whether Microsoft 365 processed the message?
In the Exchange admin center, go to Mail flow > Message trace and search using the recipient address and approximate send time. Review the trace events for delivery or routing details.
What should I check if the domain’s MX record points to a local mail server?
Confirm the recipient mailbox exists on the local system, then review Mail flow > Connectors and Accepted domains in the Exchange admin center. Use message trace to determine whether the affected message passed through Microsoft 365.
Can WPS Office resolve this Exchange error?
No. The error requires investigation of Microsoft 365, Exchange, and the recipient mail system. WPS Office can be used separately to work with documents and spreadsheets.




