Committed, thanks.
That's the only email address I see anywhere in Turba's source.

Here you are. BTW, can you please change my e-mail address in the 
documentation to flgoms (at) uol (dot) com (dot) br   ? It's my 
personal e-mail.

That sounds good. But please make a patch against current CVS HEAD, 
because I already committed most of your original patch.

Yes, it was intended because I'm sendind $strict['email'], not 
$strict['mail']. As far as I could understand that hash key should not 
be mapped/translated. I fear it won't work if that key get translated. 
Unless I send 'mail' instead of 'email' in api.php:1207 wich will only 
work with ldap since the others backends have different key mapping.

To solve that I can translate that key before send it to makeSearch():

$strict_fields[$this->map[$strict_field]] = true;

Then, that key will be translated again in makeSearch(). I attached a 
new version of the patch with that change.

What do you suggest?

Was the change to makeSearch() intended? I left it out because it 
breaks any other search and committed the rest. Let me know if 
everything works fine now.

Hi Jan,



   I just added a new patch (new_kronolith_turba.patch), it is updated 
for Kronolith RC3 and Turba RC2.

   And I made the changes you suggested. Please check them and tell me 
if they are ok.

   That patch was only tested with LDAP backend.



   Thank you.

And a suggestion: As getField() allows searching for email address 
only anyway, it doesn't make much sense to specify the fields that 
need to be strict in the parameters. The parameter should be a boolean 
instead and getField() should pass 'email' as a hardcoded strict field 
then.

Sorry, I missed this when looking at the patch the first time, but the 
patch must be against HEAD or at least Kronolith 2.1-RC3 and Turba 
2.1-RC2.

There it goes. Although I'm not sure if it will help since there are 
files for both Turba and Kronolith.

Can you create a single patch file?

While trying to obtain Free/Busy URLs, Kronolith searchs the backends 
using the default Turba configuration wich makes it use the 'LIKE' 
operand (mail = *email@domain.foo*, for LDAP). Doing that, the results 
returned may be more than one entry, causing Kronolith to discard all 
of them. The correct behavior should search for exact matches (mail = 
email@domain.foo), which would return only one entry if found.

I attached one patch with changes in Turba's (2.0.5) lib/api.php and 
lib/Driver.php and

Kronolith's (2.0.6) lib/Kronolith.php that enforces strict search for 
the 'email' field.

That patch was only tested using LDAP backend and it should be checked 
for more experienced Horde programmers to ensure if it is not breaking 
any compatibility.