[Tickets #12480] Re: Autocomplete includes all addresses for a user where any of them match

[n***@bugs.horde.org]

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

Ticket URL: http://bugs.horde.org/ticket/12480
------------------------------------------------------------------------------
Ticket | 12480
Updated By | ***@simonandkate.net <***@simonandkate.net>
Summary | Autocomplete includes all addresses for a user where
| any of them match
Queue | IMP
Version | 6.1.3
Type | Enhancement
State | New
Priority | 1. Low
Milestone |
Patch |
Owners |
------------------------------------------------------------------------------


***@simonandkate.net (2013-07-19 12:12) wrote:

See attached example - typing simonandkate returns both Katie's email
addresses, even the one that does not include that string. Same with
names, not just domains.

Not too much of an issue in a small address book, but in a larger one
this could be troublesome.

Ideally the a/c should only return addresses that match the entered string.



***@simonandkate.net (2013-07-19 12:12) uploaded: ac.png

Loading Image...

[n***@bugs.horde.org]

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

Ticket URL: http://bugs.horde.org/ticket/12480
------------------------------------------------------------------------------
Ticket | 12480
Updated By | Jan Schneider <***@horde.org>
Summary | Autocomplete includes all addresses for a user where
| any of them match
Queue | IMP
Version | 6.1.3
Type | Enhancement
-State | New
+State | Feedback
Priority | 1. Low
Milestone |
Patch |
Owners |
------------------------------------------------------------------------------


Jan Schneider <***@horde.org> (2013-07-19 17:23) wrote:

Cannot reproduce. I actually don't even get matches for email
addresses at the moment.

[n***@bugs.horde.org]

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

Ticket URL: http://bugs.horde.org/ticket/12480
------------------------------------------------------------------------------
Ticket | 12480
Updated By | Jan Schneider <***@horde.org>
Summary | Autocomplete includes all addresses for a user where
| any of them match
Queue | IMP
Version | 6.1.3
Type | Enhancement
State | Feedback
Priority | 1. Low
Milestone |
Patch |
Owners |
------------------------------------------------------------------------------

Post by n***@bugs.horde.org
Cannot reproduce. I actually don't even get matches for email
addresses at the moment.

Nevermind, I expected the AC to default to searching all available
search fields, it defaults to name only though. Still cannot reproduce
what you see though.

[n***@bugs.horde.org]

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

Ticket URL: http://bugs.horde.org/ticket/12480
------------------------------------------------------------------------------
Ticket | 12480
Updated By | ***@simonandkate.net
Summary | Autocomplete includes all addresses for a user where
| any of them match
Queue | IMP
Version | 6.1.3
Type | Enhancement
State | Feedback
Priority | 1. Low
Milestone |
Patch |
Owners |
------------------------------------------------------------------------------


***@simonandkate.net (2013-07-22 00:04) wrote:

I have an SQL backend for Turba, with the primary address book having
three email address fields selected for name matching in Imp
preferences. I wonder if it's something to do with that multiple match?

[n***@bugs.horde.org]

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

Ticket URL: http://bugs.horde.org/ticket/12480
------------------------------------------------------------------------------
Ticket | 12480
Updated By | Michael Slusarz <***@horde.org>
Summary | Autocomplete includes all addresses for a user where
| any of them match
Queue | IMP
Version | 6.1.3
Type | Enhancement
State | Feedback
Priority | 1. Low
Milestone |
Patch |
Owners |
------------------------------------------------------------------------------


Michael Slusarz <***@horde.org> (2013-07-23 13:22) wrote:

I can verify that this works fine for me. Here's the SQL statement
that appears in the DEBUG logs (searching for the string "test"):

2013-07-23T13:21:01-06:00 DEBUG: HORDE [turba] SQL (0.0144s)
SELECT object_id, object_type, owner_id, object_members,
object_nameprefix, object_firstname, object_middlenames,
object_lastname, object_namesuffix, object_email FROM turba_objects
WHERE (owner_id = 'slusarz' AND (object_firstname ILIKE '%test%' OR
object_lastname ILIKE '%test%' OR object_middlenames ILIKE
'%test%' OR
object_nameprefix ILIKE '%test%' OR object_namesuffix ILIKE '%test%'
OR (object_nameprefix ILIKE '%test%' OR object_firstname ILIKE
'%test%' OR object_middlenames ILIKE '%test%' OR
object_lastname ILIKE
'%test%' OR object_namesuffix ILIKE '%test%') OR object_alias ILIKE
'%test%' OR object_yomifirstname ILIKE '%test%' OR
object_yomilastname
ILIKE '%test%' OR object_bday ILIKE '%test%' OR object_anniversary
ILIKE '%test%' OR object_spouse ILIKE '%test%' OR object_phototype
ILIKE '%test%' OR object_homestreet ILIKE '%test%' OR object_homepob
ILIKE '%test%' OR object_homecity ILIKE '%test%' OR
object_homeprovince ILIKE '%test%' OR object_homepostalcode ILIKE
'%test%' OR object_homecountry ILIKE '%test%' OR (object_nameprefix
ILIKE '%test%' OR object_firstname ILIKE '%test%' OR
object_middlenames ILIKE '%test%' OR object_lastname ILIKE
'%test%' OR
object_namesuffix ILIKE '%test%' OR object_homestreet ILIKE '%test%'
OR object_homecity ILIKE '%test%' OR object_homeprovince ILIKE
'%test%' OR object_homepostalcode ILIKE '%test%') OR
object_workstreet
ILIKE '%test%' OR object_workpob ILIKE '%test%' OR object_workcity
ILIKE '%test%' OR object_workprovince ILIKE '%test%' OR
object_workpostalcode ILIKE '%test%' OR object_workcountry ILIKE
'%test%' OR (object_nameprefix ILIKE '%test%' OR object_firstname
ILIKE '%test%' OR object_middlenames ILIKE '%test%' OR
object_lastname
ILIKE '%test%' OR object_namesuffix ILIKE '%test%' OR
object_homestreet ILIKE '%test%' OR object_homecity ILIKE
'%test%' OR
object_homeprovince ILIKE '%test%' OR object_homepostalcode ILIKE
'%test%' OR object_workstreet ILIKE '%test%' OR
object_workcity ILIKE
'%test%' OR object_workprovince ILIKE '%test%' OR
object_workpostalcode ILIKE '%test%') OR object_otherstreet ILIKE
'%test%' OR object_otherpob ILIKE '%test%' OR object_othercity ILIKE
'%test%' OR object_otherprovince ILIKE '%test%' OR
object_otherpostalcode ILIKE '%test%' OR object_othercountry ILIKE
'%test%' OR (object_nameprefix ILIKE '%test%' OR object_firstname
ILIKE '%test%' OR object_middlenames ILIKE '%test%' OR
object_lastname
ILIKE '%test%' OR object_namesuffix ILIKE '%test%' OR
object_homestreet ILIKE '%test%' OR object_homecity ILIKE
'%test%' OR
object_homeprovince ILIKE '%test%' OR object_homepostalcode ILIKE
'%test%' OR object_workstreet ILIKE '%test%' OR
object_workcity ILIKE
'%test%' OR object_workprovince ILIKE '%test%' OR
object_workpostalcode ILIKE '%test%' OR object_otherstreet ILIKE
'%test%' OR object_othercity ILIKE '%test%' OR object_otherprovince
ILIKE '%test%' OR object_otherpostalcode ILIKE '%test%') OR
object_department ILIKE '%test%' OR object_manager ILIKE '%test%' OR
object_assistant ILIKE '%test%' OR object_tz ILIKE '%test%' OR
object_email ILIKE '%test%' OR object_homephone ILIKE '%test%' OR
object_homephone2 ILIKE '%test%' OR object_homefax ILIKE '%test%' OR
object_workphone ILIKE '%test%' OR object_workphone2 ILIKE
'%test%' OR
object_cellphone ILIKE '%test%' OR object_carphone ILIKE '%test%' OR
object_radiophone ILIKE '%test%' OR object_companyphone
ILIKE '%test%'
OR object_assistantphone ILIKE '%test%' OR object_fax ILIKE '%test%'
OR object_pager ILIKE '%test%' OR object_title ILIKE '%test%' OR
object_role ILIKE '%test%' OR object_company ILIKE '%test%' OR
object_logotype ILIKE '%test%' OR object_category ILIKE '%test%' OR
object_notes ILIKE '%test%' OR object_url ILIKE '%test%' OR
object_freebusyurl ILIKE '%test%' OR object_pgppublickey ILIKE
'%test%' OR object_smimepublickey ILIKE '%test%' OR object_imaddress
ILIKE '%test%' OR object_imaddress2 ILIKE '%test%' OR
object_imaddress3 ILIKE '%test%')) [pid 7223 on line 558 of
"/disk2/src/horde/framework/Db/lib/Horde/Db/Adapter/Base.php"]

[n***@bugs.horde.org]

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

Ticket URL: http://bugs.horde.org/ticket/12480
------------------------------------------------------------------------------
Ticket | 12480
Updated By | ***@simonandkate.net
Summary | Autocomplete includes all addresses for a user where
| any of them match
Queue | IMP
Version | 6.1.3
Type | Enhancement
State | Feedback
Priority | 1. Low
Milestone |
Patch |
Owners |
------------------------------------------------------------------------------


***@simonandkate.net (2013-07-25 11:33) wrote:

I got it...

I see this when typing "simona" in for AC:

2013-07-25T10:56:12+00:00 DEBUG: HORDE [turba] SQL (0.0023s)
SELECT object_id, object_type, owner_id, object_members,
object_lastname, object_firstname, object_middlenames,
object_namesuffix, object_email FROM turba_objects WHERE (owner_id =
'simon' AND ((LOWER(object_lastname) LIKE LOWER('%simona%') OR
LOWER(object_firstname) LIKE LOWER('%simona%') OR
LOWER(object_middlenames) LIKE LOWER('%simona%') OR
LOWER(object_namesuffix) LIKE LOWER('%simona%')) OR
LOWER(object_email) LIKE LOWER('%simona%') OR LOWER(object_email2)
LIKE LOWER('%simona%') OR LOWER(object_email3) LIKE
LOWER('%simona%'))) [pid 12252 on line 558 of
"/usr/share/pear/Horde/Db/Adapter/Base.php"]
2013-07-25T10:56:12+00:00 DEBUG: HORDE [turba] LDAP query by
Turba_Driver_ldap::_search(): user = simon, root =
ou=shared_addressbook,dc=simonandkate,dc=lan (ldap.simonandkate.lan);
filter = "(|(cn=*simona*)(mail=*simona*))"; attributes = "dn,
turbaType, turbaMembers, cn, mail, sn"; deref = "0" ; sizelimit = 200
[pid 12252 on line 195 of "/var/www/horde/turba/lib/Driver/Ldap.php"]

The "aquenta" email address that is being returned in the graphic
attached to this ticket is located in SQL object_email only, not in
LDAP at all.

Manually executing that SQL statement shows me that the script is
matching the "simona" as LIKE against object_email2 for Katie (where
that address resides), but then the SELECT statement is only returning
object_email, which contains the aquenta email address.

If I exclude the LDAP directory from the search, I see object_email
returned for the two SQL address book entries that match:

Mine, where object_email is simon AT simonandkate.net, and katie's
where it is AT aquenta..., thus returning an email address that does
not match the search query. So I have no way of auto-completing
Katie's simonandkate email address unless I move it to object_email
instead of object_email2, despite that AC actually searches them all
for matches.

[n***@bugs.horde.org]

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

Ticket URL: http://bugs.horde.org/ticket/12480
------------------------------------------------------------------------------
Ticket | 12480
Updated By | Michael Slusarz <***@horde.org>
Summary | Autocomplete includes all addresses for a user where
| any of them match
-Queue | IMP
+Queue | Turba
-Version | 6.1.3
+Version | Git master
Type | Enhancement
State | Feedback
Priority | 1. Low
Milestone |
Patch |
Owners |
------------------------------------------------------------------------------


Michael Slusarz <***@horde.org> (2013-07-25 13:15) wrote:

So where/why are you defining object_email2 and object_email3? That
doesn't appear anywhere in Turba (or Horde for that matter). We only
use object_email.

I would guess you have a badly outdated backends.local.php config.

[n***@bugs.horde.org]

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

Ticket URL: http://bugs.horde.org/ticket/12480
------------------------------------------------------------------------------
Ticket | 12480
Updated By | ***@simonandkate.net
Summary | Autocomplete includes all addresses for a user where
| any of them match
Queue | Turba
Version | Git master
Type | Enhancement
State | Feedback
Priority | 1. Low
Milestone |
Patch |
Owners |
------------------------------------------------------------------------------

Post by n***@bugs.horde.org
So where/why are you defining object_email2 and object_email3? That
doesn't appear anywhere in Turba (or Horde for that matter). We
only use object_email.
I would guess you have a badly outdated backends.local.php config.

http://wiki.horde.org/TurbaExtraFields

I wrote that 2 years ago when the extra email addresses were not
supported through ActiveSync, to give full support for three addresses
through Horde / ActiveSync / iOS.

Upgrades along the way have not broken anything with that
configuration that I setup, so I have never needed to change it.

I will look through the newer setup and see about migrating the
addresses into the newer objects.

So if I have email addresses in object_email, object_homeemail,
object_workemail (is that what the new ones are called?), will
autocomplete in Imp search all (if those fields specified in Mail
Prefs), and return all matching objects?

Thanks.

[n***@bugs.horde.org]

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

Ticket URL: http://bugs.horde.org/ticket/12480
------------------------------------------------------------------------------
Ticket | 12480
Updated By | Michael Slusarz <***@horde.org>
Summary | Autocomplete includes all addresses for a user where
| any of them match
Queue | Turba
Version | Git master
Type | Enhancement
State | Feedback
Priority | 1. Low
Milestone |
Patch |
Owners |
------------------------------------------------------------------------------

Post by n***@bugs.horde.org
So if I have email addresses in object_email, object_homeemail,
object_workemail (is that what the new ones are called?), will
autocomplete in Imp search all (if those fields specified in Mail
Prefs), and return all matching objects?

Yes, if that's how you have configured Turba's backend. But turba
isn't going to return these values unless you've configured it to do so.

So I guess I'm still not seeing the issue(?)

[n***@bugs.horde.org]

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

Ticket URL: http://bugs.horde.org/ticket/12480
------------------------------------------------------------------------------
Ticket | 12480
Updated By | ***@simonandkate.net
Summary | Autocomplete includes all addresses for a user where
| any of them match
Queue | Turba
Version | Git master
Type | Enhancement
State | Feedback
Priority | 1. Low
Milestone |
Patch |
Owners |
------------------------------------------------------------------------------


***@simonandkate.net (2013-07-31 11:17) wrote:

Thanks, I will sort out on the weekend and report back on success.
Concentrating on Bug 12486 at the moment.

[n***@bugs.horde.org]

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

Ticket URL: http://bugs.horde.org/ticket/12480
------------------------------------------------------------------------------
Ticket | 12480
Updated By | ***@thebennetthome.com
<***@thebennetthome.com>
Summary | Autocomplete includes all addresses for a user where
| any of them match
Queue | Turba
Version | Git master
Type | Enhancement
State | Feedback
Priority | 1. Low
Milestone |
Patch |
Owners |
------------------------------------------------------------------------------


***@simonandkate.net (2013-07-31 11:17) wrote:

Thanks, I will sort out on the weekend and report back on success.
Concentrating on Bug 12486 at the moment.

[n***@bugs.horde.org]

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

Ticket URL: http://bugs.horde.org/ticket/12480
------------------------------------------------------------------------------
Ticket | 12480
Updated By | ***@messinet.com <***@messinet.com>
Summary | Autocomplete includes all addresses for a user where
| any of them match
Queue | Turba
Version | Git master
Type | Enhancement
State | Feedback
Priority | 1. Low
Milestone |
Patch |
Owners |
------------------------------------------------------------------------------


***@simonandkate.net (2013-07-31 11:17) wrote:

Thanks, I will sort out on the weekend and report back on success.
Concentrating on Bug 12486 at the moment.