Archive for the 'Email' Category

Ending Email Distraction

Sunday, August 16th, 2009

In terms of our interaction, email used to be essentially snail mail that you could send and receive instantly.  But our interaction with email has moved far beyond this simple analogue of open mailbox, get messages.  The postman comes to my house once a day; whatever letters come, that’s all there is until tomorrow.  The mail is a daily ritual, a one-off thing.  Email is more like a constant trickle (or a constant stream or even a firehose).  I can check for messages as often as I like, and modern email programs have all kinds of features to allow incoming messages to announce themselves: some subtle, some not.  Mail messages are passive, but email messages have become active agents!  They flash notifications, make noise, or increase little red counters while vying for your (limited) attention.

 outlook notification

The pull of email is very strong.  For me, when I know there are messages in my inbox, I’m incredibly tempted to deal with them, or at least read them, even if I’m working on something important.  A passive inbox creates more than enough temptation for me; email which asks for my attention is too much.

The daily ritual is effective for regular mail because delivery times are measured in days, and not too distracting because you take care of everything in one go.  Dealing with email as it comes in might be very effective, but because of the myth of multitasking, it torpedoes productivity on anything that requires careful thought.  Every time we change from one task to another, it takes a while to regain focus.  Some studies have suggested this is upwards of 15 minutes!  Even if the total time you spend on email is the same, the more you break it up throughout your day, the less other things you’ll get done.

Many popular email programs have these distracting message notifications turned on by default.  Here’s how to turn them off:

Microsoft Outlook 2003/2007
Tools > Options from the main menu, click Email Options on the Preferences tab.  Then click Advanced Email Options.  In this dialog box you can untick any (or all) of the options under When new items arrive in my Inbox

Mozilla Thunderbird
In Windows this is under Tools > Options > General > When a new message arrives.  For Linux, it’s under Edit > Preferences…,  on Mac OS X, it’s Thunderbird > Preferences…

Entourage
Entourage > Preferences > Notifications and untick all the unwanted notifications.

I also like getting my email on the iPhone.  It’s great to be able to read and sort messages while on the bus or waiting in line, but I’d go nuts with it constantly alerting me of incoming email.  You can disable these under Settings > Sounds…

Punting Password Security

Monday, September 22nd, 2008

There’s another problem with passwords which deserves its own post: what do you do when you forget one?  It’s bound to happen, right?  With so many passwords floating around in our heads, we inevitably forget one entirely or forget which password goes with which account.

Sites can’t just tell you to get lost when you can’t remember, so they need a Plan B to authenticate that it’s really you, and not some attacker.  Now, if you have an existing relationship with the entity you’re trying to reset your password, it makes it much easier.  If I forget my login password at work, I walk down to IT and either talk to someone in there that knows me, or show somebody my ID card.  They reset my password, and I’m off to the races.

Yes, by punt I mean the American sense of the word.

But most sites on the internet don’t know me and haven’t issued me any kind of physical token I can use to prove that I’m me.  So, they punt.  They fall back on one of two methods: security questions, which are the slow-pitch softballs of the security world, or they simply pass the buck to somebody else to authenticate you, namely, your email provider.

Security questions are basically another form of password; information which is nominally secret, but much easier for you to remember.  The age-old bank security question of your mother’s maiden name, or the name of your first pet, or your elementary school.  Because these are usually questions about your past, they’re easy to remember, but also very easy for an attacker to guess or find out the answers.  The well publicised break-in on VP candidate Sarah Palin’s Yahoo Email account provides a good example of why security questions aren’t really secure at all, if the alleged first person account of the break-in is to be believed:

The intrusion, according to this account, was carried out via Yahoo’s password reset feature. Though the original post has been deleted, it was copied and reposted to several other blogs.
In the post’s telling, the exploit took no more than 45 minutes and simply required searching the Internet for basic personal information, such as Palin’s zip code, birth date, and where she had met her husband.

Of course, being a VP candidate is sure to have made it easier to find the biographical information required for this attack, but the point is that the answers to security questions aren’t usually well kept secrets, and enough digging by a determined attacker can punch right through them.

