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.
A bounce that carries 550 5.7.124 and the text "Sender not in allowed-senders list" means the distribution group accepts mail only from certain senders and the sender is not on that list. Microsoft gives two fixes for the group owner or email administrator: add the sender to the group's allowed senders, or remove the restriction so anyone can send to the group.
The person who received the bounce can sometimes fix it alone by joining the group. Before you change a group's delivery settings, write down the current sender options and the list of specified senders, so you can put them back.
What the error means
Microsoft's NDR reference describes the code in its table of enhanced status codes. The explanation reads: "The sender doesn't have permission to send to the distribution group because the sender isn't in the group's allowed-senders list. Depending how the group is set up, even the group's owner might have to be added to the allowed sender list in order to send messages to the group."
Microsoft's own page for the code is titled "Fix NDR error "550 5.7.124" or "5.7.124" in Exchange Online". It says you see this automated notification "when the sender isn't specified in the group's allowed senders list (directly or as a member of a group)".
Keep this code apart from 5.7.133. Microsoft lists 5.7.133, "Sender not authenticated for group", as a different code: the group is set up to reject messages from outside its organisation. Here the restriction is a list of named senders, which can apply to internal senders too.
Likely causes
| Cause | What you see | How to confirm |
|---|---|---|
| The group has a list of allowed senders and the sender is not on it | 550 5.7.124 for one sender | The group's Delivery management shows a specified senders list without the sender |
| The sender is a member of a group that should be allowed but is not on the list | Sender is in a team group and still bounces | The specified senders list names individuals, not the team's group |
| The group's owner is not on the list | The owner's own message to the group bounces | The owner's address is not among the specified senders |
| An external sender is not represented in the directory | An outside address bounces | Microsoft says an external sender needs a mail contact or mail user before it can be listed, and none exists |
| A group with more than 5,000 members | Only members can send, and large messages are refused | Microsoft says groups with more than 5,000 members have restrictions applied automatically |
Microsoft's page gives no ranking of these.
Prove the cause before changing anything
All of these only read.
- Copy the exact text from the bounce: the 550 5.7.124 code, the line "Sender not in allowed-senders list" and the group address. Microsoft says the NDR includes instructions for finding the group owner.
- In the new Exchange admin center, go to Recipients > Groups, select the Distribution list tab, select the group, then the Settings tab. Under Delivery management, read the Sender options and the Specified senders. Write down both. Do not select Save.
- Check whether the sender, or a group that contains the sender, is on the list. Microsoft's page says the sender can be allowed "directly or as a member of a group".
- Check the member count. A group with more than 5,000 members automatically has these restrictions: senders must be members, messages need a moderator's approval, and large messages cannot be sent to it.
- If the sender is outside your organisation, check whether a mail contact or mail user represents them. Microsoft's page says one must exist before an external sender can be added to the list.
Example (illustrative): at contoso.com.au the group all-staff@contoso.com.au has Sender options set to allow only specified senders, and the list holds hr01@contoso.com.au and fs01-alerts@contoso.com.au. A manager, a.nguyen@contoso.com.au, gets 550 5.7.124 when she writes to it, as does a supplier at acme.example. The manager is internal and not listed, so she needs adding. The supplier is external, so Microsoft says a mail contact for the supplier is needed before the supplier can be listed. Microsoft's page does not say whether listing the contact is enough with the Sender options value its steps choose.
Fix
The sender can ask to join the group
Microsoft's page says "Typically, members of a group can send messages to the group." It adds that if the group is in your Exchange Online organisation the sender can try to join it in Outlook or Outlook on the web. It adds that the sender may have to wait for the group owner to approve the request before sending. If the group is outside your organisation or does not allow requests to join, the sender has to ask the group owner to add them to the allowed senders list.
Method 1: add the sender to the allowed senders list
Before you change the group, record its current settings. Write down the Sender options value and every name under Specified senders, or take a screenshot of the Delivery management screen, and keep it with the ticket.
Risk: The next steps set Sender options to "Only allow messages from people inside my organization" and add one sender to the list; that sender can then email every member of the group, so confirm the request with the group owner first.
New Exchange admin center, as Microsoft gives it:
- Go to Recipients > Groups and click the Distribution list tab.
- Select the group, then the Settings tab.
- Under Delivery management, click Edit delivery management.
- Under Sender options, choose Only allow messages from people inside my organization.
- Under Specified senders, click the text box, choose the sender from the list, and confirm the sender's name shows below the box.
- Click Save changes.
Classic Exchange admin center: go to Recipients > Groups, select the group and click Edit. In Delivery management click Add, select the sender or a group the sender belongs to in the Select Allowed Senders dialog box, add it, then click OK and Save.
To add an external sender, Microsoft's page says you must first create a mail contact or a mail user to represent the sender in your organisation. The page gives no steps for creating one, none are set out here, and it does not say which Sender options value an external sender needs. Creating a contact adds a directory object that stays until someone removes it.
To undo it: open the same Delivery management screen, set Sender options back to the value you wrote down, remove the sender you added from Specified senders so the list matches your record, and click Save changes.
Method 2: let everyone send to the group
If the group does not need a restriction, Microsoft says you can remove the restrictions so anyone can send messages to it.
Before the change, record the Sender options value and the full list of Specified senders as in Method 1.
Risk: The next steps remove the restriction on who can send to the group. After the change any internal or external sender can email every member. Use it only for groups meant to be open, such as a public contact address.
New Exchange admin center:
- Go to Recipients > Groups and click the Distribution list tab.
- Select the group, then the Settings tab.
- Under Delivery management, click Edit delivery management.
- Under Sender options, choose Allow messages from people inside and outside my organization.
- Click Save changes.
Classic Exchange admin center: go to Recipients > Groups, select the group, click Edit and go to Delivery management. In the Distribution Group box, select Delivery management, remove every entry in the allowed senders list (select one entry, press CTRL + A, then click Remove), select Senders inside and outside of my organization and click Save.
To undo it: open Delivery management again, choose the Sender options value you recorded, add back each name from your record under Specified senders, and click Save changes.
Confirm the fix
- Ask the sender to send a new message to the group. A forwarded copy of the old bounce does not test anything.
- Check that an address that should not be able to send is still refused, if you used Method 1.
- Keep the saved record until the group owner has confirmed the list is right.
What to watch afterwards
- New bounces from the same group. Microsoft says the list can contain a sender directly or through a group, so a changed membership can change who is allowed.
- Mail from senders you did not expect arriving on the group address, if you used Method 2.
- Group growth past 5,000 members, which triggers the automatic restrictions Microsoft describes.
Read next
Related articles you may want next.
- TroubleshootingExchange Online 'Fix NDR error 550 5.7.133': outside senders can't email a distribution group550 5.7.133 means a distribution group rejects outside senders. Allow external mail or add named senders to the allowed list, and see each risk.Read article
- TroubleshootingExchange Online 550 5.2.3 "message too large for this recipient": the size limits and where to change themExchange Online 550 5.2.3 RecipSizeLimit, message too large for this recipient. Check both limits, allow for encoding, change one mailbox.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
Risks and limits
These steps have not been run or lab-tested.
Microsoft's page gives no step that lifts the automatic restrictions on a group of more than 5,000 members. It names Exchange Online and gives menu paths for the new and the classic Exchange admin center only. It gives no Exchange Online PowerShell command for this setting, so none is shown. Microsoft's page does not describe Microsoft 365 groups or dynamic distribution groups, and the steps above are for the distribution list tab it names. A restriction set by a mail flow rule is a different matter, and Microsoft's page does not describe it.
Sources
- Fix NDR error "550 5.7.124" or "5.7.124" in Exchange Online — Microsoft Learn, page dated 2026-08-11, accessed 22 November 2026
- Email nondelivery reports (NDRs) and SMTP errors in Exchange Online — Microsoft Learn, page dated 2026-08-24, accessed 22 November 2026
This article was originally published on .