Email client reviews

Considering the age of email as a technology, and the plethora of clients available, the situation is tragic. Here is a line-up of the clients I’ve used the last few years, and the reason I stopped using each and every one of them. Some simplifications are made, such as in the use of words like “cannot”. Yes, there are often hacks to circumvent the limitations. No, I won’t go into why using a closed source, 4 year old, unmaintained, 3rd party plugin is a bad idea.


CERN uses Exchange, so Windows desktops come with Outlook 2003 installed per default. I’m an open source enthusiast, but at first I thought it was a good idea to use what my colleagues used (and continue to use).


  • Fast, probably because of close integration with the server
  • Saves message settings (such as flags) on the server, so I can set a TODO for when I get home or reinstall
  • User friendly wizard for filter rules
  • Integrated (CERN only) plugin to report spam and control spam settings
  • Working, simple predefined search folders
  • Good LDAP integration in right click menu


  • 32 KB to store filter rules is not enough!
  • Resets the reading pane settings for some folders willy-nilly
  • Cannot bounce messages
  • Not enough configurable (show headers, color encoding of fields / replies, etc.)
  • Cannot export settings to human readable file (I want to keep it in CVS)
  • Flags cannot be assigned names or meanings
  • Flags are not the same as in Thunderbird or Mutt, and are thus only visible in Outlook
  • Closed source
  • Cannot use regular expressions in searches / filters
  • Difficult to copy email addresses
  • Bad thread display support

Works for the most part, but is not “techie” enough. I want the open source geek edition!


This seems to be the most popular email client for open source enthusiasts. I’ve tried just about every version since 0.8 or 0.9, and the following points are from


  • Open source
  • Very configurable
  • Lots of useful extensions
  • Mostly plain text profile – Can be stored in CVS
  • Single click to mark as read / unread / junk / not junk
  • Meaningful labels
  • Supports standard flagging mechanism (same as Mutt)
  • Easy copying of email address
  • Good thread display support


  • Bad default training on the spam filter
  • Junk mail filtering can “self-destruct” without telling the user – Empties the training file and never starts learning any more
  • No visual representation of flagging
  • Doesn’t react to changes in flagging by other applications (Mutt)
  • Sometimes crashes or hangs on startup
  • Mail filters often break – Client crashes when they are applied

This is not version 1.5. This is 0.9 alpha.


I learned to use this textual email client when working for Orakeltjenesten. I could see why the other techies loved it – Stable and geekily configurable.


  • Extremely configurable! Examples:
    • Set Reply-to based on To / Cc
    • Include other config files
    • Redefine key bindings
    • Create new key bindings
    • Wanna backup to and purge all non-flagged mail older than two weeks with CTRL-o? Add

      macro index \\Co "<tag-pattern>~r>2w!~F\\n<bounce-message>"

      , and just hit d when it’s done.

  • Simple and clutter-less interface – This is the iPod of email clients
  • Human readable configuration and address book files
  • Stable as lead
  • Color coding available for everything
  • Very good thread support
  • send-hook . my_hdr X-message-flag: Outlook is bad for you, use Mutt

    – A classic

  • Open source


  • Doesn’t cache emails
  • *nix only – Windows clients are no longer maintained
  • No sophisticated flagging – Only boolean
  • Doesn’t do filtering – Nnnuuuuuuuh!

With filtering and some user friendly front-end, this would be the mail client of the century.



  • Fast search
  • Only browser needed
  • Settings online
  • Stable
  • Fast
  • Good spam filtering
  • Flexible labels


  • Simplistic filtering
  • Closed source
  • Page length limit of 100
  • Max 20 filter rules
  • Cannot backup settings or mail
  • No warranty
  • No extensions

Not enough configurable, and too bad filtering.

Digg 3.0 problems

After using Digg for a few months, I’m hooked. So hooked, in fact, that the following problems have been ignored until Digg 3.0 made them almost insufferable. For the record, I exclusively read the “All Recently Popular” RSS feed via Bloglines in Firefox on Windows XP SP2, on a dual 2.8 GHz PC with 512 MB RAM, with a 10 Mbps line.

Load speed

It often takes several seconds for a story to load. This is very annoying, since the browser locks up completely during that interval. Of course, all that JavaScript takes a while to process, but not everyone goes to Digg for the comments. It would be nice to be able to set up my Digg account (or have separate RSS feeds) to disable JavaScript.


This is the only feature of Digg I absolutely loathe. Especially the fact that I seem to have to login once for each section. Opening 30+ stories at the same time, it’s hard to see which ones are not logged in. And if several tabs are logged out, all but the last story are “lost” – All of them will load the same page (the last one which was logged out) when I log in. Re-reading 150-200 links is not my idea of fun…

The “popular” limit

Digg has grown a lot, and the RSS feed of popular items fills up faster than a Coke bottle with mentos. Nowadays, it seems about 150-200 articles per day end up in this list, and the quality goes down as a smaller percentage of users Digg each “popular” article. The obvious solution is to make the “popular” limit higher or user controllable. Here are some options:

  • Percentage of user count
  • Percentage of active users, for some definition of “active”
  • Some other function of [active] users
  • User-controllable feed, using parameters to control any settings
  • Separate “Very popular” list

No direct link

For some stories, the comments are not interesting, and it would be preferable to go directly from the RSS feed to the page in question. It would therefore be nice if you could include the direct link in the feed (or a redirect), perhaps the same way Reddit does. Incidentally, this would fix the login and load speed problems as well…