Read Receipts vs Certified Email: Which One Actually Proves Delivery?
You send a termination notice, a rent increase or a signed contract. A few weeks later the other party says they never received it. You check your sent folder, and perhaps you ticked "request read receipt". Is that enough to settle it?
Often it isn't. This article explains how read receipts, tracking pixels and certified email each work, what they can and can't prove, and how to choose the right one for messages that matter.
What your sent folder actually proves
Your sent folder shows that your email client created and sent a message. It doesn't show that the message reached the recipient's mail server. Emails can bounce, be delayed or get stuck in a queue without anything changing in your sent items.
A sent folder is also easy to edit or recreate, which means the other side can reasonably question it. It's your own record, not independent evidence.
How read receipts work (and why they're unreliable)
A standard read receipt is a request added to your email asking the recipient's mail program to send back a notification when the message is opened. The key word is request.
- The recipient can decline. Most email clients ask the reader whether they want to send a receipt. Clicking "no" is easy.
- Many clients ignore them. Plenty of webmail services and mobile apps simply don't support read receipt requests.
- Silence proves nothing. If no receipt arrives, you can't tell whether the email wasn't delivered, wasn't opened, or the reader just chose not to respond.
So a read receipt is useful when it arrives, but you can't rely on getting one, and its absence leaves you exactly where you started.
What about tracking pixels?
Many marketing and sales tools track opens using a tiny invisible image. When the recipient's email client loads the image, the tool logs an "open".
This is better than nothing, but it has well-known weaknesses. Some people block remote images by default, some corporate mail systems strip them, and some privacy features load images automatically whether or not anyone reads the email. That means you can get both false negatives and false positives. Open tracking is a useful signal, but it isn't firm proof on its own.
Delivery proof: the evidence that sits underneath
When an email is delivered, your sending server talks to the recipient's mail server using a protocol called SMTP. During this exchange, often called the SMTP handshake, the receiving server either accepts the message or rejects it. If it accepts, it responds with a confirmation, and that moment can be timestamped.
This is a much stronger form of evidence than a read receipt, because:
- It doesn't depend on the recipient's choices or the settings in their email app.
- It shows the message was handed to, and accepted by, the server responsible for the recipient's mailbox.
- It can be recorded by an independent party rather than by you.
For a lot of everyday disputes, the real question is "did this arrive before the deadline?" rather than "did they read it?". If you're relying on a notice clause or a specific requirement, check the wording of your agreement or take advice on what counts as delivery in your situation.
Side-by-side comparison
| Method | What it shows | Main weakness |
|---|---|---|
| Sent folder | You sent a message from your client | Doesn't show delivery; it's your own record |
| Read receipt | The reader agreed to confirm opening | Optional, often unsupported, easy to decline |
| Tracking pixel | An image in the email was loaded | Blocked or auto-loaded images skew results |
| Certified email | The recipient's mail server accepted the message, with timestamps, recorded by an independent relay | Proves delivery to the mail server rather than that a person read it |
How MailProof certified email works
MailProof, a certified email service from Transcom, is built around that server-level evidence. Your email is routed through MailProof's certified relay, which records the full SMTP handshake with the recipient's mail server, including their acceptance and exact timestamps.
That record becomes a formal PDF certificate containing:
- A unique certificate ID and tracking code
- Sender and recipient details
- The subject line
- The names of any attachments
- The complete timestamped delivery timeline
You also get real-time tracking through each stage, submitted, dispatched, delivered, confirmed and opened, so you can see read confirmation where it's available on top of the delivery proof. A confirmation email with the PDF certificate attached is sent to you as well.
Crucially, the evidence doesn't depend on your word alone. Anyone can check a delivery on the public verification page by entering the certificate ID or tracking code, with no account needed. MailProof describes this as strong evidence of delivery that can be used in disputes, legal proceedings and regulatory matters.
A few practical details
- Your own address: emails go out from your business email address, so recipients see you rather than a generic sender.
- Attachments: you can attach files up to 10MB, and the file names are recorded on the certificate as evidence of what was sent.
- Security: messages are protected by TLS 1.3 in transit and AES-256-GCM encryption at rest, and message content is only accessible to the account holder.
- No software: there's nothing to install; you compose and send from your MailProof account.
Tips for sending messages you may need to prove
- Double-check the address. Delivery proof only helps if it went to the right mailbox. Use the address given in the contract or the one the recipient normally uses.
- Name attachments clearly. Since file names appear on the certificate, something like "Notice-of-termination-March.pdf" is far more useful than "scan001.pdf".
- Use a clear subject line. It's recorded on the certificate, so make it describe the content.
- Send early. If there's a deadline, don't leave it to the last hour. A timestamp proves when it landed, but it can't move a deadline.
- Keep the certificate safe. Store the PDF with your other records for that contract, tenancy or case.
When is certified email worth it?
For everyday messages, a normal email is fine. Certified email earns its place when a dispute, deadline or regulator might later ask you to show what you sent and when. Typical examples include:
- Contracts and agreements
- Termination notices and cancellations
- GDPR notifications, financial disclosures and other documented communications
- Landlord and tenant notices, such as rent increases or maintenance warnings
Get started with MailProof
The Free plan includes 10 certified emails every calendar month with the full feature set, including PDF certificates, tracking, read confirmation and public verification. A valid business or organisation email address is needed to sign up. If you need more, pay as you go at £0.50 per certified email plus VAT, or buy a 100-email bundle for £45 plus VAT.
To send your first certified email, create your free MailProof account.