Public folders stop receiving mails with reason: 550 5.4.1 []: Recipient address rejected: Access denied

Hello,

our Office365 account is working fine since years.

We have public folders to receive mails to addresses like *** Email address is removed for privacy ***".

Some time ago there were issues, we needed to adjust rights and then it worked fine again.

Until now - since some day in June the public folders do not accept mails from the outside any longer (e.g. from Gmail or GMX).

The sender gets a "Mail delivery failed: returning message to sender" error, with that message:

This message was created automatically by mail delivery software.

A message that you sent could not be delivered to one or more of
its recipients. This is a permanent error. The following address(es)
failed:

*** Email address is removed for privacy ***:
SMTP error from remote server for RCPT TO command, host: xxxxxxxmail.protection.outlook.com (213.199.154.999) reason: 550 5.4.1 [*** Email address is removed for privacy ***]: Recipient address rejected: Access denied

No clue. Could someone help, please?

Thanks.

Marc

|

Hi Marc,

 To better understand the problem, please provide us with the following information.

•    Do you mean that every external sender received NDR 5.4.1 when they send email to public folder address in your domain?
•    Does this issue happen to every public folder or specific public folder address?
•    May I know whether you have configured the domain type are Authoritative or Internal relay. You can check the status of the domain in the Exchange admin center by performing these steps:

1.    In the EAC, navigate to Mail flow > Accepted domains.
2.    Select the domain and click Edit icon

•    Which kind for environment do you set up? Is it Hybrid deployment?
•    Could you please provide us with the detailed Non Delivery Report (NDR without editing) and tenant domain (@contoso.com) via the private message for further analysis?

Moreover, please make sure the Anonymous users have got the enough permission so that they will be able to send emails to the public folder.

I have sent you private message and here is the link to access it: https://answers.microsoft.com/en-us/privatemessages/list

Best regards,
Shyamal

---------------------
* Beware of scammers posting fake support numbers here.

* Kindly Mark and Vote this reply if it helps please, as it will be beneficial to more Community members reading here.

1 person found this reply helpful

·

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Hi Marc,

Thanks for the information in Private Message.  To my knowledge, the 5.4.1 external mail flow could occur when Exchange Online Protection rejects the coming messages because the Directory Based Edge Blocking (DBEB) doesn't recognize the public folder as a valid recipient in Exchange Online. A workaround for this issue is to covert the smtp domain from Anthoritative to Internal Relay. Please try it in your Exchange admin center and let us know if it works.

Best Regards,
Alex

12 people found this reply helpful

·

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Hello Alex,

Thank you for your reply. It doesnt help.

I changed for that domain to 'Internal Relay', test unsuccessful, changed it back to 'Authoritative', test unsuccessful.

What next?

Thanks

Marc

1 person found this reply helpful

·

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Hi Marc,

Thanks for your efforts so far.

By checking the NDR you provided, we can see the email is sent to the public folder on a custom domain. By default, mail-enabled public folders are on the Office 365 default domain xxxx.onmicrosoft.com. Can you please let us know how you modified the email address to a custom domain? Did you use the PowerShell command Set-MailPublicFolder to do it?

Moreover, please use PowerShell to manage the permission by referring to Add-PublicFolderClientPermission. If the CreateItems permission does not work, please try a higher permission such as EditAllItems. (When doing all this, please keep the domain type as Internal Relay.)

And if the issue still exists, please run a message trace to look for the affected email, and see what it says from the trace result. You can reply to our private message again to provide the trace result.

Regards,
Allen

1 person found this reply helpful

·

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Hello Allan,

please let me point out again that our configuration ran fine for years.

We did not change/touch anything.

It suddenly stopped working in early June 2016.

Back to your questions.

We added the address "*** Email address is removed for privacy ***" by going to EAC, public folders, edit the "info" folder, click "email address", click "+".

We followed your Add-PublicFolderClientPermission for the test that you requested. No success.

We tried all kind of rights, including "owner". No success.

I run a message trace; the mails in question do not appear here.

We are a Microsoft Partner, and this case is urgent.

Could someone please now finally help to resolve that issue? It appearantly is caused by something that happened on the Microsoft end and we quickly need a fix.

Thanks a lot!

Marc

1 person found this reply helpful

·

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Hi Marc,

Thanks for letting us know these details. Upon further analysis, this issue may need to be escalated to our engineering team. Please check the new private message I sent you with the subject Information Required for Escalation.

Regards,
Allen

1 person found this reply helpful

·

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Hi Marc,

We have received the requested information via the PM. The behavior that you reported is not what we commonly encounter. We have engaged the relevant team to continue to assist you on this. You will be contacted via email for further troubleshooting. We will share the solution to the community once you have confirmed that this has been resolved. And our community members may benefit from the outcome of this issue.

Thanks,
Allen

1 person found this reply helpful

·

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Hi Marc,

I find the issue is resolved. Here is the closure summary.

 

Issue Description:

================

When external mailboxes send emails to an Exchange Online public folder, an NDR bounced with the error: 550 5.4.1 Recipient address rejected: Access denied.

 

Root Cause/Analysis:

================

When the domain type is set to Authoritative, Directory Based Edge Blocking (DBEB) allows any SMTP address that has been added to the service, except for mail-enabled public folders.

 

Resolution:

================

Keep the domain type as Internal Relay.

 

Thanks,

Young

41 people found this reply helpful

·

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

 
 

Question Info


Last updated June 11, 2021 Views 15,830 Applies to: