When creating a new IMAPS account (IMAP over SSL), the New Mail Account 'wizard' does not allow the user to select IMAPS, only IMAP. This account will then failafter it has been created with the Account Setup (unless both protocols are available), and the user then has to go to the Mail Settings and set this. Perhaps this should be permitted in the initial mail account creation wizard (ie, options are POP, IMAP, IMAPS).

Actually, this is major. For many servers when you end up creating a simple imap (not imaps) account you end up in an infinite loop of the server denying authorization and us popping up alerts about it. The only way out is to kill the browser. Restart, start mailcompose (not mailnews, since that will make us loop again), and edit the server settings. Not very intuituive....

*** Bug 87989 has been marked as a duplicate of this bug. ***

*** Bug 160223 has been marked as a duplicate of this bug. ***

Adding POPS to summary

*** Bug 179362 has been marked as a duplicate of this bug. ***

Over to account manager, updating to critical, since infinite loops with a modal window mean dataloss.

mass re-assign.

*** Bug 205162 has been marked as a duplicate of this bug. ***

Ok, taking this a merging it with bug 238583

*** Bug 252651 has been marked as a duplicate of this bug. ***

i think i was added to this bug as a result of my activity on bug 221030. along with the "secure server" checkbox, should there be a "port" checkbox? the behavior would be to toggle port value back and forth between the standard encrypted and unencrypted ports for the chosen protocol, unless the user has entered a nonstandard port value: set default protocol, "secure connection" setting set port to default port for the above combination on "secure" checkbox change, or protocol change: if current port value is "standard" port for current protocol/secure setting: change port value to standard port for the new protocol/secure setting. otherwise: do nothing, since the user has explicitly changed the port value to something else.

We should also allow specification of TLS in the account wizard.

This is even more major than you think. If you force people to incorrectly set up an account without SSL/TLS and wrong port numbers, then you have opened a security hole whereby the user's username and password can be transmitted in plain text over the internet. Strictly speaking, the user's username and password are then compromised and should be changed ASAP. Ideally speaking, you should assume that TLS is required and enable it, and require that it be disabled for insecure use. Of course, this has usability implications...

severity of blocking bug 238583 (enh) and bug 41929 (normal) are not consistent with severity of this "critical" bug. Both should be bumped, no?

see also Thunderbird Bug 221030

I would support comment 11 to select port options rather than just the encryption type. For example, both unencrytped and TLS may be required on either port 25 or 587 for SMTP, thus encryption alone would be ambiguous. Also, SMTP should be added to the list of protocols in the subject for this bug. Suggested port options for the account wizard (type-in or radio buttons): - 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. The variety of port and encryption settings asked for by the providers is becoming an increasing problem for the initial setup and should be covered by the account wizard.

I'd like to see this in SeaMonkey as well. Thunderbird allows this option.