531561 - manual edit and then re-test of connection settings defaults to wrong server type

Status: RESOLVED INVALID

(Thunderbird :: Account Manager, defect)

Description

[Jon Grossart]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.5) Gecko/20091102 Firefox/3.5.5 (.NET CLR 3.5.30729)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.5) Gecko/20091121 Thunderbird/3.0

When I was creating a new mail account in TB3.0 RC1, there was a problem with the account settings.  I wanted to play with manually editing the settings, but when I would retest the potential new configuration, it wouldn't start testing with the options I had picked.  Specifically, it would revert back to IMAP from the correctly discovered POP.

Also, comcast.net settings were discovered as SMARTTLS, but this option doesn't work correctly.  There needs to be no encryption on the POP side.

Reproducible: Always

Steps to Reproduce:
1. create a new account
2. enter account information (I was using a comcast.net account)
3. after settings are determined, click on "edit" settings
4. change nothing
5. click on "re-test configuration"
Actual Results:  
Settings revert to IMAP server with port 143

Expected Results:  
settings should stay at the options I've manually configured.

Comment 1

[Jon Grossart]

the account that you are looking to setup is a POP account in this case.  It is correctly determined as a POP account on the first pass.

Comment 2

[Nicki Messerschmidt]

I can confirm this bug. On the first test TB checks for the settings in the specified way and grabs my placed autoconfig file from the webserver.
Due to bug 564043 I cannot ask the user for the username during autoconfig and after manually editing the user cannot just click on "create account".
When clicking "retest configuration" the incoming server setting all get messed up. Hostname, port and connection security get new values.

Comment 3

[Christian Lerrahn]

I can also confirm this problem. However, to me this seems rather erratic behaviour. Sometimes, the re-testing will lead to wrong settings (wrong host name or port), even services that aren't available at all or host names that do not exist. Sometimes, the settings remain as autodetected via the autoconfig XML file on the server.

Comment 4

[Thomas D. (:thomas8)]

Jon, thank you for your time to report this bug.

This bug is reported against an old version of TB.
Good news: Automatic Account Wizard has been completely reprogrammed, so a lot of bugs have been fixed and the UI has been improved.
Please upgrade to the newest version of TB.
For any remaining problems, please file new bugs with new STR against the current versions.

Due to the new account wizard, this bug no longer applies.
In lack of a better resolution -> Invalid.