Many sites forgo questions and use the strength of your email authentication.  They send you an email with a temporary password, or a code to enter to be able to create a new password.  This means that your email account should be the most sacred of all your passwords—strong, unique, and changed often—because if it is compromised an attacker will have “the keys to the kingdom” of many of your other accounts.  Of course, this style of authentication doesn’t help email providers like Yahoo!, Gmail, or MSN/Hotmail.

And, in this respect, Information Cards are no better.  They can be lost in a computer crash, accidentally deleted, or not transferred to a new computer.  This means that sites that use them still need to punt on security in exactly the same way.  There are such things a “managed information cards,” which are issued and secured by a trusted third party.  If the user has an existing relationship with the third party (their employer, for example), they can be reissued access in a more secure way.  But this is really no different than resetting a site password via your work email account (on which you can gain access securely).  In both cases you and the site agree that if you lose your credentials, then you both should trust your employer to securely deliver you new ones.

Photo is Eric Tipton from the Duke University Archives.  Licensed under Creative Commons.

Outlook Send-Mail Infinite Loop

Saturday, August 30th, 2008

Maybe Microsoft should move its headquarters to 1 Infinite Loop.

This morning, while trying to send out some mail in Microsoft’s Outlook 2007, I noticed that after nearly 10 minutes, the message I tried to send was still sitting in my Outbox.  When I clicked “Send/Receive,” like ya do, Outlook decided to get stuck in an infinite loop of trying to send, failing, and then trying again without any kind of warning, I racked up dozens of sendmail tasks in the “Send/Recieve Details” dialog in a few seconds.  I had to kill Outlook from the taskbar.  This was no ordinary glitch: I tried restarting Outlook, switching back and forth from Offline Mode, and sending from a different account, to no avail.

Creating a new message, readdressing, and copying and pasting my email contents into the new message seemed to work.  Although, I can’t help but wonder if several of my friends got multiple (hopefully not dozens!) of copies of the email.

Then later, it happened again!

Long story short, after some furious google searching, I found some hints of explanation.  It seems that sometimes (perhaps due to ActiveSync tomfoolery) the Address Book in Outlook gets corrupted, and some display names are orphaned, no longer associated with an email address.  When you address an email to one of these orphaned names and click send, it sets Outlook into this infinite loop.

This is a pretty huge failwhale on Microsoft’s part on several levels.

Firstly, the Address Book, “what about it?” you ask.  “Isn’t that just your Contacts folder?”  As far as I can tell, no.  The Address Book is some vestigal part of Outlook code which is what is actually invoked to translate names into email addresses, rather than just using the Contacts database directly.  No one ever opens their Address Book, so far as I can tell (although there is a shortcut for it: Ctrl+Shift+B).  Everyone manages their contacts and email addresses in the contacts folder, and behind the scenes Outlook relies on some software scorcery to keep the two in synch.  Obviously, this breaks from time-to-time.  From a humane computing perspective, this is particularly cruel—creating two places to keep email addresses when one would do. Then, allowing the synchronization break without any warning until it causes a problem like:

The Infinite Loop: Seriously, Microsoft, when a display name pulls up a null from the Address Book, the best you can think to do is just try the whole send-mail process over again?  No error message, no looking to the Contacts folder for the address, no prompting the user for how to handle this, just keep banging your head into the wall.

And not only that, but the most information I can find about it on Microsoft’s site is from a post in October 2007 to Microsoft’s forums.  This means that this bug has been burning people for nearly a year with no visible action on Microsoft.  No Knowledge Base article explaining a work around, just some forum posts to wade through to try and pick the most appropriate solution.

