Fix Distribution List Email Fails for External Contacts (Error 550 5.7.520)
Question details
Messages sent to certain external contacts through a synchronized distribution list fail, triggering an external-forwarding restriction, while direct emails to the same contacts work normally.

- Product
- Microsoft Exchange
- Device & OS
- not provided
- Scenario
- Sending emails to external contacts via a synchronized distribution list in a hybrid Exchange environment.
- Observed behavior
- Emails fail to deliver with error code 550 5.7.520, citing an external-forwarding restriction, despite direct emails to the same contacts delivering successfully.
Ensure you have administrative access to your on-premises Active Directory Users and Computers (ADUC) and the Exchange Online admin center.
Correct the Mail and Proxy Addresses in Active Directory
Align the on-premises proxy and target addresses with the contact's actual external SMTP address to prevent routing errors in Exchange Online.
In a hybrid Exchange setup, synchronized mail contacts must have primary SMTP and proxy addresses that accurately reflect their external domain. If unique internal addresses (like noreply.domain.com) are used, Exchange Online may block distribution list deliveries as unauthorized external forwarding.
Launch Active Directory Users and Computers (ADUC) on your local server. Locate the failing external contact, right-click it, and select Properties.
Navigate to the Attribute Editor or the Email Addresses tab. Check the primary SMTP address and any associated proxy addresses.
Temporarily clear the 'targetAddress' attribute. Ensure that the 'mail' and proxy addresses are set identically to the contact's actual external email address, removing any generic noreply domains.
Open PowerShell on your Azure AD Connect server and execute 'Start-ADSyncSyncCycle -PolicyType Delta' to push the updated contact attributes to Exchange Online.
Send a test email to the distribution list to verify that the 550 5.7.520 error is resolved and the message is delivered to the external contact.

Resolve Guest Account Conflicts in Exchange Online
Check for and remove duplicate guest accounts in Microsoft 365 that share the same external email address as your on-premises contacts.
Enhance Your Productivity with WPS Office
While you are managing Exchange server configurations and Active Directory issues, you can rely on WPS Office for all your daily documentation, spreadsheets, and presentation needs. WPS Office is a lightweight, free alternative to Microsoft Office that offers seamless compatibility.

Frequently Asked Questions
What does error 550 5.7.520 mean in Exchange Online?
This error typically indicates that messages are being blocked by an external-forwarding restriction. It often occurs when the outbound spam filter policy restricts automatic forwarding, or when routing configurations for synchronized contacts are improperly formatted.
Why do direct emails work but distribution list emails fail for the same contact?
Exchange Online evaluates forwarding and routing rules differently for distribution lists. If an email is routed through a distribution list to a synchronized contact with mismatched target and proxy addresses, Exchange may treat it as unauthorized automatic external forwarding and block it.
How do I force directory synchronization after changing an AD contact?
To force a sync immediately, open an elevated PowerShell prompt on your Azure AD Connect server and run the command: Start-ADSyncSyncCycle -PolicyType Delta. This will push the recent changes to Exchange Online.




