On 3/16/2004 6:33 PM, Keith Moore wrote:
Are clients expected to support both IMAP and POP then?
| 4.1. Retrieval Server Lookups
| a messaging client which
| only supports one or the other service SHOULD only issue lookups
| for the retrieval service that the client supports, and SHOULD NOT
| issue lookups for services that are not supported by the messaging
| client itself.
What about
clients for which POP support is good but for which IMAP support sucks?
That's part of the 10% where SRV would not work reliably. Of course, none
of the other configuration services would guess that right, either.
Assuming you really meant "former", what's a reasonable default for
"leave mail on server"?
What's the default for your favorite client? Why would it be different?
Well, there are issues like: does the user really want his password
transmitted in cleartext?
TLS support (and SASL mechanisms) can be discovered with a probe. The
protocol specs (mostly) require TLS and there's no reason to restate what
the canonical specs already say. Obviously, clients should see what
capabilities are offered and choose accordingly, and that is specifically
allowed for (it's not demanded for other reasons, so the strongest point
was to say "you may discover stuff").
--
Eric A. Hall http://www.ehsco.com/
Internet Core Protocols http://www.oreilly.com/catalog/coreprot/