sure, anything that can be auto discovered is great.
But SRV has issues, not every corporate runs their own DNS (at least not
for external).
ACAP is great too, but it's another port and set of creds. And the
tie-in between ACAP and other services is probably manual on the
back-end right?
Xtra is NZ's biggest ISP. It blocks port 25. So when I take my laptop
home I need to reconfigure it. At least I know how to do that.
We're techies here, we forget how lost and confused the punters get.
Adrien
On 16/02/2012 10:57 p.m., Dave Cridland wrote:
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.
--
Adrien de Croy - WinGate Proxy Server - http://www.wingate.com
_______________________________________________
imap5 mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/imap5
