You could argue that GMail has a higher customization potential given the fact that you can muck around with the document client-side (though Thunderbird extensions are similar, and if you really go down that road: I can also change the source code of KMail and recompile it), but we're talking in-app options here.
And so I find the notion that "GMail has impressive configurability because it has the options described in the article" amusing. Somehow the world has forgotten just how sophisticated an experience a regular old desktop app running in the context of a regular old desktop environment can be.
I'd also argue that regular old desktop toolkits and libraries still require a lot less investment of effort to achieve such levels of sophistication than the web development environment does at the moment. Like I said, thought-provoking.
Gmail's IMAP works, though it's had a number of minor-but-irritating bugs for years (these bugs even affect the official applications too). I wish they'd fix them - I get that it's not in their interest to support nonstandard clients for which they receive no ad revenue, but that's no excuse here, because they still cause some of the same problems on the Android and Blackberry apps.
This article, dated February 2008 (four years ago!) is just as relevant today as it was then. The duplication of messages with broken synchronization is what bothers me the most, as I use offlineimap to handle my mail: http://weblog.timaltman.com/archive/2008/02/24/gmails-buggy-...