logo
search
Send & Receive Issues

How to Troubleshoot Incoming Emails Being Deleted in Exchange 2016

Huda QurayshiHuda Qurayshi Sep 29, 2026 868 views

Question details

Incoming messages are being permanently deleted upon arrival in Exchange Server 2016 without reaching the intended recipient.

Troubleshoot Incoming Emails Being Deleted in Exchange 2016
Product
Exchange Server 2016
Device & OS
not provided
Scenario
Administrators or users notice that expected incoming emails never arrive in the inbox and appear to be permanently dropped or deleted by the server.
Observed behavior
Incoming emails are permanently deleted without user intervention due to automated server processes such as mail flow rules, transport agents, or mailbox processing.
Before you start

Ensure you have Exchange administrative privileges to access the Exchange admin center (EAC) and the Exchange Management Shell. Gathering the exact sender address, recipient address, and time of the missing email will make searching the logs significantly faster.

Solution 1Recommended

Analyze Message Tracking Logs in Exchange Management Shell

Use message tracking logs to pinpoint exactly where and why the incoming email was dropped or deleted during the transport process.

Message tracking logs record all message activity as mail flows through the transport pipeline on Mailbox servers and Edge Transport servers. They are the most reliable tool for discovering which automated process terminated a message.

1
Launch Exchange Management Shell

Open the Exchange Management Shell (EMS) on your Exchange 2016 server using an administrator account.

2
Run the Get-MessageTrackingLog Cmdlet

Execute the command: `Get-MessageTrackingLog -Sender "sender@domain.com" -Recipients "user@yourdomain.com" -Start "MM/DD/YYYY HH:MM:SS" -End "MM/DD/YYYY HH:MM:SS"` to filter logs for the specific missing message.

3
Identify FAIL or DROP Events

Review the output, paying close attention to the 'EventId' column. Look for events labeled 'FAIL' or 'DROP'. The 'SourceContext' and 'RecipientStatus' fields will often detail which transport rule or agent executed the deletion.

Analyze Message Tracking Logs in Exchange Management Shell
Log Retention Limits: By default, message tracking logs are kept for 30 days. If the incident occurred before this window, the logs may have already been purged by the system.
Free Microsoft Office alternative

Streamline Your Daily Work with WPS Office

While Microsoft Exchange handles complex backend email routing, managing your daily documents shouldn't require complex configurations. WPS Office provides a lightweight, highly compatible alternative to Microsoft Office, bringing Word, Excel, and PowerPoint functionalities into one seamless interface.

Fully compatible with Microsoft Word, Excel, and PowerPoint formats (.docx, .xlsx, .pptx).Lightweight application that uses minimal system resources while delivering robust performance.Familiar user interface requires no learning curve, making migration effortless for your team.Built-in PDF editing tools for comprehensive document management.
microsoft office alternative - wps office

Frequently Asked Questions

What are transport agents in Exchange 2016?

Transport agents are software components installed on the Exchange server that process messages as they flow through the transport pipeline. Examples include third-party anti-spam, anti-malware filters, or archiving tools, which might delete emails they flag as policy violations.

Why does Exchange Server delete emails without sending a bounce-back message?

If a mail flow rule is configured with the specific action 'Delete the message without notifying anyone' (a silent drop), the server will permanently delete the incoming email without generating a non-delivery report (NDR) for the original sender.

Can I recover emails that were permanently deleted by an Exchange transport rule?

Generally, no. Emails dropped or deleted at the transport level (before they reach the mailbox database) bypass the user's dumpster and cannot be recovered using standard deleted item recovery. The original sender will need to resend the message after the routing issue is fixed.

Is Exchange Server 2016 still fully supported by Microsoft?

Exchange Server 2016 has reached the end of its mainstream support and extended support. Organizations are strongly encouraged to plan an upgrade to a newer, supported version like Exchange Server 2019 or migrate to Microsoft 365 (Exchange Online) to receive continued security updates.