Read Receipts Explained: How They Work (and Why They're Not Always Reliable)
People often assume read receipts work like the blue checkmarks on a messaging app — an automatic, unavoidable confirmation. Email doesn't work that way, and understanding why explains most of the confusion around them.
How they actually work
When you request a read receipt, your mail app adds a small technical request to the message asking the recipient's mail app to send back a notification once the message is opened. That's the entire mechanism — it depends entirely on cooperation from the receiving side. There's no way to force this, and no way to see whether a message was read if the recipient's system doesn't send that confirmation back.
Why it so often doesn't work
- Most mail apps let the recipient choose whether to send a receipt at all — many are configured to ask every time, and a lot of people simply decline or ignore the prompt.
- Some providers disable the feature by default or don't support the specific read-receipt standard your app is using — Gmail, Outlook, and Apple Mail don't all implement this identically.
- Opening an email in a preview pane (a common pattern in many apps) sometimes doesn't trigger a "read" event the same way actually opening the full message does.
- Corporate and business accounts frequently have this disabled entirely by IT policy, for privacy reasons.
What "delivered" isn't the same as "read"
Worth separating two different things people sometimes conflate: confirmation that a message was successfully delivered to the recipient's server (this part is generally reliable, and a failure here produces an actual bounce message) versus confirmation that a human actually opened and read it (this is the unreliable part, entirely dependent on recipient cooperation).
If you genuinely need confirmation someone saw something
For anything where it actually matters — a time-sensitive request, something you need acknowledged — a read receipt isn't a reliable mechanism to depend on. A direct follow-up message, or simply asking for a quick reply confirming receipt, works far more consistently than any built-in read-receipt feature.