Share via

Mail-enabled Public Folder; getting 5.4.1 errors

Anonymous
2018-02-21T13:48:59+00:00

Hi,

We have set up a mail-enabled PF, but have been getting 5.4.1 errors.

I have checked similar discussions, and have gone through the process of granting the Anonymous and Default users various permissions, such as CreateItems, and going even as high as being Owner.

I see that some people are having luck by changing their domains' status from Authoritative to Internal Relay, and that seems to resolve the issue for some.

I am really wary of changing this setting for our default domain, and possibly disrupting mailflow for hundreds of users (and a number of other mail-enabled Public Folders) in the process.

What recommendations would people have for resolving this?

Many thanks,

Steve

Microsoft 365 and Office | Subscription, account, billing | For home | Windows

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

Answer accepted by question author

Anonymous
2018-02-21T15:28:36+00:00

Hi Steve,

For 5.4.1 error, it will 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. If you did not try it, please try it and let me know if it works.

If the issue persists, please provide the following information for us:

  1. Does the issue only happen to external users?

2. Does this issue happen to every public folder or specific public folder address?

3. Which kind for environment do you set up? Is it Hybrid deployment? 4. 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?

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

Thanks,

Lance

Was this answer helpful?

1 person found this answer helpful.
0 comments No comments

7 additional answers

Sort by: Most helpful
  1. Anonymous
    2018-02-25T08:33:17+00:00

    Hi Steve,

    Let me know if you need any other assistance.

    Thanks,

    Lance

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2018-02-22T18:08:57+00:00

    Hi Steve,

    Typically, the Domain Type value should be Authoritative. However, if you have properly configured a shared domain, the value may be Internal Relay.  

    An article for your reference: Fix email delivery issues for error code 5.4.1 in Office 365

    Thanks,

    Lance

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2018-02-22T16:51:51+00:00

    Hi Lance,

    We have a couple of domains, including one that is not widely used. I gave the PF an address at that domain, made it the default email address for the PF, and changed the domain in question from Authoritative to Internal Relay.

    External and internal mails tests then worked fine.

    My question is - if I change our main domain from Authoritative to Internal Relay, would that affect our mailflow in any way?

    Thanks,

    Steve

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2018-02-21T15:45:49+00:00

    Hi Lance,

    Thanks for getting back to me.

    1. Yes, it only happens with external users.
    2. Just this specific PF that I know of.
    3. Cloud only.

    I have PM you the NDRs.

    Thanks,

    Steve

    Was this answer helpful?

    0 comments No comments