Bounce codes › Microsoft 365
550 5.7.133: Sender not authenticated for group
You wrote to a group address that only accepts mail from people inside its own organisation. Your email, domain and SPF are fine. The group simply does not take outside mail.
If you sent the email: only the group owner or their IT can change this, so write to a person instead or ask them. If you manage the group: see the admin steps.
I sent the email I manage the group
Only the recipient side can fix it Refused by a rule on the recipient side
This group address only accepts mail from inside its own organisation.
- Sent by: Microsoft 365 / Outlook
- Permanent (hard bounce). Sending the same message again fails again.
How Microsoft 365 words it (source):
Sender not authenticated for group
Why the group refused you
- The address is an internal distribution list such as
team@orsales-emea@. - The organisation never switched on "allow external senders" for the group.
How the bounce looks
Look for 5.7.133 or SenderNotAuthenticatedForGroup. The rest of the text changes with the email program:
| Where you see it | What it looks like (roughly) |
|---|---|
| Outlook and Microsoft 365 | "Your message to … couldn't be delivered." Then a line that the group only accepts messages from people in its organization or on its allowed senders list. In the server details: 550 5.7.133 RESOLVER.RST.SenderNotAuthenticatedForGroup; authentication required |
| Gmail | "Message not delivered" or "Address not found", then "The response from the remote server was:" and the same 550 5.7.133 line |
| Mailchimp, Brevo, SendGrid and other sending services | A hard bounce with a reason such as smtp; 550 5.7.133 RESOLVER.RST.SenderNotAuthenticatedForGroup |
Often the bounce adds [Sender was not authenticated, but delivery requires authentication] and a server name ending in prod.outlook.com. That is the same error, not a second one.
Group addresses look like team@, sales@, all-staff@, hr-uk@ or board@. A personal address (jane.smith@) does not give this code; the same rule on a single mailbox is 550 5.7.134.
If you sent the email
- Write to a person, not the group. If you know one member, send it to them and ask them to pass it on.
- If the group should take outside mail (a
support@,info@ororders@address on their website), tell the company. They have to change the group's settings. Use the message for their IT below. - Do not keep sending. Each new message fails the same way. Nothing you change on your side (SPF, DKIM, another IP, another email service) gets you through.
- Remove the address from mailing lists. A closed group bounces every campaign, and hard bounces count against your sender reputation. Before the next send, check the whole list for other dead addresses.
It is not a spam block
This bounce does not mean Microsoft or the company thinks you are a spammer. A Microsoft 365 group is closed to outside senders unless its owner opens it. Blocks against you as a sender come with other codes, such as 550 5.7.606 (banned IP) or 550 5.7.509 (DMARC failed).
Inside the company and still bounced
If you work at the company that owns the group, Microsoft 365 still saw your message as outside mail. It only counts you as inside when you send from your work mailbox, signed in. Common reasons:
| What happened | What to do |
|---|---|
| You sent from a personal address (Gmail, Outlook.com), or from a work address at another company | Send from your work mailbox in Outlook or Outlook on the web. |
| A printer, scanner or app sends to the group without signing in | Ask IT to set it up with a signed-in (authenticated) SMTP account, or to add it to the group's allowed senders. |
| A tool such as a CRM, ticket system or form builder sends "from" your company address through its own servers | The group sees an outside sender. IT can add that sender to the allowed list, or let the tool send through your Microsoft 365. |
| A message was forwarded or redirected from outside to the group | The forwarder is the outside sender. Forward it from your work mailbox instead. |
Ask the company to let you in
Send this to your contact there, or to their IT. Fill in the group address:
Hi, my email to your group address [group address] bounced with: 550 5.7.133 RESOLVER.RST.SenderNotAuthenticatedForGroup The group only accepts mail from inside your organization. If it should get mail from outside (customers, partners), the group owner or your email admin can allow external senders in the group's delivery settings, or add my address to its allowed senders. Microsoft's steps: https://learn.microsoft.com/en-us/troubleshoot/exchange/email-delivery/ndr/fix-error-code-5-7-133-in-exchange-online
If you manage the group
Microsoft gives two ways. Choose by who should be able to write to the group.
Way 1: allow everyone, inside and outside
- Open the Exchange admin center and go to Recipients > Groups.
- Click 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, then Save changes.
Way 2: allow only some outside senders
- First create a mail contact (or mail user) for each outside sender. The allowed list can only hold recipients your organization knows.
- In the same Delivery management screen, choose Allow messages from people inside and outside my organization.
- Under Specified senders, add the contacts, then Save changes. Add a group that holds all your staff too, or your own people are blocked.
The group's allowed senders are not the same as the anti-spam allow list under Protection > Spam filter. Adding the sender there does not fix 5.7.133.
In PowerShell
The switch behind "inside my organization only" is RequireSenderAuthenticationEnabled. Set it to $false with Set-DistributionGroup for a distribution list, or with Set-UnifiedGroup for a Microsoft 365 group. For a Microsoft 365 group the owner can often change it in Outlook on the web too, in the group settings ("Let people outside the organization email the group").
Full article: Fix NDR error 550 5.7.133 in Exchange Online (Microsoft Learn).
Not the same as
| Code | What it means | Whose move |
|---|---|---|
| 550 5.7.124 | The group has a named list of allowed senders, and you are not on it. | The group owner |
550 5.7.134 | The same rule as 5.7.133, on a single mailbox instead of a group. | The mailbox owner or their IT |
550 5.7.13 / 5.7.135 | The same rule on a public folder. | Their IT |
| 550 5.7.520 | A forward to an outside address was blocked by the sender's own company. | Your IT |
| 550 5.4.1 | The address does not exist in that company at all. | You: remove the address |
Questions
What does 550 5.7.133 mean?
The address is a group (a distribution list or a Microsoft 365 group) that only takes mail from people inside its own organisation. Your message came from outside, so Microsoft 365 refused it.
Does the address exist?
Yes. It is a working group, closed to outsiders.
Can I fix it from my side?
No. Only the group owner or an email admin at the recipient's organisation can open the group to external senders. Send them the message for their IT.
I work at the same company. Why do I get it?
Because your message reached Microsoft 365 as outside mail: sent from a personal account, from a printer or app that does not sign in, or through an outside sending service. See Inside the company and still bounced.
Is it a hard bounce?
Yes. Every new message to that group fails the same way until its settings change. Sending again does not help.
Is it a spam block or a problem with my domain?
No. Your SPF, DKIM, IP and domain are not the issue. The group rejects all outside senders, whoever they are.
Should the address stay on my mailing list?
No. A closed group bounces every campaign. Remove it, or write to a person at the company instead.
Got a different bounce?
Paste the whole message into the bounce code lookup. It reads the code and the words and tells you whose move it is.
Related codes
550 5.7.124Sender not in allowed-senders list (Microsoft 365)550 5.7.520Your organization does not allow external forwarding (Microsoft 365)550 5.4.1Recipient address rejected: Access denied (Microsoft 365)
Free tools
Checked on 8 Nov 2026 against Microsoft Learn: Fix NDR error 5.7.133 in Exchange Online (updated 10 Aug 2026). The bounce wording in each email program is shown roughly and can differ by version.