How to Read Receipts in Outlook: What They Are and How They Actually Work

Read receipts in Microsoft Outlook seem simple on the surface — you send an email, and you want to know if the other person opened it. But the reality is more layered than most people expect. Whether they work, what they tell you, and how to interpret them depends on a surprising number of factors.

What Is a Read Receipt in Outlook?

A read receipt is an automated notification that gets sent back to you when a recipient opens your email. When you request one, Outlook adds a hidden header to your message. When the recipient opens it, their email client is prompted to send a confirmation message back to your inbox.

That confirmation typically appears as a standard email with a subject line like "Read: [Your original subject]" along with a timestamp.

A delivery receipt is different — it confirms the message reached the recipient's mail server, not that anyone actually opened it. Outlook supports both, and it's worth knowing which one you're actually using.

How to Request a Read Receipt When Sending an Email

In the Outlook desktop app (Windows or Mac):

1. Open a new email compose window
2. Click the Options tab in the ribbon
3. Check Request a Read Receipt and/or Request a Delivery Receipt
4. Send your email as normal

In Outlook on the web (Outlook.com or Microsoft 365 webmail):

1. Compose a new email
2. Click the three-dot menu (More options) in the toolbar
3. Select Show message options
4. Toggle on Request a read receipt

To set read receipts for all outgoing messages by default:

• Go to File → Options → Mail
• Scroll to the Tracking section
• Check the boxes for delivery and/or read receipts under "For all messages sent, request:"

Why Read Receipts Don't Always Work 📬

This is where many users get confused. A read receipt is a request, not a guarantee. Several variables determine whether you'll ever receive one.

Recipient's email client settings: The recipient's mail client must support read receipts and be configured to send them. Many clients — including Gmail, Apple Mail, and older versions of Outlook — either ignore the request entirely or prompt the user to choose whether to send a receipt.

Recipient choice: When prompted, many users click "No" or dismiss the dialog. You have no control over this, and there's no way to force a receipt to be sent.

Corporate IT policies: In business environments, IT administrators can configure Exchange or Microsoft 365 servers to block or suppress read receipt responses — either outgoing (preventing users from sending receipts) or incoming (stripping read receipt requests from messages before they're delivered).

Email preview and reading panes: Some email clients only trigger a read receipt when a message is fully opened, not when it appears in a preview pane. Others trigger it the moment the message is displayed. This inconsistency can make timestamp data misleading.

HTML vs plain text: Read receipt functionality typically relies on HTML-formatted email. Plain text emails may not trigger the prompt in the recipient's client at all.

How Read Receipts Work at the Server Level

When you request a read receipt, Outlook inserts a Disposition-Notification-To header (or the proprietary Microsoft X-Confirm-Reading-To header in some environments) into the message. This is part of the Message Disposition Notification (MDN) standard defined in RFC 8098.

When a compliant email client opens the message and the user (or their client's auto-response setting) agrees to send a receipt, it generates a formatted reply pointing to your address.

The important takeaway: this entire system is cooperative, not coercive. It works when both ends support and allow it.

Comparing Read Receipt Behavior Across Common Setups

Managing Incoming Read Receipt Requests

If you're on the receiving end, Outlook gives you control over how to handle these requests. Under File → Options → Mail → Tracking, you can set Outlook to:

• Always send a read receipt automatically
• Never send one
• Ask each time before sending

This setting applies to all incoming receipt requests, which is useful if you prefer not to notify senders every time you open an email.

What Read Receipt Timestamps Actually Tell You ✉️

When you do receive a read receipt, the timestamp reflects when the recipient's mail client processed the open event — not necessarily when they read or understood the message. An email could be opened by accident, briefly glanced at, or opened by an automated system.

In high-volume business environments, assistants, shared mailboxes, and email management tools can trigger receipts without the intended recipient ever seeing the message personally.

The Variables That Shape Your Experience

Whether read receipts are a reliable tool for you depends on:

• Your organization's mail server configuration — Exchange and Microsoft 365 admins have significant control here
• Who you're emailing — internal recipients in the same org behave differently than external contacts using non-Outlook clients
• The recipient's own Outlook or client settings — which you can't see or change
• Whether you're on desktop, web, or mobile — Outlook mobile has limited read receipt support compared to the desktop app

For some users in tightly controlled corporate environments, read receipts work predictably. For others emailing a mixed audience across different platforms, receipts arrive inconsistently or not at all. The gap between what you requested and what you actually receive is almost always determined by factors outside your inbox.