Skip to content

Est. 2011·Microsoft Partner ID 7033487·Delivery under 3 min·Support 7 days a week

Your vault is empty.

Free Fix 550 5.7.124

550 5.7.124: the sender is not on the group’s allowed senders list

10 min read Updated October 5, 2026 Exchange Server

Fix it now

Microsoft publishes 5.7.124 as sender not in allowed-senders list: a distribution group is configured to accept mail only from named senders, and this one is not among them. Add the sender to the list, or open the group up deliberately.

Run these in the Exchange Management Shell or Exchange Online PowerShell, in order

Get-Recipient -Identity group@contoso.com | Format-List Name,RecipientType
Get-DistributionGroup 'All Staff' | Format-List AcceptMessagesOnlyFromSendersOrMembers,RejectMessagesFromSendersOrMembers,RequireSenderAuthenticationEnabled,ModerationEnabled
Set-DistributionGroup 'All Staff' -AcceptMessagesOnlyFromSendersOrMembers @{Add='sender@contoso.com'}
  1. Read the accept list in full before you change it, so you know what you are preserving. The Add form extends the list; assigning a plain value replaces it.
  2. In the new Exchange admin centre the same setting is at Recipients, then Groups, then the Distribution list tab, then the group, then Settings, then Delivery management, then Edit delivery management.
  3. If external senders should be able to write to the group, choose Allow messages from people inside and outside my organisation, or clear RequireSenderAuthenticationEnabled.
  4. An external sender has to exist as a mail contact or mail user before it can be added to an allowed senders list.

Even the group’s owner can need to be on the allowed senders list, depending on how the group was set up. Do not assume ownership implies permission to post.

If the sender’s test message now reaches the group you can stop. If the bounce carries a different code, the next section explains which setting produces which.

Why it happens

Restrictions in this family live on the recipient object, not on the route, which is why nothing you can change in mail flow, DNS or filtering will explain them. Every mailbox, group and mail-enabled object can carry a list of senders it accepts mail from and a list it refuses. When an accept list exists it is exclusive: anybody not on it is rejected, including senders who were fine yesterday. Adding a single entry to an empty list is enough to break a working configuration.

The useful part is that the four codes in this family are not interchangeable, and Microsoft publishes different causes for each. 5.7.124 is the group’s allowed senders list. 5.7.12 is the separate setting that requires senders to be authenticated, and it applies to mailboxes, groups, mail users and shared mailboxes alike. 5.7.60 is not a recipient restriction at all: it is the submitting account being told it may not use the From address it presented. 5.1.0 is the sender address itself failing to resolve or being filtered.

Reading the code before you start clicking saves the most time here, because two of the four are configured on the recipient and two are not.

The group accepts mail only from an approved list

You have this one if The bounce carries 5.7.124, and everyone already on the list can write to the group normally.

  1. Read the current list first: Get-DistributionGroup 'All Staff' | Format-List AcceptMessagesOnlyFromSendersOrMembers.
  2. Add the sender with the Add form: Set-DistributionGroup 'All Staff' -AcceptMessagesOnlyFromSendersOrMembers @{Add='sender@contoso.com'}.
  3. Where many senders need access, add a group to the list and manage membership there instead of adding addresses one at a time.
  4. Retest, and confirm the senders who could already post still can.

Setting the property to an empty value removes the restriction entirely and lets anyone write to the group. That is sometimes correct and sometimes very much not. Decide deliberately.

The recipient requires senders to be authenticated

You have this one if The bounce carries 5.7.12. Internal mail is delivered and anything from outside the organisation bounces.

  1. Microsoft’s documented cause is the Require senders to be authenticated setting on the recipient, which can be a mailbox, a group, a mail user or a shared mailbox.
  2. For a mailbox, clear it at Recipients, then Mailboxes, then the mailbox, then Mail flow settings, then Manage mail flow settings, then the Message delivery restriction pane, then Edit.
  3. For a group, choose Allow messages from people inside and outside my organisation under Delivery management, or run Set-DistributionGroup 'Support' -RequireSenderAuthenticationEnabled $false.
  4. Test from a genuinely external mailbox, not from a second internal account.

Many groups are meant to refuse external mail and the restriction is protecting you. If the group has to be publicly addressable, moderation is usually a better answer than opening it.

The account has no right to send as the address it used

You have this one if The bounce carries 5.7.60, and it affects an application or a user working from a shared address rather than everyone writing to one recipient.

  1. Microsoft publishes 5.7.60 as the client not having permission to send as this sender, which is a Send As problem, not a delivery restriction.
  2. In Exchange Online: Add-RecipientPermission 'Shared Mailbox' -AccessRights SendAs -Trustee user@contoso.com.
  3. On premises the equivalent is Add-ADPermission 'Shared Mailbox' -User 'CONTOSO\user' -ExtendedRights 'Send As'.
  4. If recipients should see that the message was sent on behalf of the mailbox, use Set-Mailbox 'Shared Mailbox' -GrantSendOnBehalfTo user instead.

Adding the address as an alias changes nothing. An alias makes an address deliverable; it grants nobody the right to send from it.

Moderation is enabled and nothing is being approved

