Read receipts in Outlook tell you when your email has been opened by the recipient. Classic Outlook users who switch to the new Outlook for Windows find that read receipt behavior changes significantly. The new Outlook uses a different email sync engine that does not support the traditional read receipt tracking system found in Classic Outlook. This article explains how read receipts work in the new Outlook, what Classic Outlook users lose, and how to manage requests and responses in each version.
Key Takeaways: Read Receipts in New vs Classic Outlook
- New Outlook cannot send read receipts: It ignores receipt requests from senders and does not generate receipt responses when you open an email.
- Classic Outlook processes receipts normally: It prompts you to send a receipt when you open a message with a read receipt request.
- New Outlook can request a receipt on send: You can still ask for a read receipt when composing an email, but the recipient must use a mail client that honors the request.
How Read Receipts Work in Outlook: The Technical Difference
A read receipt is a Message Disposition Notification (MDN) request embedded in the email headers. When the recipient opens the email, their mail client sends a small response message back to the sender. This confirms the message was opened.
Classic Outlook uses the MAPI (Messaging API) protocol to send and receive these MDN notifications. The new Outlook for Windows uses the same sync engine as Outlook on the web (Exchange ActiveSync or REST API). This engine does not process incoming MDN requests. When a message with a read receipt request arrives in the new Outlook, the request is silently ignored. No prompt appears, and no receipt is sent.
This difference is by design. Microsoft built the new Outlook on a web-based infrastructure that prioritizes simplicity and cross-platform consistency. The trade-off is the loss of several MAPI-based features, including read receipt handling, voting buttons, and some forms of message recall.
How to Request a Read Receipt in the New Outlook
You can still ask for a read receipt when you send an email from the new Outlook. The setting is in the same location as Classic Outlook, but the behavior on the receiving end depends on the recipient’s mail client.
- Open a new message
Click New Mail in the ribbon or press Ctrl+N. - Enable the read receipt option
Go to the Options tab in the message window. Check the box labeled Request a Read Receipt. - Send the email
Complete the To, Subject, and body fields, then click Send.
After sending, you will receive a read receipt only if the recipient uses a mail client that supports MDN and the recipient approves the receipt prompt. If the recipient uses the new Outlook, Gmail, or Apple Mail with default settings, you will not get a receipt.
How to Respond to a Read Receipt Request in the New Outlook
The new Outlook does not prompt you to send a read receipt when you open an email that contains a receipt request. The request is ignored with no notification to you. There is no setting to enable or disable this behavior because the feature does not exist in the new Outlook.
If you need to send a read receipt for a specific message, you must use Classic Outlook or Outlook on the web. In Outlook on the web, read receipt requests are handled automatically based on your settings under Settings > Mail > Read receipts.
How to Manage Read Receipts in Classic Outlook
Requesting a Read Receipt
- Open a new message
Click New Email or press Ctrl+N. - Select the Options tab
In the message window, click the Options tab on the ribbon. - Check Request a Read Receipt
In the Tracking group, check the box Request a Read Receipt. You can also check Request a Delivery Receipt for confirmation that the message reached the recipient’s server. - Send the message
Click Send.
Responding to a Read Receipt Request
When you open a message with a read receipt request in Classic Outlook, a dialog box appears with three choices:
- Yes: Send a read receipt now.
- No: Do not send a receipt. The request is discarded for this message.
- Always ask before sending: Outlook will prompt you each time. This is the default setting.
You can change the default behavior in File > Options > Mail > Tracking. Under For all messages sent, receive read receipts, choose Always send a read receipt or Never send a read receipt.
If Read Receipts Are Missing or Not Working
You sent a receipt request but never received a response
The recipient may use the new Outlook, a mobile email app, or a webmail service that does not support MDN. There is no workaround to force a receipt from these clients. Consider using a third-party email tracking service if you need confirmation from all recipients.
You receive read receipt requests in the new Outlook but see no prompt
This is expected behavior. The new Outlook does not process incoming MDN requests. Switch to Classic Outlook or Outlook on the web if you need to respond to receipt requests.
You want to disable read receipt requests in the new Outlook
There is no setting to block incoming receipt requests because the new Outlook ignores them by default. No action is needed.
New Outlook vs Classic Outlook: Read Receipt Comparison
| Feature | New Outlook | Classic Outlook |
|---|---|---|
| Request receipt on send | Supported | Supported |
| Prompt on incoming request | Not supported | Supported |
| Send receipt automatically | Not supported | Supported via File > Options > Mail > Tracking |
| Block all receipt requests | Not needed (ignored by default) | Supported via registry or Group Policy |
| Receipt tracking in Sent Items | Not supported | Supported via Tracking folder |
The new Outlook for Windows handles read receipts differently from Classic Outlook. You can request a receipt when sending, but you cannot send receipts when receiving. To manage incoming receipt requests fully, use Classic Outlook or Outlook on the web. If you rely on read receipts for business workflows, test which client your recipients use before switching to the new Outlook permanently. For advanced tracking needs, consider a third-party email tracking add-in that works with both versions.