Christian Mack wrote:
I already tried with "*", no results. It seems "." is still the current wildcard. Like I said, it works on my smaller user-base installation, even in Thunderbird.Am 2013-03-18 07:18, schrieb Euan Thoms:Searches in Thunderbird public address book (A.K.A. Corporate Directory) are not fully working. The search "." is not returning anything, it should return all entries.Did you try with "*" instead? There was a discussion before about valid wildcards in searches, especially the different ones used for LDAP and SQL backends. Consensus was to deprecate the use of "." and support the "*" wildcard on all backends.
I have a large cache already. I can try to increase it further but I doubt it will help. A standard Thunderbird LDAP AB works well and returns results quite fast. I could replace the SOGo public AB with a standard LDAP one, but it is slightly messy and requires extra setup per client Thunderbird installation.I have 2 installations of SOGo, configured in the same way. One with small number of users, one with many (300+). In Thunderbird public address book (populated via SOGoUserSources) some searches fail when they do not in the webmail interface. Also, the "." search in Thunderbird does not return any results, but it does in the webmail. The installation with small number of users is fine in Thunderbird and webmail. I have added similar entries in LDAP and a search will match in the smaller user-base but not in the larger user-base.You could try to speed things up, by increasing the openLDAP cache. Make it big enough to get the whole database into RAM.
I have no setting for SOGoLDAPQueryLimit. I can see all my entries in webmail, since it effects webmail as well, surely it can't be this.Agreed.Details: Also, I noticed that in the Thunderbird public address book , when I type one character, e.g "a", it shows all entries starting with a (perhaps 30 or so). When I type "b", like-wise. But when I type "f" or "t", I get no results. There should be more results for "f" and "t" than the other letters, this should serve as a a clue. Another example; I have an entry with display name (cn) "Fast Flow China - Calculation Centre" and Surname (sn) "Forwarding Account" and email (mail) "[email protected]". The search text "ffc"... will return a result. The search "Fast" and "Fast Flow" will not, but "Fast Flow China" will. The search "Forwarding Account" will not return any results. Again, all the searches work perfectly in webmail. Conclussion: At first I thought it may be a number of results limit somewhere. But I get 68 results for "c" and I should get 56 results for "Fast Flow". What I now think, is that the failed searches are those that take longer to process on the ldap server. Either it times out or is not returned in time for Thunderbirds' quick search filter. Anyone else experienced this?We also sometimes see this behaviour. We have more than 14,000 accounts with a limit of 25 hits per LDAP search. It also depends on typing speed. If you type fast and wait afterwards, then the search is mostly done correct. But if you type slow, then you often don't get any results. I assume that by typing slow you always trigger a new automatic search with each character. So this will rise the burden on the LDAP search connection. Which leads me to the same conclusion you got. Thunderbird is using a too short timeout on searches.
My issue has nothing to do with auto-complete. This is behaviour in the address book search itself, however the results apply also to auto-complete. I have increased the timeout (delay) for sogo-connector auto-complete, it doesn't make any difference.
Kind regards, Christian Mack
Thanks for your help Christian. Anyone else have any suggestions? -- [email protected] https://inverse.ca/sogo/lists
<<attachment: euan_thoms.vcf>>