For those who came via google or elsewhere looking for a solution, I’ll explain what I did to (hopefully) clear it up.  Basically, we’re going to manually clean up the Address Book.  This will be fine if there are only a few entries that need cleaning; I had about 2 dozen, If there are lots that are b0rked on yours, you might want to try some ideas listed in this thread.

  1. Go to Offline mode (File -> Work Offline), and delete any offending messages from the Outbox.  Save the text first, so you can resend, by copying and pasting into Notepad or similar.
  2. Open the Address Book (note: this is not the same as the Contacts folder).  Tools -> Address Book, or Ctrl+Shift+B.
  3. You should see a list of names, display names, and email addresses.  Corrupt entries will be any that have the email field left blank.  Note that any Contacts you have which don’t have email addresses saved should not appear on this list at all, so anything with a blank email address is a corrupted entry.
  4. Find a corrupted name, and then close the Address Book, go to your Contacts and open the entry for the name you found.  You’re going to copy the email address to the clipboard (Ctrl+C), clear the email field, then save the contact without an email address.  Then reopen the contact and paste the email address back in place (Ctrl+V), and save again.  This should recreate the entry in the Address Book with the correct email address.
  5. Rinse, repeat until all corrupt entries are fixed.  (You can ignore Distribution Lists, they won’t have an email address listed.)

Shame on you, Microsoft, for wasting over an hour of my time diagnosing and repairing Outlook from a bug that should have been fixed months ago.

Email is a noisy channel

Monday, August 11th, 2008

Photo by jek-a-go-go, CC Licensed

We’re used to computers zapping data back and forth with (mostly) perfect integrity. When you send a email, there’s no doubt that it will reach your intended recipient with all your crafty sentences completely intact.

But!, even though your computers are good at transferring the information without loosing any, your recipient probably isn’t. Humans don’t remember everything they read, if they read the entire contents of your email in the first place. Being an effective communicator over email means treating it as a noisy channel; a lossy medium. You have to assume that parts of your message won’t get through. Things that aren’t emphasized won’t get remembered; things at the end of a long message won’t get read. Some of your recipients will be so overloaded with email, or neglect it to such an extent that you will be lucky if they open it at all.

So what’s a sender to do? You can employ some strategies analogous to how computers transmit error-free messages across noisy channels.

  • Structure your messages so that they degrade gracefully—put the most critical information early in the message and emphasize it. Put the punchline in the subjectline or as the first line of the message. If you’re making more than one point in your email, make sure they are self contained: don’t leave a critical detail that changes the meaning of the message for the end.
  • Keep things as brief as you can. This will make it less likely that particularly busy recipients will put off reading your email until later, then forget about it.
  • Redundancy. Put an executive summary at the top of your email (preferred) or a punchy conclusion at the bottom. Or, as much as I hate to admit it, you can send reminder emails.

Email is a powerful medium because it’s so easy to send stuff down the pipes, but this is a double edged sword. If you want your message to be received error-free, you’ll need to put in some effort in making it well crafted. And if your message is very important, resist the urge to put “IMPORTANT” in the subject line, or add that annoying red exclamation mark of “High Priority.” Consider redundancy in channels as well—use the bulletin board, intranet, RSS feeds, Twitter, or even a good old fashioned phone tree to get the word out. If you don’t know the recipient and their email habits well, then prepare for the worst.

Photo by Jek-a-go-go, CC Licensed.

Teaching email

Monday, June 23rd, 2008

I remember my first lesson on how to write a letter: how to address an envelope, the rigid explanation of formatting differences between business and personal, the impressive-sounding terms for the parts of a letter (the salutation, the complimentary closing, the postscript).  It was in elementary school language arts class.  We wrote letters and the teacher marked them up in red pen.  Commas missed after “Dear Mr. President,” and things like that.

They understandably assumed that letter writing would be one of the most common ways that I expressed myself to other people.  Little did they suspect that letter writing would be almost entirely supplanted by the writing of emails.  In fact, letter writing is still important because it is so infrequent.  It is a way to get noticed.  Writing a letter, to a company which has pissed me off, to my senator, or to a company I want to hire me, is the epistolary equivalent of breaking out the big guns.  Far, far more pedestrian is the humble email to which most of my written communication is consigned.

As regular readers may have guessed, I’m often appalled at how bad some people are at communicating through the medium of email.

This is why I think that email should be an important part of elementary education.  And, it should be taught by teachers of language.  (Tangentally, in my day they called this subject “language arts,” which I suspect is a rebranding of the subject “English.”photo by adam79 I have no idea what they call it these days.)  Email is (or should be) no longer any more mystifying to a 10 year old than the postal service—so we don’t need computer/technology teachers to introduce it.  Using language to communicate is what email is all about, and kids will need more guidance on how to write emails than they will on how to send them.

