Fix Exchange Online Public Folder Mail Error 550 5.4.1
Question details
An administrator needs to diagnose why external messages to a mail-enabled public folder are rejected with error 550 5.4.1.

- Product
- Exchange Online public folders
- Device & OS
- not provided
- Scenario
- External senders email a public folder in a Microsoft 365 organization that may also use an on-premises mail system.
- Observed behavior
- Messages are rejected with '550 5.4.1 Recipient address rejected.' Changing the accepted domain to Internal Relay and attempting to set a different primary SMTP address did not resolve the reported issue.
Have the rejected recipient address and the complete non-delivery report available, and sign in with an account authorized to manage Exchange recipients and mail flow. Identify whether the public folder is hosted in Exchange Online or on-premises before changing routing settings.
Inspect the public folder's SMTP addresses and accepted domains
Use this first to check whether the address receiving external mail is assigned to the intended public folder and belongs to the correct accepted domain.
Open Exchange Online PowerShell and run Connect-ExchangeOnline, then sign in with an authorized administrator account.
Run Get-MailPublicFolder -Identity '<public folder identity>' | Format-List * and examine PrimarySmtpAddress and EmailAddresses. Compare them with the exact recipient address in the non-delivery report.
Run Get-AcceptedDomain | Format-Table Name,DomainName,DomainType. Confirm that the domain in the intended external address is listed and that its domain type matches the organization's mail-routing design.
Run Get-Recipient -Identity '<recipient SMTP address>' | Format-List Name,RecipientTypeDetails,PrimarySmtpAddress,EmailAddresses to see whether Exchange Online resolves the address to the intended recipient.
If a Set-MailPublicFolder -PrimarySmtpAddress command fails, retain the complete command and error output. Check the folder object and domain configuration before attempting another change; do not assume the onmicrosoft.com domain is the intended external address.

Review hybrid routing and public folder delivery
Use this when the addresses appear correct but external delivery still fails, especially in an organization with on-premises Exchange.
Document Exchange Mail Troubleshooting with WPS Office
WPS Office is a free, lightweight alternative for documenting troubleshooting and sharing reports. Its familiar interface and Microsoft Office format compatibility make it easy to move existing documents and spreadsheets, although it does not fix Exchange Online mail routing.

Frequently Asked Questions
What does error 550 5.4.1 mean for a public folder?
It indicates that the recipient address was rejected during mail delivery. Check the exact address in the non-delivery report against the folder's PrimarySmtpAddress and EmailAddresses using Get-MailPublicFolder.
Will setting the accepted domain to Internal Relay fix the error?
Not necessarily. Internal Relay must match the organization's routing design, particularly in hybrid environments. Review Mail flow > Accepted domains and the relevant connectors before changing it.
How can I check whether Exchange Online recognizes the folder's address?
In Exchange Online PowerShell, run Get-Recipient -Identity '<recipient SMTP address>' and verify that the returned recipient is the intended mail-enabled public folder.
Why does changing PrimarySmtpAddress still produce an error?
The full error output and folder configuration are needed to determine the cause. Inspect the complete object with Get-MailPublicFolder -Identity '<public folder identity>' | Format-List * and compare its addresses with Get-AcceptedDomain before trying another change.
Do public folder permissions matter for external mail?
Yes. External posting permissions can affect delivery independently of address resolution. Review the folder's permissions with Get-PublicFolderClientPermission and check whether external posting is allowed where required.




