Send & Receive Issues

Fix Mail-Enabled Security Group Not Receiving External Emails

Kushani NimanthikaKushani Nimanthika Oct 23, 2026 868 views

Question details

Newly created mail-enabled security groups managed via Active Directory fail to receive emails from external senders and return error 550 5.4.1, while older groups work correctly.

How to Fix a Mail-Enabled Security Group That Cannot Receive External Emails
Product
Microsoft 365 / Exchange Online
Device & OS
not provided
Scenario
External users (e.g., from Gmail or outside domains) attempt to send messages to a newly created mail-enabled security group.
Observed behavior
The external emails are not delivered to the new group, often triggering an NDR with Error 550 5.4.1, whereas older distribution lists receive them without issue.
Before you start

Ensure that enough time has passed for Active Directory synchronization (Azure AD Connect) to fully provision the newly created group in Microsoft 365 and Exchange Online.

Solution 1

Verify Delivery Management and Exchange Online Settings

Check if the newly created security group is restricted from receiving external emails by default.

By default, newly created mail-enabled security groups in Exchange Online may be configured to only accept messages from authenticated (internal) senders. You must manually allow external senders.

1
Access Exchange Admin Center

Log in to the Microsoft 365 admin center, expand the navigation menu, and click on 'Exchange' to open the Exchange Admin Center.

2
Locate the Security Group

Navigate to 'Recipients' > 'Groups', select the 'Mail-enabled security' tab, and click on the newly created group.

3
Modify Delivery Management

Go to the 'Settings' or 'Delivery management' tab, and change the setting from 'Only senders inside my organization' to 'Senders inside and outside of my organization', then save.

4
Test Delivery via OWA

Have an external sender test the email delivery. Additionally, test sending an internal email to the group using Outlook on the web (OWA) to ensure the address routes properly.

Free Microsoft Office alternative

Need a Reliable and Lightweight Office Suite? Try WPS Office

While resolving Exchange Online routing issues, you still need to get your daily work done. WPS Office offers a free, highly compatible alternative to Microsoft Office, ensuring you can manage Word, Excel, and PowerPoint documents without relying on cloud service stability.

  1. 1. Download the Installer: Visit the official WPS Office website and download the free installer for your operating system.
  2. 2. Install the Software: Run the installer and follow the simple on-screen instructions to set up WPS Office on your computer.
  3. 3. Open and Edit Your Files: Launch WPS Office to instantly open and edit your existing Microsoft Office documents with perfect formatting preservation.
Seamless compatibility with Microsoft Office formats (DOCX, XLSX, PPTX)Free and lightweight suite that uses minimal system resourcesFamiliar, tabbed user interface for an easy transitionBuilt-in robust PDF editing and conversion tools
microsoft office alternative - wps office

Frequently Asked Questions

Why do older mail-enabled security groups receive external emails fine, but new ones do not?

This is often due to directory synchronization delays between your on-premises Active Directory and Exchange Online. Older groups have fully propagated across Microsoft's backend servers, while newly created groups may be caught in a sync delay or require manual configuration to allow external senders.

What does Exchange Error 550 5.4.1 mean?

Error 550 5.4.1 is a routing error indicating that the recipient address was rejected by the destination domain. In Microsoft 365, it usually means there is a DNS configuration issue, a domain is incorrectly set as Authoritative, or there is an Active Directory synchronization failure preventing the server from recognizing the newly created group.

How do I check a group's safe-sender settings?

As an administrator, go to the Exchange Admin Center, locate the specific mail-enabled security group, and check its Delivery Management settings. Ensure that it is set to accept messages from senders both inside and outside the organization. Individual safe-sender settings can also be tested by having an internal user email the group using Outlook on the web.