New account wizard doesn't update SMTP port automatically



9 years ago
3 years ago


(Reporter: juha.karonen, Unassigned)


Firefox Tracking Flags

(Not tracked)




9 years ago
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv: Gecko/2009102815 Ubuntu/9.04 (jaunty) Firefox/3.0.15 FirePHP/0.3
Build Identifier: Thunderbird 3 beta 4

Changing encryption from none to SSL doesn't update the port from 25 to 465 in new account-wizard in SMTP settings. 
In the preferences it works afterwards. 

Reproducible: Always

Steps to Reproduce:
1. create new mail account
2. add data
3. change SMTP encrytion from none to ssl
Actual Results:  
The port remains to be 25

Expected Results:  
The port is updated to 465
At what moment do you try to change the port, before  pushing the create account button ?

Comment 2

9 years ago
Before pushing the create account button. 
This might not be a bug, but the user experience is inconsistent in the wizard and in the account settings (where the port changes automatically when the SSL is selected). For non-technical user it is not an option to figure out the correct port and type it in manually, selecting the SSL hould be enough... IMHO.
UI as changed. you can't do that anymore in RC1 - rc1 should be available in a  few hours. If your issue is still present in RC1 please provide a screenshot.
I Think this bug is Invalid: test in TB 3.0rc2 it seems work fine because when you click on "Edit" button on "New Account Setup" and fill the new preferences, when click "Re-test configuration" adjust the values to right place.

You agree Juha?

Comment 5

9 years ago
Still seeing this behaviour in TB 3.1.2.

I don't think it should wait until you click re-test configuration.  Particularly as you can skip this stage, and just create the account directly.  The port should update immediately as you change either the drop down selection.  Also, should apply not just to the SMTP server port, but also the POP/IMAP port.  I just ended up configuring a plaintext-auth POP server on port 993 by not noticing the port wasn't being selected automatically.
Ever confirmed: true


5 years ago
See Also: → bug 939537
You need to log in before you can comment on or make changes to this bug.