272715 - LDAP settings for multiple accounts get messed up

Status: RESOLVED EXPIRED

(Thunderbird :: Account Manager, defect)

Description

[Tim K]

User-Agent:       Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322)
Build Identifier: version 0.9

I have 4 IMAP servers configured in TB, 2 of them require an LDAP server 
setting, the other 2 don't.

In the Account Settings window if I click on Composition & Addressing for an 
IMAP server that does NOT use an LDAP server (for which the setting is "Use my 
global LDAP server preferences for this account") and then click on the 
Composition & Addressing for one of the servers configured to use a specific 
IMAP server, the specific IMAP server setting is lost. The setting changes on 
its own from the specific LDAP server to the gloabl setting.

Reproducible: Always
Steps to Reproduce:
1. Configure 4 IMAP servers, 2 with a specific LDAP server, 2 with the global 
LDAP settings.
2. Go to Account Settings for the IMAP servers configured with specific LDAP 
servers and verify they stick
3. Now click on the Composition & Addressing for one of the IMAP servers that 
uses the global LDAP settings
4. Now go back to the Composition & Addressing for the one of the IMAP servers 
that uses a specific LDAP setting
5. The specific LDAP settings will be reverted to the gloabl settings for all 
accounts

Actual Results:  
The specific LDAP settings will be reverted to the gloabl settings for all 
accounts

Expected Results:  
The settings for each account should be sticky, they should not changed just 
by viewing the settings of another account

Comment 1

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 2

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.