You have this one if Messages neither arrive nor bounce promptly, and the group has moderation configured.

  1. Check who is moderating: Get-DistributionGroup 'All Staff' | Format-List ModerationEnabled,ModeratedBy,BypassModerationFromSendersOrMembers,SendModerationNotifications.
  2. Confirm the moderators still exist and still work there. A group moderated by a leaver swallows everything silently.
  3. Add senders who should not need approval to the bypass list rather than turning moderation off.
  4. Test end to end, including the approval step.

Full reference

Which setting produces which code

Code Published meaning Where the setting lives
5.7.124 Sender not in allowed-senders list AcceptMessagesOnlyFromSendersOrMembers on a distribution group
5.7.12 Sender was not authenticated by organization Require senders to be authenticated, on a mailbox, group, mail user or shared mailbox
5.7.60 Client does not have permissions to send as this sender Send As permission on the mailbox named in the From address
5.1.0 Sender denied The sender address cannot be resolved, or sender filtering rejected it

Microsoft documents 5.7.124 against distribution groups. If a mailbox is refusing an external sender, expect 5.7.12 in Exchange Online or 5.7.1 on Exchange Server, and look at the authentication requirement rather than an allowed senders list.

Reading a restriction without changing it

Reading the accept, reject, authentication and moderation properties is entirely non-destructive, and you should always read them before writing to them. The mistake that costs the most is assigning a new value where you meant to extend the existing one, which silently drops every entry that was already there and produces a second, larger incident an hour later.

Read before you write

Get-DistributionGroup 'All Staff' | Format-List AcceptMessagesOnlyFromSendersOrMembers,RejectMessagesFromSendersOrMembers,RequireSenderAuthenticationEnabled,ModerationEnabled,ModeratedBy,BypassModerationFromSendersOrMembers
Get-Mailbox user | Format-List AcceptMessagesOnlyFromSendersOrMembers,RejectMessagesFromSendersOrMembers,RequireSenderAuthenticationEnabled

External senders on an allowed list

Microsoft’s documented step is that an external sender must first exist as a mail contact or a mail user in your organisation before it can be added to a group’s allowed senders list. There is nowhere to put a bare external address, which is why the admin centre appears to lose the entry when you try. Create the contact, then add it.

Send As and Send on Behalf are not the same thing

  • Send As shows only the mailbox address to recipients. The message looks as though the mailbox sent it.
  • Send on Behalf shows both identities. Recipients see that a named person sent it for the mailbox.
  • Choose according to what recipients should see, not according to which is easier to configure.
  • Permission changes are not always instant. Allow time for them to take effect before concluding they did not work.

When the configuration looks right and mail still bounces

  • Confirm you are looking at the object that was actually addressed. A message to an alias of a different group will show you a perfectly configured group that has nothing to do with the failure.
  • Check whether the sending address is what you think. An application authenticating as one account and setting a different From address is the classic 5.7.60 shape.
  • Check for a reject list as well as an accept list. A single entry on RejectMessagesFromSendersOrMembers blocks one sender while everyone else works.
  • Look at group membership if the accept list contains groups. Membership changes and directory sync both alter who is allowed without anyone touching the group’s own properties.

Every code this article covers

Code What it points at Source
550 5.7.124 Sender not in allowed-senders list: the sender is not in the recipient group’s allowed senders list, directly or as a member of a group that is Microsoft Learn
550 5.7.12 Sender was not authenticated by organization: the recipient is set to reject messages sent from outside its organisation Microsoft Learn
550 5.7.60 Client does not have permissions to send as this sender: the authenticating account lacks Send As on the From address Microsoft Learn
550 5.1.0 Sender denied: the sender address could not be resolved, or sender filtering rejected it Microsoft Learn

Confirm the fix worked

  1. The previously blocked sender’s test message is delivered and appears with a DELIVER event in the tracking log.
  2. The accept and reject properties contain exactly the entries you intended, with nothing lost from the original list.
  3. External senders can reach the group if that was the goal, tested from outside the organisation.
  4. For a Send As change, a message sent from the shared address arrives showing the address you expect in the From field.

Questions people ask about this

Is there anything to buy here?

No. Every setting involved is a property on a recipient object or a permission, and changing them costs nothing. If someone suggests a licence fixes a delivery restriction, they have misread the bounce.

I got 5.7.124 sending to a mailbox, not a group. What now?

Microsoft documents 5.7.124 against a group’s allowed senders list. For a mailbox refusing external mail, expect 5.7.12 in Exchange Online or 5.7.1 on Exchange Server, and look at the authentication requirement and the accept list on that mailbox.

Why did this start when nothing changed?

Something did change, but probably not on the mail system. A group recreated by a script, a membership sync, or a permission removed during an access review will all produce this on a configuration that worked for years.

Adding the address as an alias did not help. Why?

An alias makes an address deliverable to a mailbox. It does not grant anyone the right to send from it. Sending as another address requires an explicit permission, which is a separate thing entirely.

Do group owners always get to post to their own group?

No. Microsoft’s own guidance notes that depending on how the group is set up, even the owner might have to be added to the allowed senders list. Check the list rather than assuming.

Related error codes

Was this article helpful?

Your feedback helps us improve our documentation.

Related articles

Free Fix Event ID 1053: ActiveSync lacks permission to create the device container Free Fix HTTP 500.19 on Exchange virtual directories: broken IIS configuration files Free Fix Event ID 12014: Exchange cannot find a transport certificate for this domain Free Fix 550 5.7.509: your mail fails DMARC so the receiver rejects it outright
← Back to Knowledge Base