Mmm I’ll try too to take a look at these when I have a little time… We though
all could came from a Roundcube bug when dealing with mail threads… apart from
that, we didn’t really know too how these search commands (that a THREAD
command existed) worked too… we should have tried seeing it by ngr
Hi,
Please try disabling the threads or conversación view in Roundcube and repleta
the search,
Cheers!
Egoitz,
> El 24 feb 2020, a las 11:04, "ego...@sarenet.es" escribió:
>
> Hi Simon,
>
> Try selecting the non conversation view before doing the search. It seems
> Roundcube has something
Hi Simon,
Try selecting the non conversation view before doing the search. It seems
Roundcube has something weird there… but I could assure you it uses it when you
set the non-conversation (non thread view). I think really it does even there,
but perhaps it enter in a non-controlled loop with a
I don't really understand search in any depth, but it's interesting to observe
that, in addition to the different command (SEARCH vs THREAD), those two
searches are also using different search criteria ("BODY linux" vs "TEXT
linux").
It might be informative to try do the SEARCH search with "TEX
I have configured Cyrus 3.0.13 with the Xapian search engine and
enabled search_fuzzy_always. This appears to work fine when I search in
the message body using the Evolution mail client, as I get a response
quickly:
<15824537091582453713>* SEARCH 226927
226929 226964 226974 226999 227215 227238 [.