309938 - Newly added SMTP account removed after restarting Thunderbird

Status: RESOLVED WORKSFORME

(Thunderbird :: Account Manager, defect)

Description

[rasbelin]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.7.12) Gecko/20050919 Firefox/1.0.7
Build Identifier: 1.0.6 (20050716)

With no SMTP accounts specified, any new SMTP account added gets removed from
Thunderbird upon closing/restarting the program. The account still does appear
in the configuration file, but the interface shows it as reset to using the
default account (Always use default server). This happens to me when trying to
add any new SMTP account under Advanced Outgoing Server (SMTP) Settings. Doesn't
matter what the server address, port or SSL/TLS setting is. File access rights
are correct as client is capable of writing into the setting file, so seems to
be a yet another issue with Thunderbird not reading the configuration data correct.

Reproducible: Always

Steps to Reproduce:
1. Open the Advanced Outgoing Server (SMTP) Settings dialog and click Add.
Specify some new SMTP server.
2. Now make any of your newly added POP/IMAP accounts use it for outgoing e-mail
by choosing it in the SMTP tab in Advanced Account Settings.
3. Close the client.
4. Open prefs.js in an editor. Notice that the account is there.
5. Start Thunderbird. Review the list of SMTP accounts. The SMTP account is now
gone, but still appears in the config file, if you review it now. If you check
the POP/IMAP account, you notice it has been reset to default.



Profile is not located in the default directory, but this shouldn't affect this,
as Thunderbird is capable of adding new POP/IMAP accounts just fine and this has
worked before for me.

Comment 1

[Mike Cowperthwaite]

I could not reproduce this bug with TB 1.0.6, Win2K.  Note that the SMTP UI 
has been drastically improved in 1.5.  I'm going to close this bug as WFM, 
but if you can reproduce with 1.5, feel free to reopen.

Comment 2

[Mike Cowperthwaite]

Forgot to mention: it's possible this is the same as bug 314146.