[Tickets #12917] Re: Match the ActiveSync GAL search fields with Turba backend

[noreply at bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: https://bugs.horde.org/ticket/12917
------------------------------------------------------------------------------
  Ticket             | 12917
  Updated By         | Michael Rubinsky <mrubinsk at horde.org>
  Summary            | Match the ActiveSync GAL search fields with Turba
                     | backend
  Queue              | Synchronization
  Version            | Git master
  Type               | Enhancement
  State              | Resolved
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             | Michael Rubinsky
------------------------------------------------------------------------------


Michael Rubinsky <mrubinsk at horde.org> (2014-10-07 16:57) wrote:

>> There were too many results being found due to incorrectly specifying
>> the fields to search.
> This results in too many contacts in the search result or not one?

It depends. It could be so many that the  maximum is reached, so the  
actual one you are looking for never makes it to the device. Still,  
the device can filter the results on it's own too so it's possible you  
would never see those that don't match the search string.


> Horde_Core                 2.14.2  stable
> Horde_ActiveSync           2.19.3  stable

The fix is actually in Turba.

>> However, what is probably happening for you is that most clients will
>> not display the result unless the name or email contains the searched
>> text.
> I search for example the word "example", then I should find the  
> contact with the mail address "name at example.com", true? At the  
> moment I found it only if I search for the name.

Look at the synclog and see what is actually being sent to the client.