Fastmail sale to Opera: the story from one of the owners

This started as a post to hacker news, which has now been expanded to cover some history and give some background to the Fastmail company and the sale to Opera. I’m one of the main developers and was one of the (now previous) owners of Fastmail. This post is partly for historical interest, and also to give the Fastmail community some insight into the future of the service.

Starting Fastmail

Fastmail started around 1999 when Jeremy Howard prototyped the first version and brought me on board to help develop the website. While both of us were reasonably experienced programmers, neither of us had done any web development. When we looked at the way to develop websites – CGI scripts in those days – we didn’t really like the way they worked, so I ended up developing a web framework to help make the application development easier. We still use that framework today. While it’s a bit esoteric, it has served us well and includes some features that are fairly unique, even to this day.

Jeremy had come from a management consulting background, and so had spent a lot of time onsite with customers. While email was a very important part of getting work done, he found the options available very limited. In those days, people could either get basic POP email from their ISP, or free but slow and ad-laden webmail sites (eg. Hotmail and RocketMail) that had less features (no POP, SMTP and certainly no IMAP). So we decided to concentrate on being a premium email provider that targeted users that wanted a professional service with lots of features (multiple personalities and signatures, aliases, plus addressing, sub-domain addressing, filing and filtering emails, etc), a fast interface (no ads, no graphics), open access to their email (POP and IMAP support) and solid customer support – and were willing to pay for it.

Building and growing the service

The original implementation started on one server at rackspace.com, and we started to let friends use it. We then started to publicise it more widely, mostly via word of mouth and on the forum Edwin helped us set up at www.emailaddresses.com (now www.emaildiscussions.com). We offered the service as free while building out the application, but from day one we told users that it would be targeted as a paid service.

With only myself and Jeremy as developers, customer support, system administration and forum support, it took us a while to get to the stage where we were happy with the service and ready to bill users, which started in 2002.

One of the things that the founders tried to avoid was taking on external debt, and Jeremy used his savings to fund the initial development. Initially I was just employed as a programmer, but with the successful launch and growth of the service and the work that required, it was decided to form a company, and bring myself and another person (Bruce Davey) in as the owners. Later on, another person would also buy in to the business, creating an equal partnership of four people.

Over the next decade or so, Fastmail continued on a fairly simple path. We kept building up the service, adding features and trying to scale to more users. We tried a few times to bring on more programmers, though we had mixed success with that until we finally built a small and core group that has been stable for the last 5 years or so.

As a side note, a few years back a friend lent me a book called The Beermat Entrepreneur. If you’re thinking of starting a small business, especially IT related, I think this book is a great read. It may have first been written almost two decades ago (an eternity in Internet time), but even with my single data point, the advice in it really resonated, especially the parts about people.

It talks about the 5 core people, the entrepreneur and the 4 cornerstone people you need to cover technical skills, delivery (operational side of the business), sales and finance. I can really see how each of those roles is important to a business. Jeremy was definitely the driving entrepreneurial force, always pushing the big idea. Bruce was our financial controller who made sure that we sold things for more than it cost to run them (important if you want a business to survive!) and I was the technical lead.

I think initially we lacked the delivery cornerstone, and were lucky to find Bron who brought a structure and repeatability to our setup that allowed us to recover from our small disaster in 2006 (2-3 day outage for a big chunk of users) to build the incredibly reliable and solid infrastructure we now have to deliver our service. The one thing we should have done from the start was to have someone in charge of sales. After the initial success from word of mouth, I think we expected sales to keep accelerating. In hindsight, it’s clearly the thing that we never executed well.

Instead of trying to do sales our self, we tried to get other people to do it for us. We did that by creating a co-branding system that allowed people to resell the Fastmail email service under a completely different brand with a customisable look and feel. Unfortunately that was a failure. Setting up a new co-brander took too much work, and every co-brander we tried was worse at sales and marketing than we were. They often expected to be able to just set the brand up, and gain users with little or no effort.

Recent status and changes in the email market

Fastmail has always been a small company. Today there are still just 3-4 main developers (myself, Bron, Richard and just in the last year, Kurian), and a couple of support staff (Yassar, Vinodh & Larry) scattered around the world. Despite (or possibly because of) those limited resources, I think we’ve managed to build a great product with lots of niche and powerful features as well as loyal users. We’ve also been incredibly reliable, especially in recent years, as we worked hard to make sure that we learned all we could from the shortcomings that led to the outage event in 2006.