Letter writing and email writing share a similar core, but should really be taught as distinct media.  A fundamental reality of email in today’s world is the sheer volume that people receive, unparalleled by letter-writing that preceeded it.  Most people will decide in a matter of seconds whether or not an email is worth the time to ever 1) read or 2) resond to.  In order to have any hope of getting their message across, students need to know how to write emails that sound out clearly among the constant noise—not an easy task for beginning writers!  They need to know the importance of writing good subject lines, how to get to the point quickly in the body of the email, and how to make it clear (and easy for their recipient to respond with) what they want.

They should be taught the (only slightly) technical details of email, just like we did for letters: how to address it, the parts (To:, From:, CC:, BCC:, Subject:, then the familiar salutation, body, closing), how to format not only original emails, but forwards and replies as well, the difference between HTML and Plaintext.  They should be introduced to all the fun that can be had with formatting, colors, fonts, pictures, hyperlinks and the <blink> tag, have their little hearts broken when it doesn’t display like they intended on their friend’s email client, and then be gradually weaned away from all the bling to find styles that fit the tone and purpose of the email.

If there are any elementary school teachers out there, I’d love to collaborate on writing some lesson plans for this. Get in touch!

Photo by adam79

Xobni: funny name, good times with Outlook

Wednesday, May 7th, 2008

A shot of Xobni\'s user interfaceIt’s hard to come up with a decent name for your web startup. Believe me, we spent ages brainstorming, arguing, deciding everything we brainstormed was crap, and brainstorming some more before we came up with a name for the web startup that I was very briefly involved in. Whatever name we ended up with must have been underwhelming because I can’t actually remember it sitting here in front of my computer 3 years later.

Even the big boys—who can pay slickery consultants to sit in a room and pontificate on made-up words that will jive with whatever freaky internet talk them kids are sending down the tubes these days—come up with ridiculous names for services and websites. Please allow me to Joost up my Hulu-craft and so that we may partake in a Qoop down the Jaiku.

In a world where every English word is already registered on the .com top-level domain, the makers of Xobni can be forgiven for spelling “inbox” backward and calling it a day.

If you use Microsoft Outlook (2003/2007) for your email, then Xobni (even in its currently beta incarnation) is definitely worth a look. At its core, Xobni is an email-search tool, but it is decidedly different in its approach than what you’d get with Google Desktop or Windows Search. Xobni’s interface is people-centric. I don’t mean this in a dopey television ad way; Xobni’s interface is primarily organized to show you helpful information about the people you email. When you preview a message in Outlook, Xobni’s vertical panel shows you information about the sender, along with the most recent conversations you’ve had, and every file you’ve sent or received from that person. It automatically parses telephone numbers from mail, so you don’t have to go hunting, although this feature doesn’t always find them, in my limited experience so far.

It does take up quite a bit of screen real estate, and I feel like my preview pane is now slightly too narrow, but it does pack a bunch useful stuff into the small space. My geeky, data-visualization-loving side can’t help but appreciate the histogram of the sender’s emailing habits by hour of day, but I can’t yet to claim I’ve actually found this to be useful. One day!

Oxford’s upcoming groupware project

Thursday, May 1st, 2008

OK, so I’ve blogged previously about how much email at Oxford sucks. But, as I alluded to, and as commented by our friendly neighborhood Oxford-IT-guy (thanks for reading, BTW), Oxford University Computing Services has a plan! The call it the Groupware for the University Project, or just groupware. Groupware is software designed to help groups collaborate. It’s been around forever, even though the name is new; and I guarantee that you’ve used it.

Email was the original groupware. It was the first “killer app” for the internet, and the vast majority of traffic on the early ‘net was email. Groups of researchers used it communicate in those early days, and today it is as mainstream as chocolate pudding. Usenet came next, in the 80s. It was a kind of discussion forum arranged around categories called newsgroups. Although it is still in use today, it has largely been supplanted by newer developments like web-based forums. The point is that lots of software is groupware: instant messanging, wikis, etc. So we all use different types of groupware for different purposes or for different groups. Other than email, there has been no University-wide attempt to give everyone a common set of groupware applications.

