Not able to send mail to Distributed List from databricks

Lepuru, Manish 0 Reputation points
2026-11-17T01:43:36.6633333+00:00

Hello Team,

We are sending email alerts from Databricks to distribution lists. Individual mailboxes receive the alerts, but no members of the distribution lists do. Details are below:

  • Organisation: [Moderator note: Personally Identifiable Information removed] 
  • Sender email: [Moderator note: Personally Identifiable Information removed] @chubb.com
  • Recipient distribution lists:
    • [Moderator note: Personally Identifiable Information removed] @esis.com
      • [Moderator note: Personally Identifiable Information removed] @chubb.com
      • Source application: Databricks

Please investigate why these messages aren't reaching the distribution list members. Also let us know if the sender needs to be allowed, or if the DLs need to accept mail from this sender or from external or application sources.

Thank you,

Manish.

Exchange | Exchange Server | Management
Exchange | Exchange Server | Management

The administration and maintenance of Microsoft Exchange Server to ensure secure, reliable, and efficient email and collaboration services across an organization.

0 comments No comments

2 answers

Sort by: Most helpful
  1. Dora-T 2,425 Reputation points Independent Advisor
    2026-11-17T02:38:21.8333333+00:00

    Hi @Lepuru, Manish

    Based on my research, I couldn't find an exact case matching your scenario, where emails sent from Databricks are successfully delivered to individual mailboxes but not to members of Exchange Server distribution groups. 

    However, you can try checking the following: 

    1.Review the distribution group's delivery restrictions:  

    Verify whether the group is configured to accept messages from all senders or only specific authenticated senders. 

    2.Review message tracking logs:  

    Check whether Exchange Server receives the messages and successfully expands the distribution groups into individual recipients. Pay particular attention to the EXPAND and FAIL events. 

    You can refer to the following Microsoft documentation for more information: 

    Message tracking | Microsoft Learn 

    Set-DistributionGroup (ExchangePowerShell) | Microsoft Learn 

    For reference, the following community discussion describes a similar scenario involving RequireSenderAuthenticationEnabled in Exchange Server 2016: RequireSenderAuthenticationEnabled - Distribution Groups - Exchange 2016 | Microsoft Community Hub 

    Please note that this is a user-to-user support forum, not an official Microsoft Support channel. Community members can share information and suggestions based on publicly available resources, documentation, and community discussions, but we cannot access Microsoft's internal systems, inspect your Exchange Server environment, or directly investigate your organization's mail flow configuration. 

    If the issue persists after trying the suggested checks, you may consider raising a Microsoft Premier/Unified Support ticket. This would allow Microsoft Support team to investigate the issue further and determine the appropriate next steps.

    Please note that this is a paid support option, which requires an active support plan or a one-time support purchase. However, one of the benefits of using this channel is that your inquiry will be handled by the appropriate Microsoft support team, which has access to additional technical expertise and resources. This team is better positioned to provide accurate and in-depth guidance, especially for complex or edge-case scenarios that go beyond publicly available documentation or community knowledge.

    You can refer to this guide Open a new Support request - Microsoft Engage Center | Microsoft Learn 

    Was this answer helpful?


  2. AI answer

    2026-11-17T01:44:55.7833333+00:00

    Identify which organization hosts each distribution list and have that organization’s Exchange administrator trace a Databricks message before changing the group’s sender restrictions.

    The chubb.com and esis.com addresses may be administered by different Exchange organizations. Configuration and tracing must be performed by the administrator or group owner responsible for each list; access to one tenant does not provide control over a list in another tenant.

    1. Establish the actual mail path

    For each distribution list, record:

    • Whether it is an Exchange Online distribution list, an on-premises Exchange group, or a third-party list.
    • Which organization administers it.
    • The exact send time, recipient list address, and visible From address.
    • The SMTP envelope sender or Return-Path, if available.
    • Any non-delivery report (NDR) and its complete status code.

    The visible From address alone does not establish that Exchange received an authenticated internal message. Databricks might submit through an SMTP relay, connector, or another service, so the trace/NDR must determine how Exchange classified the submission.

    2. Trace the message in the organization that owns the list

    For a list hosted in Exchange Online, an Exchange administrator should:

    1. Open Exchange admin center.
    2. Go to Mail flow > Message trace.
    3. Select a time range containing the test.
    4. Enter the actual sender and the distribution-list address.
    5. Run the search and open the message’s Details.

    Message trace shows how the message passed through Exchange Online and whether it was delivered, rejected, quarantined, or affected by another policy.^1^

    Interpret the result as follows:

    • No trace entry: Exchange Online did not receive the message under those sender/recipient details. Check the Databricks SMTP submission or relay logs and the actual envelope addresses.
    • Failed with 5.7.133: The group rejects unauthenticated/external senders.
    • Failed with 5.7.124: The sender is not in the group’s allowed-senders list.
    • Quarantined: Review the corresponding quarantine or filtering event.
    • Delivered to the group: Inspect expanded-recipient events and any moderation or downstream delivery status.

    Microsoft documents 5.7.133 as an external-sender authentication restriction and 5.7.124 as an allowed-senders restriction.^2^

    3. Apply the matching group configuration

    If the result is 5.7.133

    If the business policy permits any external/application sender:

    1. Go to Exchange admin center > Recipients > Groups.
    2. Select the distribution list.
    3. Open Settings > Delivery management > Edit delivery management.
    4. Select Allow messages from people inside and outside my organization.
    5. Save and send a new test message.

    Only the group owner or an email administrator in the recipient organization can make this change.^3^

    If the result is 5.7.124, or only Databricks should be allowed

    Use a restricted allow-list rather than opening the group to every external sender:

    1. In the recipient organization, create a mail contact or mail user representing the actual external sender identified by the trace/NDR.
    2. Go to Recipients > Groups > Distribution list.
    3. Select the list, then open Settings > Delivery management > Edit delivery management.
    4. Enable messages from inside and outside the organization.
    5. Under Specified senders, add the mail contact or mail user.
    6. Save and retest.

    An external sender must first be represented by a mail contact or mail user before it can be selected in the group’s allowed-senders list.^4^

    4. Optional PowerShell inspection

    For Exchange Online, after establishing an Exchange Online PowerShell session, inspect rather than change the group first:

    Connect-ExchangeOnline
    
    Get-DistributionGroup -Identity "[Email]" |
        Format-List PrimarySmtpAddress,
            RequireSenderAuthenticationEnabled,
            AcceptMessagesOnlyFrom,
            AcceptMessagesOnlyFromSendersOrMembers,
            ModerationEnabled
    

    Get-DistributionGroup is available in both Exchange Online and on-premises Exchange, subject to the administrator’s assigned permissions.^5^

    If either list is on-premises Exchange or managed by a third-party platform, the Exchange Online portal procedure does not apply; its owning administrator must inspect that system’s message-tracking data and sender restrictions. For the esis.com list, this may require a separate administrator from the one managing chubb.com.

    A successful retest should show the message accepted for the distribution-list address and delivery attempts to its expanded members.


    References

    1. Find and fix email delivery issues as a Microsoft 365 for business admin
    2. Email nondelivery reports and SMTP errors in Exchange Online
    3. Fix NDR error "550 5.7.133" in Exchange Online
    4. Fix NDR error "550 5.7.124" or "5.7.124" in Exchange Online
    5. Get-DistributionGroup-Syntax
    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.