Fastmail has been nicely profitable for many years, but not spectacularly so. As the above paragraphs show, we’re mostly technical and support people, and we don’t have a marketing or sales department that can grow our customer base significantly. We did try recently, and I have to thank Jack Miller for the hard work he put in in that area, but unfortunately it didn’t work out. Realistically only business accounts can have a reasonable return on any sales investment, and we really should have developed our business product 3-4 years earlier than we did. We were slow to enter that market and behind the leaders.

Again I think this relates back to the lack of a sales cornerstone again. Rather than having someone testing to market to see what profitable areas we should be attacking, we probably preferred to spend our time building neat technical stuff, fixing that edge case bug, or doing that fun thing… we’re really just geeks that like working with technology.

In retrospect, I think we had to face facts a bit; we were a small fish with limited resources in a market that has become vastly more competitive in recent years. We also needed to invest a large chunk of time and money in updating our interface and adding new features, especially better mobile synching, if we were to take that next leap.

Approach by Opera

Coincidentally, it’s around the time that we were considering our options that Opera came along and started a conversation with us. Despite being half a world apart, there turned out to be a lot of fit between our companies. They use a lot of perl, as do we. They’re a company run by technology people, creating a product that’s loved by geeks, is highly customisable, has a loyal fan base, and despite its small size, punches above its weight. I think that summary pretty much describes Fastmail as well.

So the timing was right, and Opera have an interest in picking up email as a core competency as well as a number of ideas about what they want to improve and what they want to build. As the other Fastmail staff are also interested in new opportunities, we are all making the transfer and becoming Opera staff and are committed to working there for several years at the very least. There’s already plans for some staff to move to Norway to work, a change of life after 5 years of just the 3 of us in a single office (apparently the Norwegian lessons are paying off… Jeg vil gjerne et øl til).

Looking forward to the future

It will be an interesting change, and something new which I’m looking forward to. I’ve been working for Fastmail for 10 years now. It’s been a great time. I’ve loved building the product and the company. Like anything, there’s been ups (it’s fun developing a site that customers really love and tell you about) and downs (some people are addicted to being able to access their email at all times, and running a 24/7 email service means that if people can’t get to their email for even just 1 minute, you’ll start hearing about it). After 10 years, it’ll be strange having a boss again. I’ve met a bunch of the Opera people, and it’ll be really great working with them. I know the other staff are also looking forward to working with the Opera team.

It will also be great to be able to work with Neil Jenkins again, who is also going to work for Opera having nearly finished his university studies. He worked for us over a couple of summers, and basically designed the entire "new" web interface, all the HTML, CSS and JS. We’ve already got 80% of a whole new AJAX interface done (remember in programming though, the first 90% takes 90% of the time, the remaining 10% takes the other 90% of the time), and I’m looking forward to completely finishing that work.

Of course there’s lots of other work that we’ll be doing with Opera, some of which I can’t comment on at this stage, but some of which we’re already working on.

Over the past few years, Bron has probably become the worlds expert on cyrus, the IMAP server we use. Recently he’s been refactoring large sections of the code to make it even more stable and RFC compliant, and adding new code to reduce the amount of IO required (eg. make it faster), and radically reduce the amount of bandwidth required for replication, which will be very useful in a multi-data-center setup.

Richard has been working on making sure every part of Fastmail is Unicode compliant, which will allow us in the future to translate the interface to different languages, and will finally mean that non-english folder names can be displayed correctly in the web interface.

As mentioned in the original blog post about the sale, FastMail.FM will continue to run and grow as the reliable email service you’ve known for over 10 years. Opera have clear plans for the future, and can help provide significantly more resources to build a bigger and better infrastructure and provide even more features.

Rob Mueller <robm@fastmail.fm>

Updated “Migrate IMAP” on beta server

We’ve made some updates to the Options –> Migrate IMAP feature that are currently on the beta server. Certain edge cases that were causing problems have been fixed up, and there’s now a “No duplicates” option as well. When enabled, as each folder is migrated, the migration code will first check if the folder exists locally, and if so, retrieve a list of Message-Id headers. It will then not download any remote message with the same Message-Id. This can be useful for avoiding large numbers of duplicate emails being downloaded if for some reason a migrate only partially completes, or for some reason you already have some messages downloaded from a remote server.

Please email me (robm@fastmail.fm) with feedback if you’re able to test this feature. Assuming there’s no issues, this will be rolled out to production soon.

IBM X3550 M2 or X3650 M2 and Debian/Ubuntu

