What is a Return/Read Receipt (RR) in Email?

I’ve been asked about return receipts regularly, so I thought I would offer an overview of RRs and how and when they should be engaged.

Return or Read Receipts (RRs) are a way of determining if an email has been received on the recipient’s computer. It does not, however, mean they have actually read it.

There are those who, because they want to know when you receive their email, even if the content is not critical, will engage the RR feature. In some cases, I think it is a control thing.

Or, it could be your friend does not even know they have this option selected. Maybe nicely emailing them with a “Did you know…..” can let them know this is not a feature to be used for every single casual email.

RRs Are to be Used Sparingly

There is no point in engaging a Return or Read Receipt (RR) request for the personal emails. Don’t be that person who has to know when someone opens the email you sent to them.

You force the recipient to react just to see your email. They have to take the step to accept or decline. That is why this feature can be viewed as intrusive.

I’ve had folks email me, noting they understand that RRs may be perceived as annoying, but they will continue to use RRs anyway. They want to know when their emails are received.

I’m not sure what that point of view accomplishes, especially considering you can decline RR requests — which is what most folks do. Or have them set to be automatically rejected like I do.

Managing Return Receipts

For me, it is none of anyone’s bee’s wax when I open any particular email. Don’t get me wrong, on those infrequent occasions when it is an important matter and I can understand why there is an RR is requested, I go ahead and give my approval.

These situations would include receiving a legal document or an important update. The sender wants a simple confirmation that I received their information. I understand why, so there is no problem there. But RRs for benign or non-critical emails?

What about “Blind” RRs?

Some services and plugins offer “Blind” RRs. These products imply that the recipient will not be aware of the RR request. These services can report back if an email is opened. But it is sort of smoke and mirrors with no guarantees.

Opened does not mean read.

What these services and plugins do is include a little one-pixel graphic with each email. When the email is opened, the graphic is called from the sender’s server. Stats will then reflect that the email to your address was opened for the graphic to be called.

While you can assume the email was opened, that doesn’t mean read. There is no way to prove that your message was read.

I have my email program set not to download graphics automatically. This is a security feature in my email software and includes that little pixel graphic.

This means there is no way to know I opened the mail, let alone to make the gigantic leap that I read it. (If you don’t want to be tracked, engage this feature in your email software too.)

So why continue using RRs? Especially considering you have no confirmation that a) the intended recipient is the opener and b) they read your email. Of course, except for those rare circumstances I previously noted. Unless both sides understand why the request is being made, RRs are not recommended.

RRs Should be a Rarity

So don’t be an email stalker. I’ve never found a reason to use RRs with everyday personal emails to friends or family. Now that I think about it — I don’t even remember the last time I initiated an RR request.

(If you know a return receipt abuser, you can use my example email to send them here.)