Australian cloud for business software — built and run in Sydney since 2002

NetLeverage
NetLeverage

Exchange Online "550 5.7.13" or "550 5.7.135": external senders rejected by a mail-enabled public folder

Technical article
Troubleshooting

About this article: This article is reviewed against the cited sources. This is source research, not lab validation. Check the stated versions and your own requirements before making changes.

Microsoft's page says the notification appears "when the recipient is a public folder that's configured to reject messages from external senders (senders from outside the organization)." The codes are 550 5.7.13 and 550 5.7.135. Microsoft's NDR overview names them "Sender was not authenticated for public folder".

Only an email administrator for the recipient's organisation can fix it. The sender cannot, and the recipient's administrator can choose between two settings in the Exchange admin center (EAC): accept mail from all senders, or add named external senders to the folder's allowed list.

What the error means

The sender is told what Microsoft's page says to tell them: only an email administrator in the recipient's organisation can fix the issue, so the sender should contact that administrator and refer them to the information.

A mail-enabled public folder has message delivery restrictions, set in its Mail flow settings in the EAC. Microsoft's page describes the folder in this fault as one "configured to reject messages from external senders". The sending system receives the 550 response and returns the bounce.

Microsoft's NDR overview describes the code: "The recipient address is a public folder that's set up to reject messages sent from outside its organization. Only an email administrator for the recipient's organization can change this configuration."

Other codes mean something else. Microsoft's overview lists 5.7.133, "Sender not authenticated for group", for a group distribution list that rejects outside senders, 5.7.134, "Sender was not authenticated for mailbox", for a mailbox, and 5.7.136, "Sender was not authenticated", for a mail user. Each has its own Microsoft page, and each says the recipient's email administrator, or for a group its owner, must change the configuration. If the recipient on your bounce is a mailbox, group or mail user and not a public folder, a different Microsoft page applies.

Likely causes

Cause What you see How to confirm
The folder's "Accept messages from" is set to authenticated senders only External senders bounce; internal senders deliver In the EAC, open the folder's Mail flow settings and read Message delivery restrictions
The folder uses an allowed senders list that omits the external sender Some external senders deliver, one does not Read the "Only senders in the following list" members
The recipient is not a public folder Code 5.7.136 or a group code Check the recipient type in the EAC

Prove the cause before changing anything

All of these read only.

  1. Read the bounce and note the recipient address, the code (5.7.13 or 5.7.135) and the sender's address.
  2. Confirm the recipient is a public folder. Microsoft says the codes appear only for that.
  3. In the EAC, as an administrator of the recipient's organisation, go to Public folders > Public folders, choose the folder from the list and select Edit. The Mail flow settings area holds Message delivery restrictions > Accept messages from. Read what it says and record it, then close the properties screen without saving.

Microsoft's page names the Exchange admin center and links to "Exchange admin center in Exchange Online" for how to open it.

Example (illustrative): at contoso.com.au the public folder Orders receives supplier order confirmations. A new supplier at fabrikam.com.au gets "550 5.7.135" when mailing it. Internal staff can mail the folder. In the EAC the folder's Accept messages from setting has "Require that all senders are authenticated" ticked and "Only senders in the following list" selected, with only the staff group listed. The supplier is not in the list, which is the second cause in the table.

Fix

Choose one of Microsoft's two methods. The first opens the folder to every sender. The second opens it to chosen external senders only.

Before you change either, write down the folder's current Accept messages from settings: whether "Require that all senders are authenticated" is ticked, which option is selected, and every member of the list. The EAC page gives no export for these settings, so the written record is your saved copy.

Method 1: allow all internal and external senders

Risk: the next steps let every sender outside the organisation send mail to this public folder. Whoever has access to the folder reads what arrives, and the folder no longer filters senders.