We’ve been long time IBM hardware users. In general we love IBM hardware, it’s rock solid and just runs and runs. Being able to get 24×7 support contracts with a 4 hour response time for someone with replacement parts to be on site in case of a problem is great as well.

However IBM also have a down side. Often their Linux support is limited to Redhat and SUSE installs and the kernels that go with them. In some cases that means that they only distribute binary blob drivers which only work with the particular kernel and version distributed by Redhat/SUSE. Because we like to use Debian Linux, and also to compile our own kernels from source with just the modules and features we need, a binary blob driver or a driver that only works with Redhat/SUSE kernels is unacceptable for us.

We discovered this problem the hard way with our first X3550 purchase, which came with a ServeRAID 8k-i controller. It turns out that controller was based on some LSI “fakeraid” chipset which needed a binary blob driver (can’t find the link right now) and thus we couldn’t get it to work sanely. We ended up returning the machines.

On the other hand, the ServeRAID 8k controller (note the difference, not the –i version) is actually completely different, and works fine with any Linux kernel with the vanilla open source AACRAID driver. We’ve bought almost a dozen machines with the 8k controller and they’ve all worked really well.

Now however, the X3550 and X3650 machines have been replaced by the newer X3550 M2 and X3650 M2 models, which update the CPUs and motherboards to use the newer Nehalem based CPUs, as well as replacing all the available ServeRAID controller options with new ones again :(

  • ServeRAID-BR10i SAS/SATA Controller (3577)
  • ServeRAID M5014 SAS/SATA Controller (3877)
  • ServeRAID M5015 SAS/SATA Controller (Battery not included) (0093)
  • ServeRAID-MR10i SAS/SATA Controller (3571)

We’re having trouble finding much information about any of these controllers, and what support there is in the vanilla Linux kernel for any of these controllers. If anyone has some good information about vanilla Linux for these controllers (or lack there of), please email me at robm@fastmail.fm

Update: Someone from the IBM Linux Technology  Center passed on the following useful information to us that others might also find useful.

  • ServeRAID-BR10i SAS/SATA Controller (3577)

    LSI 1068[E] support has been upstream prior to 2.6.14 which means that this controller is support by all newer Ubuntu versions. The driver for this card is mptsas.

  • ServeRAID M5014 SAS/SATA Controller (3877) / ServeRAID M5015 SAS/SATA Controller (Battery not included) (0093)

    Both of these are supported by the same megaraid_sas driver which went upstream in 2.6.27 (megaraid_sas version: v00.00.04.01-rc1 or newer), which means these controllers are supported by Ubuntu 9.04 (based off 2.6.28)

  • ServeRAID-MR10i SAS/SATA Controller (3571)

    LSI 1078 support has been upstream sinse 2.6.16 which means this controller is also supported by all newer Ubuntu releases. The driver for this card is megaraid_sas (v00.00.02.04 or newer)

Improved email address tokeniser on /beta/

The new web interface attempts to convert email addresses put in the To/Cc/Bcc boxes on the compose screen into “tokens”. However there were a number of bugs with the current implementation listed on our wiki bug page:

  1. Email addresses surrounded by ‘ (single quotes) were handled poorly, partly disappearing, but still being left in the data sent back to the server
  2. Email addresses where the “phrase” part had more than one , (comma) in it were split incorrectly. For example: “smith, john, help center” <johnsmith@example.com>
  3. Email addresses where the “phrase” part had a angle-bracketed address were handling incorrectly. For example: “<johnsmith@example.com>” <johnsmith@example.com>

I’ve now completely rewritten the address parser, and put it on our beta server for testing. The new parser fixes all of the above problems, should be more resilient to odd address formats, and now allows you to do things like paste a list of email address with only spaces between them (rather than having to put commas) and it should tokenise them correctly.

If you come across any new problems, please email me directly at robm@fastmail.fm with details including an example of how to reproduce the problem and I’ll look into it.

Update 16-Apr-2009: Since there were no reported problems, I’ve now rolled out the new tokeniser to the production servers.

Help beta test new web interface

For the past year, we’ve been working on a large overhaul of our web interface. With the help of a great designer, and feedback from our users, we’re now ready to release the interface for general beta testing by all users.

The beta site is available here – http://www.fastmail.fm/beta/ – you can login using your regular account username and password.

  • Overall features
    • Professional look with cleaner layout, reduced clutter and simple icons to make common actions clearer
    • More consistent layout between screens (eg. navigation bar always available, common sidebar)
    • Javascript used to improve user experience, but still works fine without
    • More semantic HTML makes future stylesheet (look and feel) customisation easier
    • Significantly improved mobile display on modern mobile devices (eg. iPhone, Opera Mini, Opera Mobile)
  • Mailbox screen
    • Much better keyboard support – navigate using keys j/k/x/o/Enter, action menu via . (fullstop), search email via / (slash), search folders via , (comma)
    • Better auto-sizing to screen size to display more of the message subject
    • Cross folder searching available
    • Advanced search syntax available (eg. from:john subject:dinner since:”1 week ago”)
  • Message read
    • Much better keyboard support (like mailbox screen)
    • Attached messages shown inline
    • Attached images shown as thumbnails
    • Better integration with file storage to save attachments
  • Compose
    • Address book auto-complete and address tokenisation
    • Improved HTML editor
    • Auto-saving of drafts
    • Background upload of attached files
    • Improved spell check
    • Separate reply/forward quoting options
    • Default font face/size for HTML email

For more details, please see our new interface wiki page. To report bugs/issues, please see our new interface bugs page. We encourage all users to give the new interface a go and report any issues on the bug wiki page.

We plan to eventually roll out the new interface to http://www.fastmail.fm so all standard logins use the new interface. Depending on feedback, that should occur in the next month or two. We plan to run the old interface for 3-6 months after the changeover, but will eventually decommission the old interface.

If you have any particular comments you want to make about the new interface, please email me directly at robm@fastmail.fm.

Instant Messaging Server (Jabber/XMPP) available

FastMail is now running a Jabber server for all users. Jabber is an open-standard instant messaging protocol (also known as XMPP).

You can read more about Jabber here: http://www.jabber.org/

Our Jabber service is configured to allow S2S (server to server) communications, so you can use your email address as an instant messaging address and connect to users of other XMPP compatible chat systems (including google talk, livejournal, and of course jabber.org). Currently there’s no way to connect with proprietary messaging systems like MSN, Yahoo, AOL, etc. However there are a number of multi-protocol instant messenger clients (eg Pidgin, Miranda, etc) that will allow you to connect to multiple messenger services at once.

The main advantages of using the FastMail Jabber server over other services are:

  • Your login name/email address is the same as your chat name, so there’s only one address people have to use/remember
  • If you’re using a business or family account, it makes it easy for everyone in the family/business to chat to each other without needing to signup for any external service
  • We can interoperate with any other jabber system (eg google talk, livejournal, jabber.org, etc)
  • You can setup the service so that when a chat session is closed (or times out after 5 minutes), the chat log is emailed to you (login to the beta server at http://www.fastmail.fm/beta/ and go to Options -> Chat Settings). This is better than using your messenger clients history feature because the log is stored as an email in our IMAP server, so it’s replicated, backed up, and accessible anywhere

The main limitations of the FastMail jabber server are:

  • Can’t interoperate with proprietary messaging systems
  • Multi-user chat (chatrooms) aren’t available at the moment
  • You have to use your main login email address as the jabber id. You can’t use an alias

For instructions on setting up various clients, see this wiki page: http://wiki.fastmail.fm/index.php?title=ChatService. Note that most instant messaging clients have poor error reporting. If they can’t connect, they often don’t report an error, or report a poor error message. If you can’t seem to connect, please check that you’ve got all the options set correctly, and that you’ve entered your password correctly.

If you experience any problems, please report them to robm@fastmail.fm. Make sure you include as much information as possible, such as your username, operating system, messaging client, error message, etc. Try and include a screen shot of the setup screen and/or any error message.

Dell laptop keyboard slow/freezing in Vista

I got a new laptop a few weeks back, a Dell XPS M1330. It’s a nice laptop; light, a good keyboard and bright screen. I spec’ed it reasonably nicely and it’s got 4G of RAM and a 7200RPM 200G HD.

Despite the high specs, I found that after a week of using it that it started behaving oddly. Basically the keyboard would start being slow and whatever I was typing would start lagging. This was regardless of application (Mail, Notepad, Firefox, etc).

After that it got even worse, with intermittent “pauses” occuring anywhere from 1 second to 10 seconds. The pauses would occur when I was typing or even holding down a key. For instance, hitting the Ctrl key (to do a Ctrl-click on a link in Firefox to open in a new tab) would sometimes cause the machine to “freeze” for 1-10 seconds.

I pulled up a bunch of monitoring tools, but they didn’t show anything interesting. The machine was barely using any CPU. If I left the performance monitor up, normally it updates every second. But if I typed into another window, the performance monitor too would “freeze up” for 1-10 seconds.

So turning to the Internet, I found lots of reports of Vista problems, but nothing that seemed to be specifically like this problem… until I came across this:

http://www.randomsupport.com/rs/blogs/index.php?title=dell_laptop_slow_lagging_delayed_keyboar

The problem description sounded the same. Looking at the update at the end, I pulled up the Dell Mediadirect program, disabled the “Instant Office” feature, rebooted, and suddenly my keyboard is back to actually being useable!

This seems like a serious bug to me. And that post is from September 2007. I can’t believe that every Dell Vista laptop was and still is shipping with this bug?

Update: It seems disabling the “Instant Office” feature wasn’t enough. Over the next day the machine became slow and laggy to keyboard response again. Killing the PCMService.exe process and removing Dell Media Direct does seem to have permanently fixed the problem.

robm@fastmail.fm

Alternate namespace IMAP port (may help Outlook, OL Express, Apple Mail and BIS users)

Background summary: Since we started FastMail, we’ve been using cyrus as our IMAP server. By default, cyrus uses 2 different namespaces for folders: “INBOX” for personal folders, and “user” for shared folders. What this means is that all personal folders are actually a sub-folder of INBOX looking like this:

  • INBOX
    • Drafts
    • Sent Items
    • Trash
    • My Folder

Since cyrus is a well used email server, and most people prefer personal folders being at the same level, most email software includes a “root prefix” option or the like, and setting that to “INBOX” will promote all the sub-folders of INBOX up one level, and display INBOX as Inbox, to create this:

  • Inbox
  • Drafts
  • Sent Items
  • Trash
  • My Folder

The problem is that not all programs handle this as well as they should, some programs not at all, and for some when you do set the root prefix, it “hides” the “user” namespace, so you then can’t use shared folders at all.

Alternate namespace: cyrus does have a mode where you can enable what’s called the “altnamespace” feature. What this does is basically cause cyrus to internally remap folder names to (eg promote sub-folders of INBOX up one level), rather than getting the client to do it.

The problem is this is a server wide setting, and we can’t just change it for everyone in one go, because every existing person that had an IMAP client setup would suddenly start getting errors. (eg their email client would try to select the folder INBOX.Drafts say, and the server would say that that folder doesn’t exist anymore because it’s now called just Drafts). Every existing user would have to remove the root prefix from their client, and then re-download a lot of email in many cases. This would cause massive disruption.

Solution: Well it turns out that while it’s a server wide setting, it’s actually per “service instance”. What this means is that we can actually run two completely separate imap service instances at the same time, and one has regular namespace, and one has the “altnamespace” setting set. To make this accessible, we basically have to put it on a separate server/port.

So what I’ve done now is set this up, and map it to separate port numbers. So if you setup your email client with:

  • Username: yourusername@domain.tld
  • Password: yourpassword
  • Server: mail.messagingengine.com
  • Root prefix: (leave blank)
  • Port: 142 (or for SSL 992)

You’ll get the alternate namespace IMAP instance.

Who is this for?: This is most useful for the following people:

  • Outlook/Outlook Express users with folders shared from another person – If you set the root prefix in Outlook/Outlook express, it will hide the shared folder “user” namespace. With the alternate namespace ports, shared folders will appear under the “user” folder
  • Apple Mail users with folders shared from another person – ditto to above, and additionally, leaving the “root prefix” blank which used to be a solution now causes Apple Mail to warn you every time you start it up. With the alternate namespace ports, and the “root prefix” left blank, this shouldn’t happen
  • Blackberry BIS users – it seems the Blackberry BIS server uses some fairly hardcoded folder paths (eg “Sent Items” and “Trash”) and won’t search for sub-folders of INBOX, so this should work better. To set this up, you need to login to the BIS website, create the FM account and leave your password blank. It should then take you to a more advanced configuration screen where you can set the port to use explicitly.

Thunderbird users don’t need to use this, because Thunderbird seems to be a bit smarter with an INBOX root prefix. It promotes the sub-folders correctly, but still shows the “user” namespace for shared folders as well.

Limitations: One thing the cyrus altnamespace instance doesn’t handle properly is creating sub-folders of Inbox. I’m not entirely sure what will actually happen, but I’d recommend you don’t do it.

If you have any issues, please email me at robm@fastmail.fm

LDAP access to address book

You can now access your FastMail address book via LDAP. Many email programs (eg Outlook, Outlook Express, Thunderbird, etc) support LDAP access for address books.

There are some important caveats with using this:

  1. The address book is read-only via LDAP, so you can’t make changes or add addresses to your address book from your email program
  2. The address book is not cached offline (in theory Thunderbird 2 supports this, but the implementation is currently broken, it should be fixed in Thunderbird 3), so it will only work while you are connected to the Internet

LDAP is most useful for families/businesses that have a large global address book. In these cases, the LDAP address lookup will search the users private address book & and the global address book.

If you understand these limitations, and want to give LDAP a go, here are some quick instructions for setting up LDAP on the most popular email clients:

  • Outlook Express – Go to Tools -> Accounts. Click Add -> Directory Service, then see below
  • Thunderbird 2 – Go to Tools -> Options. Click Composition tab, then Addressing sub-tab, click Edit Directories. Click Add, then see below.
  • Outlook 2007 – Go to Tools -> Account Settings. Click Addressbooks tab. Click New then see below.

Once you follow the above steps, you’ll be asked for some information about the LDAP server. You need to enter the following details:

  • Server/Host name: ldap.messagingengine.com
  • Port: 389 (or 636 for SSL)
  • Login: Required (but must be “plain”, not “SPA”)
  • Username/Bind DN: cn=[your-username]@[your-domain],dc=User
  • Search base/Base DN: dc=AddressBook

Obviously replace [your-username]@[your-domain] with your actual full login name in the above settings (and remove the [ and ] brackets as well, they’re just to make it clearer which bits need some changing), but remember the “cn=” part at the start and the “,dc=User” part on the end.

Here’s some photos for the Outlook Express setup:

And this is for Thunderbird:

To actually do an address book search via LDAP

  • Outlook Express – Go to Tools -> Address Book (or click Address Book on the main toolbar), then Edit -> Find People (or click Find People on the toolbar). Select the LDAP directory from the Look in popup menu. Then use the fields below to search. To automatically search the LDAP address book when composing, make sure that when you setup the LDAP account, you select the Check names against this server when sending email checkbox on the General tab. Note that any local addresses will always be matched first. Only names that can’t be matched in your local address book will use LDAP for the search.
  • Thunderbird 2 – Go to Tools -> Address Book (or click Address Book on the main toolbar), select the LDAP address book from the list at the left. Use the search box at the top right of the window to search. To automatically search the LDAP address book when composing, go to Tools -> Options. Click Composition tab, then Addressing sub-tab. In the Address Autocompletion section, make sure the Directory Server checkbox is checked, and make sure you select the LDAP account you setup above from the popup menu.

If you have any questions, please see our forum or email me at robm@fastmail.fm.

New mail.messagingengine.com SSL certificate

Sometime in the next 24 hours we’ll be changing over the SSL certificate for mail.messagingengine.com to a new one. In theory, users shouldn’t notice any change at all. However there are two changes in the new certificate that might affect some users.

  1. We’re changing our SSL provider from Thawte to Digicert. Some users using older devices may have had to install the Thawte root certificate into their device to be recognised properly. Those devices may also be missing the Digicert root certificate. A copy of the Digicert root certificate can be downloaded from http://www.fastmail.fm/DigiCertCA.crt (It’s actually a chained certificate, and the correct root to use is http://www.fastmail.fm/Entrust.net_Secure_Server_CA.pem). Most devices that don’t recognise the Digicert certificate by default should allow you to install a root certificate from the above URL.
  2. We’re changing from a pure mail.messagingengine.com certificate to a wildcard *.messagingengine.com certificate. Some old devices may not understand wildcard certificates properly. For those devices, we’ve included mail.messagingengine.com as a “server alternate name” in the certificate, which should work.

We’ve checked that compatibility with this new certificate should be good, but as always, there are edge cases and some users may have issues. If you do have any problems, please email me directly at robm@fastmail.fm with details of the device you’re using and the error you’re getting.

The reason we’re changing is that Digicert offer more flexibility with their SSL certificates, such as wildcard certificates with multiple “server alternative name” options.

Update: I rolled out the new certificate, and shortly afterwards had some reports of problems with Eudora/iPhone/Thunderbird/etc. I contacted Digicert support who were very helpful. Turns out I’d forgotten to RTFM fully, and hadn’t included the chained certificate in the PEM file. I’ve now done that, so things should be better for Eudora/iPhone/Thunderbird/etc users that were having problems.

Update: Unfortunately for Eudora users, it seems Eudora does not come with the required root certificate built in. This means Eudora users will still see an error message with the new certificate. Fortunately, it’s easy to fix this, just follow the directions here to add the list of trusted certificates in Eudora.