Interview with Colin Walters about the online desktop [LWN.net]

Interview with Colin Walters about the online desktop

Posted Oct 2, 2007 8:13 UTC (Tue) by nim-nim (subscriber, #34454)
In reply to: Interview with Colin Walters about the online desktop by alankila
Parent article: Interview with Colin Walters about the online desktop

> I find it startling to consider that people would rather use the web browser
> than some IMAP client for their email.

For every entity that offers secure IMAP+TLS access, you have 30 offering some kind of webmail. IMAP has not lost on the client side but on the server-side - most mail provides just jumped from pop to webmail without even trialing IMAP.

Mail providers just live webmail, they can stuff it with adds, they can integrate spam filtering easily, and they don't need to explain users how to configure all the different mail clients out there (this bit is an indictment of mail rich client config UIs, and of the de-emphasing of IMAP in big enterprise clients like outlook and notes)

to post comments

IMAP's real problem was scale and timing

Posted Oct 2, 2007 11:15 UTC (Tue) by philipstorry (subscriber, #45926) [Link] (1 responses)

The problem IMAP had initially was scale.

POP3 is really simple as a protocol, and scales well. But more importantly, POP3 tends to assume (in most client defaults) that mail will not remain on the server. IMAP doesn't, and therefore increases storage use and associated costs.

Back then storage space on large mail servers was a serious issue. The machines weren't all that capable, and solutions like SANs were exotic and expensive.

By the time the machines became mature enough to handle IMAP accounts, the market wanted webmail rather than IMAP, as it doesn't tie you to a machine. (Although it does tie you to a browser.)

Ironically, from what I've seen many of the webmail implementations out there are actually based on having data served from an IMAP server, albeit one that's only accessible on the loopback address or behind a firewall you can't access...

I agree with your client config point 100% - IMAP is not thought of as a viable option for most enterprises though, so it's only to be expected. To be honest, I think it was only added in the first place for the education sector, as some large universities used it.

I couldn't figure out why someone didn't just pick this market up buy the scruff of its neck and provide a simple {XML|CSV} file format that was open and freely licensed, and could be read by your mail client to configure itself for you. Then configuring a mail client could literally be as simple as "click on this link, then type your username and password"...

But I still don't think that would have changed things much... Webmail, once used, has a certain accessibility that's far more attractive to light users than a more restrictive rich client will ever be...

IMAP's real problem was scale and timing

Posted Oct 2, 2007 19:09 UTC (Tue) by bronson (subscriber, #4806) [Link]

The biggest problem is the IMAP protocol. When have you ever used an IMAP client that just worked 100%? Never! Every IMAP client I've ever seen is a creeping nightmare for the user to configure (SSL? TLS? Kerb? NTLM? GSSAPI?). Oh, you can get it to barely work, but it will never work right. There will always be oddities like all your folders appearing as subfolders of your inbox, or separator issues, or folders randomly disappearing (subscription issues), etc. IMAP is a horribly overcomplex protocol for what it does, and effectively makes it impossible to write a sold client.

Another problem is synchronicity. All IMAP clients that I've seen seem to think that they have exclusive access to the mailbox. When I read a message on my phone, I want it instantly marked as read on my desktop. When I move a message from one folder to another, I want to see that change everywhere, instantly. Today, you need to quit & restart each client for them to update their status. That's a showstopper.

Another problem is filtering. This is something that MUST be done server-side. Client-side filtering is simply too big a maintenance headache for anybody uses multiple clients to access the same mailbox. SIEVE is awful. I'm not sure what the guys who wrote it were thinking... Probably something along the lines of, "if we make it take 5 man-years to write a working Sieve GUI, we're assured luuuucrative consulting contracts for the rest of our lives. hahahaha!" Sieve is actually worse than nothing because it's now an obstacle to developing a good, simple, working solution.

What about standardizing tagging and labeling? And junk mail handling?

I guess that will do for now. I could keep going if prompted. :)

Today, the problem is poorly designed protocols. The webmail guys don't have to fight IMAP and Sieve, so they don't need to worry about broken clients/servers, so they can develop their software 10X faster than the poor desktop guys.

It pains me to watch all this vital information slowly moving into opaque silos. But, at this point, I don't know what can be done about it.