Comment 31 for bug 119358

(In reply to comment #21)
> For the next release, we should consider this. Ideally, we'd do an
> auto-detection of whether SSL or TLS works, and auto-configure.

I found this filed as bug 394487 along with a suggestion for a possible scan order. Judging from the increasing number of "cannot connect" posts at MZ forums, and the fact that more and more providers are requiring encryption these days, having more options in the initial account setup is crucial. First-time users may be frustrated twice by first not finding any option in the account wizard to specify the port and encryption method obtained from their providers, then again when the first connection fails. Taking the guesswork out by a scanning mechanism would certainly be the best solution, I agree.

A few more thoughts:
 - Include SMTP in this bug, as providers are more likely to require encryption also for outgoing e-mails these days.
 - Offer port options rather than just encryption, e.g., TLS may be on either port 25 or 587; or, add the port to the attachment 186131 layout.

Possible port options to select in the account wizard:
 - POP3: 110 (implies try TLS), 995 (use SSL)
 - IMAP: 143 (implies try TLS), 993 (use SSL)
 - SMTP: 25 (implies try TLS), 465 (use SSL), 587 (try TLS)

Note that none of the options has "no encryption" by default, assuming the "try TLS" option can be used if TLS is not supported by the server.