312115 - global ldap server preference is not taken into account when typing email addresses in a new mail. you must use different ldap server setting

Status: RESOLVED WORKSFORME

(Thunderbird :: Preferences, defect)

Description

[boxpower_x]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b5) Gecko/20051006 Firefox/1.4.1
Build Identifier: version 1.5 Beta 2 (20051006)

If you set a ldap server in addressing in the global options, it does not get
used if you compose a new message and type an email address in the corresponding
field.

But if you choose "Use a different LDAP server" in the Composition and Adressing
option of the account, and then set it to the LDAP server in question, it
queries correctly the LDAP server when entering adresses in a new blank mail.

Reproducible: Always

Steps to Reproduce:
1. Set a new LDAP server in global preferences to be queried
2. Compose a new message
3. Type a name

Actual Results:  
No results are returned, the name stays red

Expected Results:  
The LDAP server should be queried and you should see the result of the query in
a list box under the address bar.

If you change the Composition and Addressing preferences of this particular
account, then it works properly.

Comment 1

[Adam Guthrie]

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20051012
Firefox/1.6a1 ID:2005101212

So I assume this bug persists even if you restart Thunderbird?

Comment 2

[Adam Guthrie]

I'm willing to bet that you're seeing bug 312180. Is there anything in the
JavaScript console? Tools > JavaScript console

Comment 3

[boxpower_x]

Yes, the bug persists after a restart of Thunderbird. Also, I used the
JavaScript console as described and no errors are reported, nor warning,
generated from the setting of both global preferences and account settings when
modifying those settings.

So, to restate the problem, if you set the LDAP server in the account settings
to the one you configured in the global preference (or any other) it gets used
properly. It's just that if your global preference are set to use a LDAP server
and that your account preference are set to use the global preference, it does
not work as previous version of Thunderbird.

This is using Thunderbird 1.5b2 on both a Windows and a Mac computer, and it is
highly reproducible.

Comment 4

[Brett Leber]

(In reply to comment #3)
> Yes, the bug persists after a restart of Thunderbird. Also, I used the
> JavaScript console as described and no errors are reported, nor warning,
> generated from the setting of both global preferences and account settings when
> modifying those settings.
> 
> So, to restate the problem, if you set the LDAP server in the account settings
> to the one you configured in the global preference (or any other) it gets used
> properly. It's just that if your global preference are set to use a LDAP server
> and that your account preference are set to use the global preference, it does
> not work as previous version of Thunderbird.
> 
> This is using Thunderbird 1.5b2 on both a Windows and a Mac computer, and it is
> highly reproducible.

Comment 5

[boxpower_x]

As of RC1, this does not apply anymore...

I redownloaded a beta2 released, and was able to reproduce, but between the two releases, it was solved somehow.

Comment 6

[Daniel Veditz [:dveditz]]

I'm seeing this too (build 20051206), and over the years other folks have filed similar bugs. The currently active one appears to be bug 317566