Why Exchange Online bounces mail to a group, mailbox, mail user or public folder with 5.7.133, 5.7.124, 5.7.134, 5.7.135 or 5.7.136, and how to allow external or specific senders in the EAC or PowerShell.
Home › Guides › Exchange Online 5.7.133 and 5.7.124
Last updated 17 November 2026
These codes all mean the recipient is configured to reject the sender, not that anything is wrong with the sender's domain. Normally only the group owner or an email admin in the recipient's organization can fix them (for 5.7.124 a sender can sometimes join the group). From Microsoft's Exchange Online NDR reference:
| Code | Text | Recipient and cause |
|---|---|---|
| 5.7.124 | Sender not in allowed-senders list | Distribution group; the sender isn't in the group's allowed senders list. Depending on the setup, even the group's owner might need to be on it. |
| 5.7.133 | Sender not authenticated for group | Distribution group set to reject messages from outside the organization. |
| 5.7.134 | Sender was not authenticated for mailbox | Mailbox set to reject messages from outside the organization. |
| 5.7.13 or 135 | Sender was not authenticated for public folder | Public folder set to reject messages from outside the organization. |
| 5.7.136 | Sender was not authenticated | Mail user set to reject messages from outside the organization. |
| 5.7.12 | Sender was not authenticated by organization | Recipient address set to reject messages sent from outside its organization. |
Microsoft's articles title these errors with 550 (for example "550 5.7.133"). Its separate troubleshooting article for 5.7.12 has been retired, so the reference entry above is the current description.
Every recipient type has the same two fixes: allow all external senders, or keep the restriction and add specific senders to the recipient's allowed senders list.
For 5.7.133, 5.7.134, 5.7.135 and 5.7.136 Microsoft says only the recipient's group owner or email admin can fix the issue, so send them the NDR. For 5.7.124 on a group inside your own organization, try to join the group in Outlook or Outlook on the web; you might have to wait for the owner to approve the request. If the group is in another organization or doesn't allow join requests, ask the owner to add you to the allowed senders list. The NDR tells you how to find the owner.
In the new EAC:
Microsoft notes that Only allow messages from people inside my organization is the default for distribution lists. In PowerShell:
Set-DistributionGroup -Identity "Support" -RequireSenderAuthenticationEnabled $false
RequireSenderAuthenticationEnabled $true accepts messages only from authenticated (internal) senders; $false accepts internal and external senders. Check the current settings with:
Get-DistributionGroup -Identity "Support" | Format-List RequireSenderAuthenticationEnabled,AcceptMessagesOnlyFromSendersOrMembers,ModerationEnabled
For a Microsoft 365 group, Set-UnifiedGroup has the same RequireSenderAuthenticationEnabled parameter. Microsoft's NDR articles are written for distribution lists and don't say which code a Microsoft 365 group returns.
New-MailContact -Name "Debra Garcia" -ExternalEmailAddress dgarcia@tailspintoys.com -Alias dgarcia.Things Microsoft calls out:
In PowerShell, add or remove senders without overwriting the existing list:
Set-DistributionGroup -Identity "Support" -AcceptMessagesOnlyFrom @{Add="dgarcia"}
Set-DistributionGroup -Identity "Support" -AcceptMessagesOnlyFromDLMembers @{Add="All Staff"}
AcceptMessagesOnlyFromSendersOrMembers sets individual senders and groups together but overwrites the list, and it can't be used in the same command as AcceptMessagesOnlyFrom or AcceptMessagesOnlyFromDLMembers. Blank ($null) means the group accepts messages from all senders.
| Recipient | EAC path | PowerShell |
|---|---|---|
| Mailbox (5.7.134) | Recipients > Mailboxes, select the mailbox, Manage message delivery restriction, clear Require senders to be authenticated, Save | Set-Mailbox -Identity <user> -RequireSenderAuthenticationEnabled $false |
| Mail user (5.7.136) | Recipients > Contacts, select the mail user, Edit, Mailbox flow settings, View details under Message Delivery Restrictions, clear Require that all senders are authenticated, select All senders, OK, Save | Set-MailUser -Identity <user> -RequireSenderAuthenticationEnabled $false |
| Public folder (5.7.13 or 5.7.135) | Public folders > Public folders, select the folder, Edit, Mail flow settings, under Message delivery Restrictions > Accept messages from clear Require that all senders are authenticated, select All senders, Save | Set-MailPublicFolder -Identity <folder> -RequireSenderAuthenticationEnabled $false |
To allow only some external senders instead, clear the authentication check box and choose Selected senders (mailbox) or Only senders in the following list (mail user, public folder), then add mail contacts for the external senders plus a group that contains all internal users. An external sender writing to a restricted public folder can also see 550 5.7.1 RESOLVER.RST.AuthRequired; authentication required [Stage: CreateMessage]; see the 550 5.7.1 guide.
Microsoft's 5.7.124 article says groups with more than 5,000 members automatically get these restrictions: senders must be members of the group, messages need a moderator's approval, and large messages can't be sent (those get a different NDR). Moderation for any group can be set in the EAC under Message approval or in PowerShell, as in Microsoft's example:
Set-DistributionGroup -Identity "Customer Support" -ModeratedBy "Amy" -ModerationEnabled $true -SendModerationNotifications 'Internal'
If moderation is on and no moderator is set, messages go to the group owners for approval. Use Add senders who don't require message approval (BypassModerationFromSendersOrMembers) for trusted senders.
Need SPF, DMARC and MX checks across a whole client list? Run the Bulk SPF / DMARC / MX Auditor on Apify ($2 per 1,000 domains).
Read the NDR in the Email Header Analyzer, keep the cmdlets in the PowerShell Cheat Sheet, confirm the tenant with the M365 Tenant Lookup, check the recipient domain with the MX Record Lookup and the sending domain with the Email Deliverability Checker and DMARC Record Checker. Related guides: Exchange Online 550 5.7.1, Exchange Online 550 5.7.520, Exchange Online 550 5.1.10 and Exchange Online 5.2.2.
Microsoft says the recipient is a distribution group set to reject messages from senders outside the organization. Only the group owner or an email admin can fix it, by allowing people inside and outside the organization or by adding the sender to the group's allowed senders list.
The distribution group has an allowed senders list and the sender isn't on it, directly or through a group. Depending on the setup, even the group's owner might need to be added. Add the sender, or a mail contact for an external sender, under Delivery management.
In the EAC open Recipients, Groups, Distribution list, select the group, then Settings, Edit delivery management, and choose Allow messages from people inside and outside my organization. In PowerShell run Set-DistributionGroup with -RequireSenderAuthenticationEnabled $false.
Microsoft notes that if the group allows only senders inside your organization, mail from a mail contact is rejected even when it's on the list. Change the sender option to allow people inside and outside the organization as well.
The same restriction on other recipient types: 5.7.134 is a mailbox, 5.7.13 or 5.7.135 is a public folder and 5.7.136 is a mail user, each set to reject senders from outside the organization. Clear Require senders to be authenticated, or use RequireSenderAuthenticationEnabled $false.
Runbooks, checklists and helpdesk templates: IT Admin Packs on Gumroad.