Fix Exchange Online 5.4.1 Errors for Mail-Enabled Public Folders
Question details
Resolve a 5.4.1 delivery error for a mail-enabled public folder that may not be recognized by Directory-Based Edge Blocking.

- Product
- Exchange Online and Exchange Online Protection
- Device & OS
- not provided
- Scenario
- Internal or external senders need to deliver email to a mail-enabled public folder.
- Observed behavior
- Exchange Online Protection may reject a message with a 5.4.1 error because it does not recognize the public folder as a valid recipient.
Have the full non-delivery report (NDR), the public folder's SMTP address, and administrator access to the Exchange admin center ready. Identify whether the public folder is hosted in Exchange Online or in an on-premises or hybrid deployment.
Check the public folder address, permissions, and mail flow
Use the NDR and Exchange settings to identify whether the recipient address, permissions, or routing configuration is causing the rejection.
Open the non-delivery report and check the full 5.4.1 diagnostic message and rejected recipient address. Use these details to distinguish recipient recognition problems from other delivery issues.
In the Exchange admin center, open Public folders and select the mail-enabled folder. Check its email addresses and confirm that the address used by senders is present and spelled correctly.
Review the folder's delivery restrictions and public folder permissions. If external senders must post to it, verify that the appropriate anonymous posting permission is configured.
In the Exchange admin center, review Mail flow settings and the accepted domain. For hybrid or on-premises public folders, also check that mail-enabled public folder objects are synchronized as required for the deployment.
Send separate messages to the folder from an internal mailbox and an external address. If either fails, compare the new NDR with the original diagnostic message.

Test an Internal Relay domain for the public folder
Consider this approach when a suitable domain is configured as a shared domain and recipient recognition remains a problem.
Document Exchange Troubleshooting in WPS Office
WPS Office is a free, lightweight Office alternative with a familiar interface and support for common Microsoft Office formats, making it easy to move existing documents and record mail-flow troubleshooting. It does not change Exchange settings or resolve delivery errors.

Frequently Asked Questions
What does a 5.4.1 error mean for a public folder?
It can indicate that Exchange Online Protection does not recognize the folder's address as a valid recipient. Check the full diagnostic text in the NDR because the exact cause depends on the deployment and mail flow.
Should I change my primary domain to Internal Relay?
Not without reviewing the impact. In Exchange admin center, check Mail flow > Accepted domains and review routing and connectors first. Test with a suitable less-used domain before considering a primary-domain change.
Can external senders email a mail-enabled public folder?
Yes, if its address, delivery restrictions, and public folder permissions allow it. Review the folder's settings in the Exchange admin center and verify appropriate anonymous posting permission when external access is required.
What should I check in a hybrid public folder deployment?
Verify that the mail-enabled public folder objects are synchronized as required and that connectors route messages to the correct environment. Use the NDR and internal and external test messages to narrow down the failure.




