Home › Exchange Online › 5.7.133

Exchange Online · 5.7.133 · Windows 11 22H2

Exchange Online Error 5.7.133 Windows 11 22H2 Sender Not Approved

Error due to sender not being authenticated or approved for a distribution group; fix by updating distribution group settings.

Error Details

FactValueSourceNote
Exact error string5.7.133 - Sender not approved to send to distribution group.Event Viewer -> Application Log-> Event ID
Affected OS build rangeWindows 10 and Windows 11Microsoft Learn documentation
Registry key or OMA-URI involvedNone directly applicable, but related to Exchange Online settings.Intune configuration policies-> Not a registry setting
Relevant service/endpoint URLhttps://outlook.office365.com/EWS/Exchange.asmxMicrosoft documentation
Log line signatureEvent ID: 1072 - MSExchangeSubmissionMailboxEvent Viewer -> Application Log

Log Files to Check

What This Error Actually Means

The error code "5.7.133" is raised by Exchange Online when a sender attempts to send an email to a distribution group but lacks the necessary permissions or authentication required for such actions. Specifically, this error indicates that the sender's credentials are not recognized as approved within the context of the targeted distribution group settings. This error is often encountered in environments where strict security measures are enforced on mail flow and access control.

Affected Versions and Scope

This issue affects users running Windows 10 or Windows 11 operating systems when attempting to send emails through Exchange Online services. The problem arises due to the configuration of distribution groups within Exchange Online, where administrators have set up stringent requirements for sender authentication or restricted sending privileges to specific users only. This error does not occur in environments where such strict controls are not enforced on distribution group mail flow.

Where To Look First: Logs and Event IDs

To diagnose this issue effectively, start by examining the Application event log located at C:\Windows\System32\winevt\Logs\Application.evtx. You should look for entries with Event ID 1072 under MSExchangeSubmissionMailbox. Additionally, inspect the HealthService.log file found in C:\Program Files\Microsoft Monitoring Agent\Agent\HealthService.log for relevant error messages or warnings that correlate with the time of the incident. The exact log line to search for is: "5.7.133 - Sender not approved to send to distribution group." This message will be logged when an attempt to send a message fails due to sender authentication issues. The event ID 1072 in MSExchangeSubmissionMailbox provides critical details about the failed submission and can help pinpoint the exact cause of the problem.

Root Causes

Incorrect Sender Authentication Settings

This issue often stems from misconfigured distribution group settings where sender authentication is required but not properly set up. To identify this, check if the -RequireSenderAuthenticationEnabled parameter for the affected distribution group is set to true in Exchange Online.

Limited Allowed Senders List

Another common cause is a restrictive allowed senders list that excludes legitimate users from sending messages to specific groups. This can be verified by examining the -AcceptMessagesOnlyFrom setting on the problematic distribution group.

Inadequate Exchange Online Configuration

Sometimes, the issue lies within broader Exchange Online configurations rather than individual distribution group settings. Reviewing SMTP client authentication policies and transport rules may reveal misconfigurations that prevent certain senders from accessing distribution groups.

Fix Procedure

  1. First, ensure you have the necessary permissions to modify distribution group settings in Exchange Online.

  2. To adjust sender authentication requirements for a specific distribution group, use the following PowerShell cmdlet:

    Set-DistributionGroup -Identity "GroupName" -RequireSenderAuthenticationEnabled $false

    Note: Setting this to false might temporarily increase security risks. Ensure you understand the implications before proceeding.

    Disabling sender authentication can expose your organization to unauthorized access and spamming attempts. Always verify that such changes align with your security policies.
  3. If the issue is due to a restrictive allowed senders list, add permitted users or groups using:

    Set-DistributionGroup -Identity "GroupName" -AcceptMessagesOnlyFrom @{Add="[email protected]","[email protected]"}

    This cmdlet allows you to specify individual email addresses or entire Active Directory groups.

  4. To review and adjust broader Exchange Online configurations, navigate to the Exchange admin center > Mail flow > Rules. Here, inspect existing transport rules that might be interfering with mail flow to distribution groups.

Error Code Variants

CodeDescriptionDistinguishing Factors
5.7.134Sender not authenticated for distribution group.This error occurs when the sender's credentials are invalid or missing, indicating a problem with SMTP client authentication rather than permissions on the distribution group itself.
5.7.132Distribution group is full and cannot accept new messages.In contrast to 5.7.133, this error signals that the recipient's mailbox or distribution group has reached its storage capacity, preventing further message delivery regardless of sender authentication status.
5.7.0Generic mail flow failure.This broad category covers numerous issues not specific to sender authentication or distribution groups, making it distinct from 5.7.133 which is highly targeted towards these aspects of Exchange Online.

Verification

After implementing the necessary changes, verify that the issue has been resolved by attempting to send a test message to the affected distribution group. If successful, check the Application event log for Event ID 1072 and confirm there are no error messages related to sender authentication or restricted access. Additionally, navigate to Exchange admin center > Mail flow > Rules/Connectors/Accepted domains to ensure that your adjustments have been correctly applied at a broader organizational level. The absence of the original "5.7.133" error message in logs and successful delivery of test messages indicate a successful resolution.

Prevention

To prevent recurrence of this issue, establish clear guidelines for distribution group management within your organization. Regularly review and update sender authentication settings and allowed senders lists to ensure they remain aligned with current security policies and operational requirements. Implementing granular control over who can modify these settings through role-based access control (RBAC) in Exchange Online further mitigates risks associated with misconfigurations. Additionally, consider setting up monitoring alerts for changes made to distribution group properties that could affect mail flow or security compliance.
A quick diagnostic shortcut is using the Get-MessageTrace cmdlet with a recent time range to trace message delivery issues directly from Exchange Online.
By following these detailed steps and maintaining vigilant oversight over your distribution group configurations, you can effectively manage this error and ensure smooth communication within your organization.

Sources & References

Related Guides

Get new error code fixes by email

Product-specific solutions for Intune, Autopilot, SCCM and Entra ID — straight to your inbox. No spam.