Closed Bug 580270 Opened 10 years ago Closed 10 years ago
won't save authentication method "normal password" as preference
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:184.108.40.206) Gecko/20100625 Firefox/3.6.6 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:220.127.116.11) Gecko/20100608 Thunderbird/3.1 After restarting thunderbird my preference of the authentication method gets lost and is set back to "Any secure method", even though before restarting the program, it remembers the set preference. Happens only with the selection "SSL/TLS" and "normal password". I'm using two mail-servers and this problem occurs only with the one referred to as mail.server.server1 I looked up prefs.js to find that thunderbird won't save the authMethod variable when its value is 3 (="normal password"). After editing the file manually everything works fine. Reproducible: Always Steps to Reproduce: 1. select "ssl/tls" for the mailserver of incoming mails in your prefs 2. select authentication method "password, normal" 3. restart program Actual Results: the selected preference won't be saved; instead the preference turns to "Any secure method"
See http://forums.mozillazine.org/viewtopic.php?f=39&t=1955465&start=0 (which also has a link to a similar thread on the GetSatisfaction support forum) They worked around the problem (in Thunderbid 3.1 and 3.1.1) by setting useSecAuth false.
I see this too after updating from T'bird 3.0.6 to 3.1.1, en-US build on mac 10.6. On an IMAP account I have Connection security: SSL/TLS Authentication method: Any secure method (deprecated) and get an alert on connection The IMAP server <blah> does not support the selected authentication method. Please change the 'Authentication method' in the 'Account Settings | Server settings' If I go there and set it to 'Normal password' then I can login, but that change is lost after restarting Thunderbird. Peeving after the 3rd time. How do I request blocking for this to get fixed in 3.1.x ?
Status: UNCONFIRMED → NEW
Ever confirmed: true
Version: unspecified → 3.1
Mark, we'll call me CC-ing you a blocking request for 3.1.x since it seems the flag permissions are set wrong (neither myself nor nthomas can REQUEST blocking for 3.1)
(In reply to comment #3) > Mark, we'll call me CC-ing you a blocking request for 3.1.x since it seems the > flag permissions are set wrong (neither myself nor nthomas can REQUEST blocking > for 3.1) It ain't wrong just follow our policy. You both have access now.
Is there anything on the error console when you try to change the setting?
No, but perhaps the error would occur on shutdown. Is there an argument I can give at startup time to dump error console output to the terminal ?
I just tried reproducing this but couldn't. What I think may be useful to get is a copy of the mail.server.server<n>.* prefs where n is the server relating to the one you're having trouble with.
(In reply to comment #6) > No, but perhaps the error would occur on shutdown. Is there an argument I can > give at startup time to dump error console output to the terminal ? -console does that normally
I left out mail.server.server4.directory, not clear what that pref is. Trying -console: $ /Applications/Thunderbird.app/Contents/MacOS/thunderbird-bin -console Warning: unrecognized command line flag -console
Setting Connection Security: None Authentication method: Password, transmittend insecurely and restarting t'bird gives me Connection Secutiry: None Authentication method: Any secure method (deprecated) I can't reproduce with a new profile either. Data migration routing gone wrong ? BTW, the Mozilla ISP settings sets SSL/TLS & Encrypted Password when the server needs Normal password.
There's definitely something wrong here. If I take my current profile, and set mail.server.default.authMethod to 8, then I see the authentication method as "Any secure method (deprecated)". However, if I set mail.server.default.authMethod back to 3 and have mail.server.server7.authMethod set to 8, then that server shows "Normal Password". As the specific server instance is meant to override the default one, there's something not right here.
(In reply to comment #11) > If I take my current profile, and set mail.server.default.authMethod to 8, then > I see the authentication method as "Any secure method (deprecated)". > > However, if I set mail.server.default.authMethod back to 3 and have > mail.server.server7.authMethod set to 8, then that server shows "Normal > Password". Unfortunately about:config had decided to set my server7.authMethod to a string value rather than integer, which is why this wasn't doing the expected.
Ok, I can reproduce this now, STR: 1) Simulate a profile from Thunderbird 2 or 3: have mail.server.server<n>.useSecAuth set to true. Ensure mail.server.server<n>.auth_login unset. 2) Run Thunderbird 3.1 (or trunk), mail.server.server<n>.authMethod gets set to 8 by mailnewsMigrator.js i.e. "Any secure method (deprecated)". 3) Go into account settings and select "Normal password" for the authentication method. => At this stage mail.server.server<n>.authMethod gets *cleared* because it would be set to 3 but that's the value of mail.server.default.authMethod (hence it gets cleared). 4) Restart Thunderbird. => mailnewsMigrator.js sees authMethod not being set to a user value, and therefore re-initialises it to 8.
Oh, dang. Taking.
Assignee: nobody → ben.bucksch
Ben, would you be able to have a patch of this by/on Monday? I'd like it in the respin for 3.1.2. If you can't I may be able to work on it, but would like to know roughly how you were thinking of fixing it.
mark, my plan was to introduce a new pref "something.migrated" which is set to true after the migration code set the autoMethod pref. It would be checked only if we found useSecAuth and friends and directly before writing the migrated authMethod, so that we don't need it in new profiles created in 3.1, only in migrated profiles.
Based on Ben's suggestion this implements the migrated option per server that requires it. I've gone for a migrated pref that has integer values, I'm not sure if we'd ever use them, but we at least can re-use it if we deem necessary. Asking review from David, as I'd like to get this in asap to start 3.1.2, but also asking feedback from Ben to get his thoughts.
Comment on attachment 462173 [details] [diff] [review] Fix and unit test Thanks, Mark, for the patch. Sorry for not providing it myself fast enough - it would have been my duty. Patch is almost exactly what I had in mind, yes. r=BenB. Thanks!
Attachment #462173 - Flags: feedback?(ben.bucksch) → feedback+
Comment on attachment 462173 [details] [diff] [review] Fix and unit test a=Standard8 for 3.1.2, as this is low risk and has good unit tests.
Attachment #462173 - Flags: approval-thunderbird3.1.2+
Checked in on trunk and branches for 3.1.2: http://hg.mozilla.org/comm-central/rev/654926c4dc9c http://hg.mozilla.org/releases/comm-1.9.2/rev/f928d045509d http://hg.mozilla.org/releases/comm-1.9.2/rev/33cfe20ec166
I just updated to 3.1.2 and on already migrated profile I find that changing Authentication method from 'Any secure method (deprecated)' to 'Normal' still doesn't stick on restart. Is that expected ?
You need to log in before you can comment on or make changes to this bug.