Fix DBEB Rejection Error 550 5.4.1 for Exchange Online Public Folders
Question details
Users need to prevent Directory-Based Edge Blocking (DBEB) from rejecting incoming messages sent to mail-enabled public folders in Exchange Online.
- Product
- Exchange Online
- Device & OS
- not provided
- Scenario
- External or internal emails are being routed to mail-enabled public folders but are unexpectedly blocked by the server's directory filtering.
- Observed behavior
- Senders receive a Non-Delivery Report (NDR) with the error '550 5.4.1 Recipient address rejected: Access denied' because of DBEB restrictions.
Verify that your organization utilizes a trusted third-party email security service to filter traffic before creating any rules to bypass Exchange Online Protection (EOP).
Create a Mail-Flow Rule to Bypass Exchange Online Protection
Use this solution to selectively bypass DBEB for affected public folders, allowing messages through your third-party security layer.
Directory-Based Edge Blocking (DBEB) rejects messages to addresses not recognized in your directory. By bypassing Exchange Online Protection (EOP) for specific public folders, you can successfully route these emails.
This configuration should only be implemented if you have an external, trusted third-party email security gateway protecting your Microsoft 365 environment.
Log in to the Exchange Admin Center, run a message trace on the failed email, and review the Non-Delivery Report (NDR) to verify that DBEB is actively causing the 550 5.4.1 rejection.
In the Exchange Admin Center, go to 'Mail flow' in the left-hand navigation pane, and select 'Rules'.
Click the '+' icon to create a new rule. Name the rule appropriately, such as 'Bypass EOP for Public Folders'.
Under 'Apply this rule if...', select 'The recipient is...', and choose the specific mail-enabled public folders experiencing the DBEB rejections.
Under 'Do the following...', select 'Modify the message properties', then 'set the spam confidence level (SCL)'. Set the value to '-1' to bypass spam filtering.
Save the rule and ensure its status is set to 'Enforced'. Test the configuration by sending an email to the public folder.
Manage Your Work Efficiently with WPS Office
While resolving complex Exchange Online mail routing issues, ensure your team stays productive with their everyday documents. WPS Office is a free, lightweight, and powerful alternative to Microsoft Office, offering an intuitive interface and high format compatibility.
- 1. Download the Installer: Visit the official WPS Office website and download the free installer for your operating system.
- 2. Install the Software: Run the setup file and follow the on-screen prompts to complete the rapid installation.
- 3. Open Your Documents: Launch WPS Office and immediately open your existing Microsoft Office formats (.docx, .xlsx, .pptx) without any layout distortion.
Frequently Asked Questions
What causes the '550 5.4.1 Recipient address rejected' error?
This error occurs when Directory-Based Edge Blocking (DBEB) in Exchange Online rejects an incoming email because the recipient's email address is not recognized as a valid mailbox within the directory.
Is it safe to completely disable DBEB?
No, completely disabling DBEB globally is not recommended as it leaves your organization vulnerable to directory harvest attacks and excessive spam. You should only use targeted mail-flow rules to bypass filtering for specific trusted scenarios.
How do I confirm if DBEB is blocking my public folder emails?
You can confirm this by running a message trace in the Exchange Admin Center. Review the delivery details and the Non-Delivery Report (NDR) attached to the trace, which will explicitly indicate if Directory-Based Edge Blocking intercepted the message.
