Big Brother is Watc…[Recalled]
The big kerfuffle over Amazon’s Kindle Team removing several books without warning from users’ devices (story and link at the end of the blog) has lead me to think about the various time clients have used the Recall Message feature. Typically, they have found that it behaved just slightly better than opening their office door and screaming “NOBODY READ THAT!”
There are a lot of great reasons to use Recall Message in Outlook and Exchange. Perhaps something was sent before it was finished, accidentally clicking Send without typing in that last bit of information. Maybe you meant to add an attachment but did not – in which case may I suggest some of the great tools at Sperry Software. You may also have accidentally hit Reply All instead of Reply, or added in a group email list via AutoComplete instead of the one person you wanted to send email to. All of these are legitimate reasons to really want to get the email out of everyone’s Inbox.
Years ago, Microsoft attempted to build the functionality of yanking back an errant email on command. It required (and still requires) that you be using Outlook in Exchange Mode, and a Microsoft Exchange Server as your email platform. When first introduced, this worked great. There was no such thing as a preview pane, you were always using an Exchange Server and MAPI for communication, and folks were probably online and connected since there was no Cached Mode.
The issues arise when you look at what is required for a Recall attempt to succeed:
- The user must be online and connected to the Exchange Server
- They must not be in Cached or Offline Modes
- The message must be unread in the recipient’s Inbox (including unread by the Preview Pane)
- The recipient cannot have moved the message to another folder (unread or otherwise)
- They must be using MAPI. Even POP3 or IMAP on an Exchange Server won’t count.
So, as you can see, since the majority of email users these days do not meet one or many of these requirements, Recall Message will fail for the majority of your users. What they will see is the original email (unchanged) and a notice saying you would like to recall the original email. This can often be just as embarrassing as the original gaff, as it acts as a glaring exclamation point that someone made a goof.
One more note, Recall Message will not impact the copy of the information on a Blackberry or other 3rd-party Smartphones and mobile devices. So even if the user’s desktop has all the requirements met, they’ll still have a copy of the message (and the recall request) sitting on their mobile device.
In the days of Exchange and Outlook with MAPI connections being the only conduit to email, Recall Message was a great way to manage errant information. Today, with so many ways to connect to any mail system, including Exchange Server, this feature has lost its usefulness and created a false sense of security. Remember, if there is a chance that someone’s using a non-Outlook client or not meeting all of the requirements above, you will not recall the mail. An ounce of prevention is your only cure these days.
As for the Amazon gaff, for those who did not see the news: Amazon recently pulled all the books by a major author and deleted them off all Kindle devices that held them. This was due to someone posting the books on the Kindle store, without the publishing rights needed to earn money from them. Once Amazon realized what was going on, they of course stopped selling all the books from that vendor. Unfortunately they also removed all the digital copies that were stored on users’ Kindle devices without mentioning it to the Kindle owners. They did refund everyone’s money, and they did send out an explanatory email, but not until several days later after the blogosphere detonated with Amazon hate postings.
Frankly, Amazon’s user agreement does say that they reserve the right to do exactly what they did. I can’t fault them for heading off trouble (in the form of a copyright litigation) at the pass. However, it could have been handled a lot better, with more information supplied immediately to end users about what was going on and why. Amazon has promised to make this process much more transparent so that next time there is no confusion.
The reason there was such an outcry about the process this time (as it has happened in the past, quietly and without fanfare or hate mail)? The author in question was George Orwell, and the books were the likes of 1984 and Animal Farm. Both of these books deal with subjects like retroactively removing information that didn’t meet the criteria of an overarching body of government or law.
From Dictionary.com:
Irony: an outcome of events contrary to what was, or might have been, expected.
Labels: Exchange, Exchange 2000, Exchange 2003, Exchange 2007, Outlook
0 Comments:
Post a Comment
Subscribe to Post Comments [Atom]
<< Home