Send & Receive Issues

Stop Microsoft 365 NDRs for Nonexistent Recipients

Emma BrownEmma Brown Nov 20, 2026 868 views

Question details

The user wants to prevent unwanted non-delivery reports for messages sent to deleted or nonexistent recipients from reaching a mailbox.

Stop Microsoft 365 NDRs for Nonexistent Recipients
Product
Microsoft 365 Exchange Online Protection
Device & OS
not provided
Scenario
Spam sent to invalid recipients triggers non-delivery reports that appear in a postmaster mailbox or Junk folder.
Observed behavior
Microsoft-generated NDRs reach the mailbox even though the original spam does not reach the user.
Before you start

Keep a representative NDR and its message headers so an Exchange administrator can identify its sender, recipient, and original delivery failure. Sign in with an account that can access the Exchange admin center and, if submitting messages, the Microsoft Defender portal.

Solution 1Recommended

Trace the NDR and verify Exchange recipient settings

Use this approach to identify why the report reaches the mailbox and check whether the domain and recipient configuration is correct.

1
Inspect a report

Open an NDR in Outlook and review the report recipient, failed recipient, diagnostic details, and message headers. Check whether the report is addressed to an existing mailbox or a spoofed address.

2
Run a message trace

In the Exchange admin center, open Mail flow > Message trace. Search for the NDR using its recipient and approximate delivery time, then review its delivery details.

3
Check domain and recipient settings

In the Exchange admin center, open Mail flow > Accepted domains and verify whether the affected domain is configured as authoritative or internal relay as intended. Under Recipients, check for relevant mailboxes, aliases, and forwarding settings.

4
Submit representative messages

In the Microsoft Defender portal, open Email & collaboration > Review > Submissions and submit representative messages for analysis. Include the original spam when available, rather than assuming the NDR itself is the original message.

Trace the NDR and verify Exchange recipient settings
Avoid blocking random senders: Spoofed sender addresses often change, so blocking individual addresses may not stop the reports. Do not change an accepted domain from internal relay to authoritative without confirming that all valid recipients are hosted in Microsoft 365.
Free Microsoft Office alternative

Work with Office documents in WPS Office

WPS Office is a free, lightweight alternative for working with Office documents through a familiar interface. Its format compatibility makes it easy to move existing files into your workflow, although it does not change Microsoft 365 mail-flow settings or stop Exchange NDRs.

Work with documents while investigating email delivery issuesOpen and edit common Microsoft Office formats, including DOCX, XLSX, and PPTXUse a familiar interface for a smoother transition from Microsoft OfficeAccess a free, lightweight office suite
microsoft office alternative - wps office

Frequently Asked Questions

Why am I receiving NDRs for messages I did not send?

A spammer may have spoofed your address as the sender, causing a delivery failure report to be sent to it. Inspect the NDR headers and use Exchange admin center > Mail flow > Message trace to investigate.

Will blocking the original sender stop these reports?

Usually not if the original sender addresses are random or forged. Review the NDR and trace details first, and submit representative messages through the Microsoft Defender portal for analysis.

Should I change my accepted domain to authoritative?

Only if that matches your mail environment. Check Exchange admin center > Mail flow > Accepted domains and confirm that all valid recipients are hosted in Microsoft 365 before changing an internal relay domain.

Can a mail-flow rule stop Exchange from generating every NDR?

Not necessarily. A rule may filter certain reports after they are generated, and system-generated NDRs may not behave like ordinary messages. Test a narrowly scoped rule and verify the results in Message trace.