You've likely received a "Message Recall" e-mail at some point. They have a Subject line that looks like this: Reid Trautz would like to recall the message "You won't believe what Dan Pinnington said." The text within the quote marks is the Subject line of the original message – the one the sender wants recalled.
Many e-mail systems, including the widely used Microsoft/Outlook Exchange Server and IBM Lotus Notes/Domino Server, offer a Message Recall feature. This feature is supposed to delete unread copies of the recalled message from the recipients’ inboxes so they never see it.
When does one make use of Message Recall?
Usually when you are in a minor to major panic in one of these scenarios:
- You send a message without the attachment that you wanted to include.
- You send a message when you are mad or upset and 20 minutes later you realize your words were nasty or inappropriate and you want those words back.
- You realize after you’ve sent something that it was addressed to the wrong person. The level of panic in this scenario can go sky-high if the message had confidential or sensitive information in it.
Message Recall could be a real blessing — afterall, it’s specifically designed to help fix embarrassing or even costly mistakes. But I have some bad news: In most cases the Message Recall feature doesn’t work, meaning your e-mail server won’t remove the recalled message from the inbox of the people that received it.
And on top of that, keep this in mind: By even sending a Message Recall e-mail notice, you are pretty much screaming to everyone that gets this notice that they want to immediately open and read the very message you don’t want them to read.
HOW TO AVERT THE PROBLEM So when and why won’t a Message Recall work on different e-mail systems? At the risk of oversimplifying, among other things it depends on these factors: the settings that have to be enabled in your e-mail client; the settings that have to be enabled on your e-mail server; whether the recipient has already opened the message; and whether it has gone to an Internet e-mail address or a mail server outside of your office. (In the last case, you’re almost always out of luck so don’t even bother trying a Message Recall.)
If you want the technical details for configuring recall settings on MS Outlook/Exchange Servers, see http://office.microsoft.com/en-us/outlook/HA010917601033.aspx. For IBM Lotus Notes and Domino V8, see www.ibm.com/developerworks/lotus/library/notes8-recall.
But let’s suffice it to say that odds of the settings and circumstances working out so that Message Recall could in fact pull back an errant message are about as rare as a total lunar eclipse. (I’ll save you a trip to Wikipedia — that would be on average about twice a year.) So then, how do you avoid ever having to wish that Message Recall would actually work and save your career?
Every time you are about to hit Send, pause for a second and ask yourself three simple questions:
- Do I have the correct persons in the To, Cc and Bcc lines?
- Did I attach the file I want to send?
- Have I said anything that shouldn’t go out in an e-mail? (If you’re not 100 percent sure, save the message to your Drafts folder and review it after you’ve cooled off.)
Practice safe e-mail, everyone.
If you're going to put it in the drafts folder, delete the outgoing address.
Point well taken. Here and there there are some somewhat more helpful technical solutions on the prevention side. Regarding the first of your three simple questions, Gmail and Google Apps users might want to check out "Got the wrong Bob?."
Our company, metaLogic Consulting, developed what IBM called the Cadillac of message recall for Lotus Notes – we call it Fetch Retriever. Our clients still continue to use our software over the email recall feature native to Lotus in version 8. With email recall, the tricky areas are whether or not someone has truly read the message (i.e. previewed versus opened)and also once that message hits the internet or a copy is taken offline, there is no turning back!
To me, this is just poor functionality design. Good to sell only.
The easiest and robust way to implement such a functionality would be to have a mail server retain emails in a "staging" queue for a tunable period, say of 15mn by default, delaying sending of email for 15mn.
The Message recall will have the effect to tell the mail server to remove it from that "staging" queue.
The option in the mail client, would be to "Send Immediately", skipping the 15mn wait, instead of a post-mortem "Recall This Message".