The administration and maintenance of Microsoft Exchange Server to ensure secure, reliable, and efficient email and collaboration services across an organization.
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
Fromaddress. - 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:
- Open Exchange admin center.
- Go to Mail flow > Message trace.
- Select a time range containing the test.
- Enter the actual sender and the distribution-list address.
- 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:
- Go to Exchange admin center > Recipients > Groups.
- Select the distribution list.
- Open Settings > Delivery management > Edit delivery management.
- Select Allow messages from people inside and outside my organization.
- 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:
- In the recipient organization, create a mail contact or mail user representing the actual external sender identified by the trace/NDR.
- Go to Recipients > Groups > Distribution list.
- Select the list, then open Settings > Delivery management > Edit delivery management.
- Enable messages from inside and outside the organization.
- Under Specified senders, add the mail contact or mail user.
- 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