I'm not the admin of the site. I submitted a new request, so a user 
could change/modify the searchbox without messing with templates, js 
or the backend. https://bugs.horde.org/ticket/13623

Thanks for your explanations.

Keywan

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.
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.

You should configure a full text indexing on the imap server. Since we 
have this I mostly use the "Search (Entire Message)" option with a 
result in < 1s.

Hi Michael,

if we are out of scope of this bug report and it is inappropriate to 
ask my questions here, please let me know. Anyway thanks for your 
patience about my request.
Thats nice, because I delete cookies after browser session I never 
experienced this feature before.
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).
I think, the Recipients option is right now very good and the sender 
isn't a "recipient".
Exactly.

For me the drop down list would be grat with

- entire message
- Text
- From
- Recipient
- Subject
- Address or Subject
Evolution has this and I use it all the time. I never want to search 
for "bob" in address and subject, but when I search for "bob" or 
"meeting", I didn't need to use the drop down menu and change the 
filter. Ok, with whole message I never never need to do this, but if I 
wouldn't have performance issues, I wouldn't ask for this feature.

Again, in an ideal world we all would be happy with "

I tried to go to "Erweiterte Suche..." (custom search?!, sorry can't 
switch to english) and to define such search pattern by my own, I 
wasn't successful. Is it possible with Horde Groupware 5.2.0 to add 
items to the search drop down list?

Best

Keywan

Users have always been able to change their "default".  Namely - the 
last search field used is saved.

Technically speaking, a *user* can't change defaults, since they need 
to access the UI at least once - and this first display necessarily 
needs to be set to some kind of setting.  Only admins can define 
defaults.

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 could possibly be talked into adding From to the current 
"Recipients" option (To/Cc/Bcc) and changing into an "All Recipients" 
option.

Then again, there is common use cases for To only searches (i.e. I 
remembered that "bob" sent me a message and want to search for it - I 
don't care about messages that he received).  So not really inclined 
to do this at this time.

It still makes zero sense to me to combine address searching with 
subject searching.

So in future each admin can change the default search criteria? 
Wouldn't it be nice, that a user can change this. If you where admin 
on a webmail I use, at least on of us would be sad ;)
Ok, that is correct. But I have a subfolder with 20000 mails and it 
took ages for the result list (ok ca. 60s).

What about to add FROM/TO/CC/BCC/Subject to the set of predefined 
searches? (Or the ability to add custom searches to the list).

I think a search filter "Adress or Subject" is a good compromise 
between fuzzy enough and performance.

Thanks, Keywan

The dynamic_prefs hook has been added to git master to allow for an 
admin to change the default search criteria.

And it doesn't make sense to default to a header only search since 
that's not how a "normal" user thinks search works.  90% of my 
searches are for message *content*.  I don't know/care who sent me a 
message most of the time, and subject's are pretty much worthless for 
a general search since they often have very little connection to the 
context of the message

The current default is correct.

Oops, wrong ticket, sorry.

For framework libraries, yes, this is planned for Horde 6.
For application installation, probably not yet, because Composer is 
still far from being on par with PEAR in that domain.

The default search pattern in the webmail module is "Search (whole 
mail)" [Gesamte Nachricht]. The search takes a long time and the 
results are to fuzzy.

A better default search pattern in webmail is in my opinion 
FROM/TO/CC/BCC/Subject (often refered as Address or Subject). This is 
fast and cover 90% of the cases.