OUCS plans to begin deployment, according to the project page, in June of this year. However, the user requirements document was finalized in February, so we already have a pretty good “high level” idea of what the University hopes to accomplish. Even though the document breaks up requirements into 8 “components,” from a user’s perspective, there are 5 main applications:

  1. Email
  2. Calendaring and Resource Booking
  3. Contact List
  4. Shared Data Repository
  5. Interface to Student Information System (SIS)

(The other 3 requirements components cover all the applications and are: encryption support, remote web access, and mobile access.)

Email is pretty self-explanatory, but there are a couple requirements worth noting:

  • webmail needs to support a range of functions “typical of leading/common current webmail clients.”
  • must have the ability to synchronize with mobile clients (e.g. syncML, Blackberry, ActiveSync)
  • support for shared mail folders

The last one is particularly important for on-campus student groups, who often want to have an email inbox for the group which can be monitored by all the officers.

Calendaring is the ability to keep and manage one or more calendars which are stored on the server and accessible from either the web interface, a mobile device, or a desktop calendar client (iCal, Outlook, etc.). This becomes groupware when you have the ability to share your calendar with people or groups to aid in scheduling. Unfortunately, there isn’t a requirement to be able to schedule meetings with a visual representation of people’s Free/Busy information (generated from their calendar, if they choose to share it). This is one of my favorite features of using a system like MS Exchange Server. Let’s hope whatever we get has this feature anyway. Resource booking means being able to see when resources, like rooms or projectors, are unscheduled, and the ability to reserve them from the groupware. That’ll save a lot of time in trying to book tutorials.

The contact list is just like it sounds—an address book. They’ve included some much needed requirements that it is straightforward to import and export from the contact list. They’ve also mandated that the groupware interact with something called the Core User Directory, which I can only assume is the central University Admin’s database of all the people at Oxford. This should hopefully mean you can find contact information for people who are members of the University very easily.

The Shared Data Repository is a fancy name for a place to upload files you want to share with people or groups. Notably, though, it is required to have version control (yes!), be searchable, be cross-platform, and have directory-level access control.

The interface to the Student Information System is an integration requirement with Oxford’s existing system. The SIS is where students can look up administrative information about their status and update their contact information with the University (among other things).

I appreciate that OUCS has been careful to include requirements about platform-agnosticism: there would otherwise be the potential of many a Linux user being left out in the cold. The requirement that all groupware functionality be fully available via the web, securely, from any internet connection is a bold one, and I’ll be interested to see what software vendors come up with. I’m also pleased that at least for the email and calendaring they’ve explicitly listed mobile access as a requirement. It would be nice to see for the contact list as well, but there is a requirement about the groupware being compatible with 3rd party interfaces like Intellisync, so I’m hopeful this one will also end up being in the final implementation. I’d also liked to have seen a standards-based (i.e. Jabber) instant messaging system. I know that everyone already has their own favorite IM service/client, but the integration with the user database would make it much easier to find and make contact with people.

I have one final complaint: no wikis?

I’ll end by noting that I’m on the email list for the User Consultative Group, and we’ve just been having a discussion about “use cases” to send to software vendors.  So, I remain somewhat skeptical about them having a solution shortlisted and then chosen by June. My guess is that implementation is delayed until late summer at the earliest—but this is Hofstadter’s Law-style pessimism, so take it with a grain of salt.

Why Oxford’s email sucks

Thursday, April 24th, 2008

I’m a student at the University of Oxford, and as is standard practice, they provide a email system for staff and students. It’s called Herald, and I assume it’s a home-grown email server that has evolved from code written in the 1980s.

It’s a piece of crap.

I kid, I kid! Admittedly, that’s probably dropping a little too much hate on its poor aged lines of God-knows-what language. It has basic features and gets the job done… most of the time.

