Error Details
| Fact | Value | Source | Note |
|---|---|---|---|
| Exact error string | 550 5.7.350 Access denied, The IP address you are sending from is blocked | Exchange admin center (EAC) > Mail flow > Message trace | -> NDR |
| Affected build range | Exchange Online / Microsoft 365 | Microsoft documentation | |
| Registry key or OMA-URI involved | |||
| Relevant service/endpoint URL | sendersupport.olc.protection.outlook.com | Microsoft Sender Support portal | -> Delist request |
| Log line signature | Remote MTA: 'amtp102-nwrkr03.namprd02.prod.outlook.com' reports that the connection from '<sending IP>' has been blocked | Exchange admin center (EAC) > Mail flow > Message trace | -> Delivery event |
Log Files to Check
C:\Program Files\Microsoft\Exchange Server\V15\Logging\MessageTracking\<date>.log/var/log/exchange/message-tracking/<date>.log
What This Error Actually Means
The error code "550 5.7.350 Access denied, The IP address you are sending from is blocked" indicates that the sender's IP address has been identified as a potential source of spam or malicious activity and has been blocked by either Exchange Online Protection (EOP) or the recipient server’s connection filter policy. This error message is generated when an email sent from a specific IP address encounters a blocklist check during delivery, which results in the mail being rejected before it reaches its intended destination. The component raising this error is typically part of the Microsoft 365 security infrastructure designed to prevent spam and malicious content from entering or leaving tenant environments. This includes EOP's outbound filtering mechanisms as well as third-party services that maintain blocklists based on reputation scores for IP addresses.Affected Versions and Scope
This error is relevant across all versions of Exchange Online and Microsoft 365, including the latest builds as of this writing. It affects any tenant where email sending operations are conducted from an IP address that has been flagged by EOP or a third-party blocklist service due to suspicious activity. The affected build range includes: - Exchange Online - Microsoft 365 This error does not affect on-premises deployments of Exchange Server unless the server is relaying messages through Exchange Online and encounters this issue during relay. Additionally, it doesn't impact users who are sending emails from IP addresses that have a clean reputation or are exempted from blocklists due to specific tenant policies.Where To Look First: Logs and Event IDs
To diagnose the root cause of this error, start by examining logs in both Exchange Online and on-premises environments if applicable. The exact log paths for Exchange Online include: -C:\Program Files\Microsoft\Exchange Server\V15\Logging\MessageTracking\.log (Windows)
- /var/log/exchange/message-tracking/.log (Linux)
In these logs, look for the following literal log line signature to identify where and why the IP address was blocked:
Remote MTA: 'amtp102-nwrkr03.namprd02.prod.outlook.com' reports that the connection from '' has been blocked
Additionally, review Event IDs 5080 (MSExchange SMTP Send) in the on-premises Application log for entries indicating a refusal of connections due to blocklists. These logs will provide critical information about when and how often the sending IP was blocked.
Root Causes
Public Blocklist Inclusion
If your organization's IP address is listed in public blocklists such as Spamhaus SBL, SORBS, or Barracuda Reputation Block List, this can trigger the "550 5.7.350" error. To determine if this applies, check mxtoolbox.com/blacklists.aspx for a red status indicating inclusion.Outbound Spam Filter Policy
Exchange Online's outbound spam filter may block an IP address if it detects bulk or phishing email activity originating from that IP within your tenant environment. This is often due to compromised accounts sending malicious emails, which gets the entire IP flagged until resolved.Inbound Connector Configuration Mismatch
If you have on-premises servers relaying messages through Exchange Online and these servers use an IP address not listed in the inbound connector's IP allow list, this can result in the "550 5.7.350" error. This is especially common if there has been a recent change to your network infrastructure without updating the connector configuration.Fix Procedure
- Determine Sending IP Address: Identify the sending IP from the NDR header using the 'Received:' line at the top of the message.
- Check Public Blocklists: Visit mxtoolbox.com/blacklists.aspx and enter the sending IP to check for inclusion. Also, review specific DNSBLs mentioned in the NDR text (e.g., spamhaus.org/lookup).
- Submit Delist Request from Microsoft Sender Support Portal: Go to
sendersupport.olc.protection.outlook.com, enter the sending IP, and submit a delist request if blocked by EOP. - Review Restricted Users in Exchange Admin Center (EAC): Navigate to EAC > Mail flow > Restricted users. If compromised accounts are listed here, remove them after fixing account security issues such as resetting passwords and enabling MFA.
- Update Inbound Connector Configuration: Use PowerShell cmdlets like
Get-InboundConnectorandSet-InboundConnector -Identity <name> -SenderIPAddresses @{Add='<ip_address>'}to ensure the IP address of your on-premises relay server is correctly listed. - Review Event Logs for Connection Refusals: Check Event ID 5080 in the Application log for 'connection refused' entries with remote IPs. This helps identify specific instances where connections were blocked due to configuration mismatches or blocklist inclusion.
Error Code Variants
| Code | Description |
|---|---|
| 550 5.7.13 | The sender's domain is not allowed to send email through this server. |
| 421 4.3.0 | The mail system is temporarily unavailable due to a technical problem. |
| 550 5.7.69 | The recipient's domain does not accept email from this sender. |
Verification
To verify that the fix has been successful, send a test message from the delisted IP address and check EAC > Mail flow > Message trace for confirmation of delivery status. Additionally, review logs atC:\Program Files\Microsoft\Exchange Server\V15\Logging\MessageTracking\.log or /var/log/exchange/message-tracking/.log for any new entries indicating successful delivery without blocklist rejections.
Prevention
To prevent recurrence of this issue, implement the following measures: - Regularly monitor and maintain a clean reputation for your organization's IP addresses by ensuring no spam or malicious activity is originating from them. - Configure inbound connectors to accurately reflect all IP addresses used by on-premises relay servers to avoid mismatches that could lead to blocklist issues. - Implement robust security policies, including multi-factor authentication (MFA) and regular password resets for user accounts, especially those with elevated privileges or access to critical email functions.Be cautious when modifying IP allow lists in inbound connectors; incorrect changes can disrupt mail flow for enrolled devices.
Use the
Get-MessageTrace cmdlet to quickly identify recent instances of blocked emails and correlate them with blocklist entries or configuration issues.