I don't normally do these kinds of posts on this blog, since I like to keep it very technology focused on factories, but I just had to share this - hoping it could help yourself avoid some of the stoopid mistakes like the ones I've made over the last few years.
Every now and again I make a real embarassing blunder in my email correspondence. It's happened a few times in the past, and I can see at least three scenarios that pop up every few months or so, and its at times like these you just want to bury your head in the sand, as your credibility tumbles.
The irony about cases 1 & 3 is that your error burns in the back of your retina as you release the mouse button over the 'Send' button - and just as the explicative's form in your mouth, and the sweat starts - "I didn't really do that, did I!?!".
Because your email client (mine is Outlook) is so optimized for sending email responses so quickly, you scramble around to try and find that 'Recall This Message...' command, which is never where you expected it.
[In case you are wondering where it is nowadays in Outlook 2007, you need to open the sent email, (hopefully it is in your sent items folder), then the command is on the 'Other Actions' menu - good luck, sods law is against you here.]
Anyhow, you are likely very doomed by this point - as your mail wings its way across the interweb. Most people nowadays are very quick to pick up their email (thanks to mobile devices), and all you can hope for is that the someone you didn't want the email to go to is either asleep or offline - yeah right! - both cases pretty unlikely in your present predicament.
An obvious solution to these problems is to delay the email from being sent, giving you that little bit of time to correct the err's in your ways. In Outlook, you have always been able to do this by setting the 'Do not deliver before' time in the Options of the mail.
The problem is that you have to do this for every email (per instance), and if you are in a rush for example - which we are most of the time, you may forget to do this for every mail. (It's a shame Outlook doesn't have this as a global setting).
For ages I have been meaning to create an add-in for Outlook that gave me 2 buttons on my mail, the first one (the big default 'Send' button) called 'Send' automatically delays the email for a configurable amount of time (say 10 min's), and a smaller button called 'Send Immediately' sends the email immediately (without the delay). You would also have an options dialog somewhere to configure the delay amount, and some other minor options that escape me for now.
However, I have not had the time to create this add-in and recently I was struck by this issue again - much to my demise.
I was speaking to a mate of mine at work about this last incident, and sharing the embarrassment, when he suggested you can set up a rule on your outgoing email to achieve the same thing.
I didn't really believe him at first, because if this were true, surely I would have heard about it before. This is surely a known user issue, and everyone who uses email (everyone then!) must have experienced this before, surely it would be out-of-the-box functionality and we would all know about it!
Anyhow I decided to check it out and to my amazement its real easy to setup. Here goes:
OK, and to test, send yourself an email message, and it should sit in your Outbox for the number of minutes you defined. To check this, open the email, and look at the email options, you should see that the rule has set the 'Do not deliver before' time to whatever in the future.
So, this solution is easy, anyone can do it and it doesn't require installing anything to each machine you run Outlook (for example at home and at work). The rules get updated for all instances of Outlook.
I have not tested this on OWA (Outlook Web Access), but I suspect these types of rules don't work in OWA.
The only issue I see, is that I don't have that 'Send Immediately' command I wanted for my add-in. In these cases, I will need to go into my Outbox and clear the 'Do not deliver before' flag on the mail per instance - bummer, but its probably a good thing in the big picture.