But the internet means so much more to so many more people these days, and Herald isn’t equipped to let people make the most of it. Take webmail, for example: ugly, testy, difficult—these are words which spring to my mind when I think of Herald webmail.  You’re stuck sending and receiving in plaintext, and the interface is offensively bad.  It was never supposed to be this way—Herald was designed to be used via your email client of choice, a hulking server hiding in the shadow of a more carefully crafted interface.  But since the early days of Hotmail, Yahoo! mail, Netscape and the rest, webmail has been a primary avenue of accessing email.  Some people prefer it that way, and its easy to see why: one interface to learn which can be used on any computer with an internet connection and a browser, and no obnoxious setup steps (IMAP or POP3? SMT-what? SSL-port-who?).  And since gmail came on the scene a few years back, there’s simply no reason to believe that webmail can’t be a pleasant experience.  Something is deeply wrong when free webmail services outclass what’s provided to you by the people you pay £10,000 a year.

But still, armies of my classmates here at Oxford use Herald webmail as their primary email.  They hate it, even if they don’t realize it.  I know this because it shows.  They use Facebook to send messages to one another.  That’s right, Facebook.  Facebook, with it’s terrible message editor, iron-fisted threading, and walled-garden take on communication.

But I’ve just been informed of a project in the works at Oxford’s computing services to change all that, and finally move beyond email and into the realm of internet collaboration.  These services have existed for some time now, and what Oxford is proposing isn’t anything groundbreaking—but they’re a hell of a welcome (if overdue) change.

I’ll blog more about them soon.

Critical information shouldn’t go via email exclusively

Saturday, February 16th, 2008

Sure, email is an easy way to send important information out to a large number of people. It’s almost too easy, and many people’s definition of “important” borders on ridiculous. The marginal cost in computing resources and effort to reach additional people is so tiny, it can be neglected in any reasonably sized organization. In many cases, targeting a specific subset of an organization is significantly harder than blasting everyone. For this reason (among several others) everyone gets too much email in the sense that the majority of it is either straight up spam, “important” information that we’re not interested in, or poorly targeted emails which don’t apply to us. I get tons of the latter at The Department, “To all Post-doctoral Research Staff,” (I’m a grad student; you’d think they’d have separate lists).

It’s easy to get overzealous in clearing your inbox when you come back from an afternoon away from your desk. I’m very good about reading my email, but enough is enough. Anything with that stupid red exclamation point or the capitalized words IMPORTANT or PLEASE READ in the subject line is on its way to the Deleted Items folder faster than my average ping to icanhascheezburger.com. There are people who let emails sit unread and undeleted in their inbox for days, nay weeks. Which brings me, finally to my thesis:

You can’t depend on email to convey critical information, especially if it is time sensitive.

Yes, email is easy. Yes, finding other ways of communicating with your fellow humans feels so 1989. But email is a congested medium and people find that a lot of it just wastes their time. Don’t blame your users for this! The solution is not to tell them they need to pay more attention to their email. The solution is for you to pay more attention to them. Take a multi-pronged approach which is appropriate to your organization. Are there noticeboards? Information screens? Put notes in people’s mailboxes, or post extremely critical information on the door as they walk in. Like this guy:

electrical shutdown

This, on the door to our office, got my attention. They were going to shut down the power the next day–would I have seen the email in time? Maybe. Would I have realized it meant me before deleting it? Maybe. Alan in building services, well done.

Sometimes low-tech is better than high-tech.

Anti-virus Email Footers

Wednesday, February 6th, 2008

Can I just say that among my email pet peeves (and believe me, they are numerous) is when anti-virus software appends a message to outgoing mail, along the lines of:

No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.5.516 / Virus Database: 269.19.20/1259 – Release Date: 4/02/2008

I copied this from a friend’s email, I won’t say whom. Remember, this is the sender’s computer which is appending this message. If my friend’s computer were infected with a nasty virus, which was spreading itself by sending email unbeknown to him, the virus could very easily add a similar tidbit to the end. Rationally, seeing such a message at the end of the email should in no way affect my confidence about whether or not this email contains a virus. It’s the equivalent of writing “This is not a mail-bomb,” on the front of every package you send.