Send & Receive Issues

Fix Exchange Online User Can Receive Email but Cannot Send

Anum MushtaqAnum Mushtaq Nov 2, 2026 869 views

Question details

An Exchange Online user is unable to send outbound emails and receives a valid-sender error, despite successfully receiving incoming messages and not appearing on the Restricted users page.

How to Fix Exchange Online User Can Receive Email but Cannot Send
Product
Exchange Online
Device & OS
not provided
Scenario
A user attempts to send an outbound email but it fails to deliver, triggering a non-delivery report (NDR).
Observed behavior
The outgoing message bounces back with an NDR, typically error 550 5.1.8, indicating the sender is suspected of sending spam. The admin cannot unblock them because the user is missing from the Microsoft 365 Restricted users list.
Before you start

Before reaching out to support, verify that the affected account has not been compromised. It is highly recommended to reset the user's password and ensure Multi-Factor Authentication (MFA) is actively enforced.

Solution 1Recommended

Open a Service Request to Remove Backend Restriction

Since the user does not appear on the standard Restricted users page, Microsoft support must manually investigate and remove the hidden backend block tied to NDR 550 5.1.8.

Non-delivery report (NDR) 550 5.1.8 occurs when an account is flagged by Exchange Online Protection for exceeding outbound spam limits. Typically, admins can unblock these users from the Microsoft 365 Defender portal.

However, if the user does not show up on the Restricted users list but still suffers from this valid-sender error, the restriction is applied at the backend level. You will need to contact Microsoft Support to have the block manually lifted.

1
Log in to the Admin Center

Navigate to the Microsoft 365 admin center and sign in using your global administrator or Exchange administrator credentials.

2
Navigate to Help & Support

Click on the 'Support' or 'Help & support' icon located at the bottom right corner of the admin dashboard.

3
Create a New Service Request

Type a brief description of the issue (e.g., 'User cannot send email NDR 550 5.1.8') in the search bar. If the automated troubleshooting steps do not resolve the issue, select the option to contact support and open a new service request.

4
Provide User Details

In the ticket, explicitly state the affected user's email address, attach a copy of the non-delivery report containing the 550 5.1.8 error code, and specify that the user is absent from the Restricted users page.

Open a Service Request to Remove Backend Restriction
Propagation Time: Once Microsoft Support removes the backend restriction, it may take between 1 to 24 hours for the changes to fully propagate through the Exchange servers.
Free Microsoft Office alternative

Enhance Your Workflow with a Free Office Alternative

While resolving Exchange and email server issues requires Microsoft admin tools, everyday document drafting shouldn't be complicated. WPS Office is a free, lightweight, and user-friendly alternative to Microsoft Office that makes writing emails, tracking data, and designing presentations effortless.

  1. 1. Download the Installer: Visit the official WPS Office website and download the free installation package tailored for your operating system.
  2. 2. Install the Software: Run the downloaded executable file and follow the straightforward on-screen instructions to complete the setup.
  3. 3. Start Creating: Launch WPS Office to instantly access Writer, Spreadsheet, Presentation, and PDF tools without any subscription barriers.
Seamlessly draft professional email contents and reports using the WPS Writer tool.Fully compatible with Microsoft Word, Excel, and PowerPoint formats (.docx, .xlsx, .pptx).Lightweight application that uses minimal system resources and runs flawlessly across Windows, Mac, and mobile.Familiar user interface ensuring zero learning curve for seamless document migration.
QA img-9

Frequently Asked Questions

What triggers the 550 5.1.8 error in Exchange Online?

This error is triggered when Exchange Online Protection detects anomalous outbound mail flow, such as sending bulk emails or suspected spam, automatically blocking the account to protect the tenant's reputation.

Why is the blocked user not showing up on the Restricted users page?

This usually happens due to a backend sync delay, or because Microsoft has applied a deeper, tenant-level or backend restriction that bypasses the standard Microsoft 365 Defender portal UI.

How can I prevent Exchange Online users from getting blocked?

Enforce Multi-Factor Authentication (MFA), educate users on phishing scams, use strong passwords, and ensure your organization stays within Microsoft's outbound message limits.