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.
If someone outside your organisation gets a bounce with 550 5.7.133 when emailing a distribution group, the group is set to reject mail from outside senders. Microsoft says this notification appears "when the recipient is a group that's configured to reject messages from external senders who are from outside the organization". Only the group owner or an email admin in the recipient's organisation can change it. The sender cannot fix it from their side.
There are two documented fixes: allow messages from people inside and outside the organisation, or keep the group closed and name the external senders who may use it. They carry different risks, set out below.
What the error means
The NDR (non-delivery report, or bounce) names a group as the recipient. The group's delivery management setting is what rejects the message, so the sender's mailbox, domain and message are not the place to look.
If you are the person who got the bounce, Microsoft's advice is to contact the group owner or an email admin in the recipient's organisation and refer them to the fix. Forward the full bounce text with the date and time you sent it. Retrying the same message cannot succeed while the setting is unchanged. If you are the group owner or admin, the sections below are for you.
For distribution groups in the Exchange admin center, Microsoft's group page lists three sender options. "Only allow messages from people inside my organization" means a message from outside the organisation is rejected, and Microsoft states this is the default setting. "Allow messages from people inside and outside my organization" lets anyone, including people on the Internet, send to the group. "Specified senders" narrows the group further: if you add senders to that list, they are the only ones who can send mail to the group, and mail from anyone not on the list is rejected.
In PowerShell the equivalent setting is RequireSenderAuthenticationEnabled: per the Set-DistributionGroup reference, $true accepts messages only from authenticated (internal) senders, and $false accepts messages from authenticated (internal) and unauthenticated (external) senders. Read it before you change anything.
Likely causes
| Cause | What you see | How to confirm |
|---|---|---|
| Group accepts only inside senders (the default) | 550 5.7.133 for every external sender | Delivery management shows "Only allow messages from people inside my organization" |
| Allowed senders list names only some senders | One external sender is rejected while another is accepted | The sender is missing from Specified senders |
| External sender is represented by a mail contact while the group is inside-only | Bounce persists even after the contact was added | The group is set to inside-only; Microsoft says mail from a mail contact is then rejected even if added to the list |
| Sender address does not match the entry in the list | Bounce for a sender who is listed | Microsoft's note: the address must match the 'Reply to' field, not the 'From' field |
Prove the cause before changing anything
Read the group's current setting first. In Exchange Online PowerShell:
Get-DistributionGroup -Identity "sales@contoso.com.au" | Format-List RequireSenderAuthenticationEnabled,AcceptMessagesOnlyFrom,AcceptMessagesOnlyFromDLMembers,AcceptMessagesOnlyFromSendersOrMembers | Out-File -FilePath .\sales-group-before.txt
Open sales-group-before.txt. RequireSenderAuthenticationEnabled set to True means inside senders only. The three AcceptMessagesOnlyFrom properties hold the allowed senders list (individual senders, group members, or both), and any entry there means the group is already restricted to those senders. Keep the file: both methods below use it as the record to go back to.
Then compare against the bounce. Ask the sender for the full bounce text and the exact address they sent from, because the list entry has to match that address. Confirm that the group named in the bounce is the group you are about to change, so you do not alter the wrong one.
You can also open the group in the Exchange admin center: Recipients, then Groups, select the group, then the Settings tab, then Edit delivery management. The sender options are on that screen.
Example (illustrative): the group sales@contoso.com.au has 40 members and is inside-only. Six external partners need to email it. Under Method 2 the allowed senders list needs a mail contact for each of the 6 partners, plus one entry for a group that contains all staff so internal senders keep access. That is 6 + 1 = 7 entries. Method 1 would need none, but would let anyone on the Internet send to 40 mailboxes.
Fix
Microsoft's page names the two methods. Choose by who needs to write to the group. A group meant to take enquiries from any customer, such as a general sales address, suits Method 1. A group that only a handful of partners should reach suits Method 2. If you are unsure, start with Method 2 for the named partners and widen later, because narrowing a group after it has been open to the Internet cannot undo mail that has already arrived.
Method 1: allow all internal and external senders.
Risk: the portal steps below make the group accept mail from anyone, including the Internet. Everyone in the group receives whatever arrives.
In the Exchange admin center, go to Recipients, then Groups, select the group and open the Settings tab. Under Delivery management select Edit delivery management. Under Sender options choose "Allow messages from people inside and outside my organization", then select Save changes.
To undo it: return to the same screen and choose "Only allow messages from people inside my organization", then save. In PowerShell, set the value you recorded:
Set-DistributionGroup -Identity "sales@contoso.com.au" -RequireSenderAuthenticationEnabled $true
Method 2: use the group's allowed senders list.
Save first: record the address of the mail contact you create below.
Risk: the first note below has you create a mail contact, which adds an object to your directory.
Microsoft says this lets you selectively allow messages from internal senders and named external ones. It has notes that matter:
- To add an external sender to the list, first create a mail contact or a mail user to represent them in your organisation.
- To add everyone inside your organisation, create a distribution group or dynamic distribution group that contains everyone and add it to the list.
- The group's allowed senders list is a different list from the organisation-wide allowed senders for anti-spam, which is under Protection and Spam filter.
To undo it, delete the contact you created.
Disruptive step: because the list is exclusive, adding only external senders blocks internal senders who are not on it. Microsoft's group page says that once senders are added, they are the only ones who can send. Include the all-staff group in the same change. This method changes two things: the sender option moves from "Only allow messages from people inside my organization" to inside and outside, and the list gains entries. Save-first: sales-group-before.txt from the read-only step holds the sender option and the list as they were. Back-out needs both reversals, because removing only the entries would leave the group open to anyone on the Internet. In the group's delivery management, remove the entries you added, set the sender option back to "Only allow messages from people inside my organization" and save. In PowerShell the second part is Set-DistributionGroup -Identity "sales@contoso.com.au" -RequireSenderAuthenticationEnabled $true, using the value recorded in the file. If the file showed a list before you started, put those entries back.
Steps: open the group's delivery management as above, choose "Allow messages from people inside and outside my organization", select the text box under Specified senders, choose the senders and select Save changes.
If your group is also meant to receive mail from a mail contact while inside-only, Microsoft states that this does not work, so Method 1 or the list route is the only choice.
Confirm the fix
Ask the external sender to send a new message, not to resend the bounced one, from the exact address you added. Check that the group receives it. Run a message trace in the Exchange admin center under Mail flow, then Message trace, and look for a delivered status. Check an internal sender also still reaches the group, and test with one external sender who is not on the list if you used Method 2, because that message should still be rejected. A rejection there shows the list is doing its job.
What to watch afterwards
- Unwanted mail arriving at a group that was made open to everyone. Method 2 is the way to narrow it again.
- Staff who stop receiving mail from colleagues after the list was changed, which signals the all-staff entry is missing.
- New external partners who will need adding to the list.
- Mail contacts whose sender address changes.
Read next
Related articles you may want next.
- Troubleshooting550 5.1.10 RESOLVER.ADR.RecipientNotFound: a Microsoft 365 user can't email a hybrid user whose address existsMicrosoft 365 user gets 550 5.1.10 RESOLVER.ADR.RecipientNotFound sending to a hybrid user? Check the on-premises object and ExchangeGuid, then fix.Read article
- TroubleshootingExchange Online '5.7.520 Access denied, Your organization does not allow external forwarding': what changed and how to allow it safely5.7.520 Access denied: external forwarding is blocked by an outbound spam policy. Find the policy, then allow forwarding for named users only.Read article
- TroubleshootingScanner or app can't send through Microsoft 365: '535 5.7.3 Authentication unsuccessful' and SMTP AUTH settingsScanner or app can't send via Microsoft 365 (535 5.7.3 or 5.7.57)? Check SMTP AUTH on the mailbox and tenant, then choose SMTP AUTH, relay or Direct Send.Read article
Risks and limits
These commands have not been run or lab-tested. Microsoft's NDR page gives portal steps only. The PowerShell lines here use the Get-DistributionGroup and Set-DistributionGroup reference pages and the RequireSenderAuthenticationEnabled parameter documented there. Microsoft's NDR page describes the list as allowing all internal senders plus the specified external ones, while its group management page says that if you add senders to the list, they are the only ones who can send mail to the group. Add the all-staff group to the list explicitly so internal senders keep access. Opening a group to the Internet increases the mail it can receive from strangers. The steps cover Exchange Online distribution groups only. Microsoft 365 Groups and other group types have their own settings that the NDR page does not describe.
Sources
- Fix NDR error "550 5.7.133" in Exchange Online — Microsoft Learn, page dated 2026-08-11, accessed 20 November 2026
- Create and manage distribution groups in Exchange Online — Microsoft Learn, page dated 2026-08-21, accessed 20 November 2026
- Get-DistributionGroup — Microsoft Learn, date not shown, accessed 20 November 2026
- Set-DistributionGroup — Microsoft Learn, date not shown, accessed 20 November 2026
- Out-File — Microsoft Learn, date not shown, accessed 20 November 2026
- Find and fix email delivery issues as a Microsoft 365 for business admin — Microsoft Learn, page dated 2025-06-25, accessed 20 November 2026
This article was originally published on .