[Tickets #13616] Re: Change default search pattern in webmail to FROM/TO/CC/BCC/Subject

[noreply at bugs.horde.org]

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

Ticket URL: https://bugs.horde.org/ticket/13616
------------------------------------------------------------------------------
  Ticket             | 13616
  Updated By         | Michael Slusarz <slusarz at horde.org>
  Summary            | Change default search pattern in webmail to
                     | FROM/TO/CC/BCC/Subject
  Queue              | Horde Groupware Webmail Edition
  Version            | 5.2.0
  Type               | Enhancement
  State              | Rejected
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


Michael Slusarz <slusarz at horde.org> (2014-10-08 14:44) wrote:

>> OK - but how is header searching any faster?  Unless you are making
>> an assumption that the IMAP server indexes header - but there is
>> absolutely no way that is guaranteed.
>
> I searched for a term only in To, Address or Subject (each an own  
> search) and another custom search for address or subject. Each  
> search only need 2-3 seconds. The search for whole text took 60s  
> (maybe a timeout).

Then you have an IMAP server (like Dovecot) that caches header/search  
information.  But realize that 1.) this cache isn't guaranteed on that  
server, and 2.) not all IMAP servers run this.

So from a default software configuration perspective (i.e. how Horde  
is distributed), you can't say with any certainty that a header search  
is noticably faster than a body search.

> Is it possible with Horde Groupware 5.2.0 to add items to the search  
> drop down list?

As open source software, anything is changeable locally.  This  
particular request would probably be a bit more difficult since you  
not only need to change the template, you also need to change the  
javascript to handle the additional search option and to change the  
backend server code to actually do the search you defined.