![Thunderbird logo](https://assets-prod.sumo.prod.webservices.mozgcp.net/media/uploads/products/2024-02-12-07-36-53-599028_1.png)
when composing new mail autocomplete not working properly with ldap (while in adress book search works perfectly)
I am using Thunderbird 38.5.1 Greek edition. I have set up Ldap connection for the address book and within address book everything works fine (search / find etc).
However, when I try to compose a new mail - the auto-complete feature of the "To" field either doesn't work at all or brings limited number of names from the Ldap server - without bringing the name that I am looking for.
I cannot figure out what is causing this behavior.
My Actions:
1. I open up the compose window and type into "To" field letter "e"
2. "e" becomes red
3. I leave it for a while (2 min) to be sure that the slow response is not the problem here
4. Nothing happens, "e" remains red
5. I start deleting the letter "e" and then typing it in again.
6. At some point (not always, only if lucky) some names appear in the auto-complete (but not every email that contains "e" in it)
7. At this point, I give up ;-)
Also, even if I find the correct address in the address book - when transferred to "compose" window, the address becomes red
(as if not found).
P.S. The only address book enabled is - Ldap - everything else is unchecked.
Modificado por plirkee a
Solução escolhida
Ok I will reply to this one myself ;-)
The problem was solved when I changed Ldap port from 389 (default) to 3268 which is apparently port for searching in Global Catalog.
Other settings in Ldap were:
Base DN: dc=organization, dc=com Bind DN: myuser@organization.com filter : (objectclass=*)
Also this solved LDAP Replication failure message.
Ler esta resposta no contexto 👍 1Todas as respostas (1)
Solução escolhida
Ok I will reply to this one myself ;-)
The problem was solved when I changed Ldap port from 389 (default) to 3268 which is apparently port for searching in Global Catalog.
Other settings in Ldap were:
Base DN: dc=organization, dc=com Bind DN: myuser@organization.com filter : (objectclass=*)
Also this solved LDAP Replication failure message.