Re: [imap5] Feature set? - was Re: Designing a new replacement protocol for IMAP

[Dave Cridland <[e-mail]>]

On Thu Feb 16 09:20:44 2012, Adrien de Croy wrote:
> SMTP: specification of server, choice of authentication method,  
> choice of security (SSL vs STARTTLS vs none), username and password.
> IMAP: specification of server, choice of authentication method,  
> choice of security (SSL vs STARTTLS vs none), username and password.
> LDAP: specification of server(s), choice of authentication method,  
> choice of security (SSL vs STARTTLS vs none), username and password.

Well, of course, I'd argue that you could use a combination of SRV,  
common options, discovery, and ACAP to fix all that.

The problem with Thunderbird isn't that it has all these options,  
it's that it requires the user to enter them, and fails to do  
discovery properly - Tony Finch wrote a particularly good blog post  
on why it's so awful several years ago, and provided solutions, too.

Interestingly, XMPP has generally gone the discovery route, and the  
result is that you only enter a jid and a password.

For Polymer, you enter a username, ACAP server, and password - ACAP  
doesn't have the SRV option, and maybe I should just add that in -  
not that anyone but me cares anymore.

Having written multiprotocol clients, I just don't think they're as  
hard as people make them out to be.

Dave.
-- 
Dave Cridland - mailto:[e-mail] - xmpp:[e-mail]
  - acap://acap.dave.cridland.net/byowner/user/dwd/bookmarks/
  - http://dave.cridland.net/
Infotrope Polymer - ACAP, IMAP, ESMTP, and Lemonade