323655 - Autocompletion does not work when account is set to use global LDAP preferences

Status: RESOLVED DUPLICATE of bug 317566

(Thunderbird :: Preferences, defect)

Description

[Dana Kashubeck]

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8) Gecko/20051111 Firefox/1.5
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8) Gecko/20051111 Firefox/1.5

AutoComplete does not work if I have the account set to use my global LDAP preferences. If I set the account to use a different server, but choose the same server in the pop-up list, AutoComplete works.

Reproducible: Always

Steps to Reproduce:
1. Set up LDAP server via Preferences -> Composition -> Addressing tab -> Edit Directories...
2. Check "Directory Server" under "Address Autocompletion" and choose the LDAP server
3. Verify that the settings work by performing a search via the Address Book
4. Set the account to "Use my global LDAP server preferences for this account" via Tools -> Account Settings -> Composition & Addressing
5. Open a new compose window and start typing an address.  The address is not completed and the text turns red
6. Set the account to "Use a different LDAP server" and choose THE SAME LDAP SERVER from the pop-up menu
7. Open a new compose window and start typing an address.  The address is completed as expected.

Actual Results:  
When the account is set to "Use my global LDAP server preferences" autocompletion does not work, even though searching via the Address Book does.  When the account is set to "Use a different LDAP server" and the same server is chosen, autocompletion does work.

Expected Results:  
I would expect that the autocompletion would work when the account is set to use the global LDAP settings.

Comment 1

[bigsmoke]

I can confirm this bug. The same is happening to me.

Comment 2

[Steve-o]

This appears a new regression in version 1.5 (20051201), I see the exact same problems with the Windows release, 1.0.7 worked fine.

Comment 3

[James Andrewartha]

ldap_2.autoComplete.directoryServer is not being set when the global LDAP server for autocompletion is selected, while mail.identity.id1.directoryServer is being set properly by the account specific UI.

Comment 4

[Richard GABRIEL]

I can confirm this bug with Thunderbird 1.5.0.8 on Windows XP/SP2.
It's probably not a MacOS - only issue...

Comment 5

[Chris Hiestand]

The bug also reproduces with Thunderbird 1.5.0.9 in Linux.

Comment 6

[Orion Poplawski]

Confirmed with Thunderbird 1.5.0.10 on Linux.

Comment 7

[Laurent Bauvens]

> When the account is set to "Use a different LDAP server" and the same server is
> chosen, autocompletion does work.

It works the same way when you use autoconfig (MCD) to configure ldap directories.
Users must force ldap directory activation from the UI while configuration is OK.

--> Corporate TB 1.5.0.2 packaged with autoconfig

(nb: same issue with antispam function)

Comment 9

[Aaron Lawrence]

Can anyone confirm this is still present in TB2.0? If so I will confirm it. I think it might have been fixed.

Comment 10

[Orion Poplawski]

This appears to be working for me on TB 2.0.0.12 on Fedora 8.

Comment 11

[Mark Banner (:standard8)]

Duplicate of bug 317566 which was fixed for TB 2.0