Microsoft's steps in the new EAC:

  1. Navigate to Public folders > Public folders.
  2. Choose a public folder from the list, then click Edit. The public folder properties screen appears.
  3. Click Mail flow settings.
  4. Under Message delivery Restrictions > Accept messages from, clear the check box for Require that all senders are authenticated.
  5. Select All senders.
  6. Click Save.

To undo it, repeat the same steps and set the options back to what you wrote down (tick "Require that all senders are authenticated" again, and select the previous option and members), then click Save.

Method 2: use the public folder's allowed senders list

Microsoft's page says you can instead allow all internal senders and "the specified external senders". Its notes:

  • To add an external sender to a public folder's allowed senders list, you must first create a mail contact or a mail user to represent that sender in your organisation.
  • To add everyone in your organisation to the allowed list, create a distribution group or dynamic distribution group that contains everyone, and add that group to the list.
  • The public folder's allowed senders list "is different from the organization's allowed senders list for anti-spam that you manage in the EAC at Protection > Spam filter."

The mail contact or mail user must exist before the steps below. Creating it is its own change in the directory, adds a recipient object, and Microsoft's page gives no steps for it.

Risk: the next steps change who may mail this folder. A wrong entry blocks mail that is delivered today, because the folder will accept only the members you list. A mail contact for an external sender also adds a recipient object to your directory.

Microsoft's steps in the new EAC:

  1. Navigate to Public folders > Public folders.
  2. Choose the public folder from the list and click Edit.
  3. Under Message delivery Restrictions > Accept messages from, clear the check box for Require that all senders are authenticated.
  4. Select Only senders in the following list, then click +. The Select members screen appears.
  5. Check the boxes of the specific external senders and the all-internal-users group you want to add.
  6. Click add, then click OK, then click Save.

To undo it, repeat the steps and restore the options and list you wrote down, then click Save.

Classic EAC

Microsoft's page gives the same two methods for the classic EAC. The save-first record above still applies.

Risk: the next steps change the same delivery restriction as the new EAC steps. Method 1 lets every sender outside the organisation send mail to the public folder, and Method 2 makes the folder accept only the members you list, so a wrong entry blocks mail that is delivered today.

Microsoft's classic EAC steps for Method 1:

  1. Go to Public folders > Public folders, select the public folder from the list and click Edit.
  2. In the properties dialog box, go to Mail flow settings.
  3. In the Accept messages from section, clear the check box for Require that all senders are authenticated.
  4. Select All senders.
  5. Click Save.

Microsoft's classic EAC steps for Method 2:

  1. Go to Public folders > Public folders, select the public folder from the list and click Edit.
  2. In the properties dialog box, go to Mail flow settings.
  3. In the Accept messages from section, clear the check box for Require that all senders are authenticated.
  4. Select Only senders in the following list, then click Add.
  5. In the Select Members dialog box, select the external senders and the "all internal users" group.
  6. Click OK, then click Save.

To undo it, open the same dialog box and set the Accept messages from section back to the options and list you wrote down, then click Save.

Confirm the fix

  • Ask the external sender to send a new message to the folder. The 5.7.13 or 5.7.135 bounce should not return.
  • Open the folder from a mailbox that has access and confirm the message arrived.
  • Re-read Mail flow settings and compare it with what you intended.

What to watch afterwards

  • With Method 1, the folder's mail volume and junk content.
  • With Method 2, new external senders, because each needs a mail contact or mail user and an entry in the list.
  • Whether a similar bounce appears for a mail user or a group, which have their own codes and their own Microsoft pages.
  • The organisation's anti-spam allowed senders list, which Microsoft says is a separate list and does not change this folder's setting.

Risks and limits

These steps have not been run or lab-tested.

Microsoft's page gives only the two EAC methods and says nothing about PowerShell. The new EAC and classic EAC differ in layout. Method 1 removes the sender restriction for every sender, and Method 2 depends on mail contacts that must be created first. Only an administrator of the recipient's organisation can make either change.

Sources