similar to: Is FTS needed for Subject/Recipient/Sender server-side searches?

Hi, I'm having some trouble writing an FTS plugin that uses notmuch (http://notmuchmail.org/) as the backend. As a proof of concept, I'm adding a hardcoded UID to the search results in the plugin's lookup handler: seq_range_array_add(&result->definite_uids, 1, 42); but this UID is never returned by IMAP SEARCH commands. I know the plugin is being used, since I'm also

Hello, It looks I encoutered a bug or misconfiguration. fts_squat search for subject and body works excellent for English mails. For non-English (in particular, Russian) it works only when query consists of 1 word. Phrases - 2 and more words - always returns nothing. Example: search for "planet" ("???????") returns results, search for "Earth" ("?????") also

Hello, New subscriber here. I noticed that the FTS index is not used in compound searches. Is this expected? Tested in 2.0.0 and 2.0.8: . search BODY "waldo" * SEARCH . OK Search completed (0.000 secs). . SEARCH CHARSET UTF-8 OR SUBJECT "waldo" FROM "waldo" * SEARCH . OK Search completed (1.768 secs). . SEARCH CHARSET UTF-8 OR SUBJECT "waldo" BODY

>> New subscriber here. I noticed that the FTS index is not used in compound searches. >> Is this expected? Tested in 2.0.0 and 2.0.8: > >Yep. It's been in TODO for a while. I know this thread is quite old, but we have the same issue with v2.0.14 and squat. Would this issue also affect the Solr FTS backend? Thanks, Nikolai.

Michael Welsh Duggan <mwd at md5i.com> writes: > Using Debian, dovecot-solr 1:2.2.26.0-4, and solr-tomcat 3.6.2+dfsg-9, I > am getting 400 errors when doing searches. Here is an example search > query from dovecot that failed (captured with wireshark): > > Frame 23: 338 bytes on wire (2704 bits), 338 bytes captured (2704 bits) on interface 0 > Linux cooked capture

On 01/11/2020 15:20, PGNet Dev wrote: > On 11/1/20 1:56 AM, John Fawcett wrote: >> At the moment I don't see other corrections needed in dovecot apart from >> command line doveadm fts which is not a show stopper. Via doveadm search >> I confirm - on my simple config - that search for accented or non >> accented characters works correctly as it does via imap

> On 01/11/2020 20:35 John Fawcett <john at voipsupport.it> wrote: > > > On 01/11/2020 15:20, PGNet Dev wrote: > > On 11/1/20 1:56 AM, John Fawcett wrote: > >> At the moment I don't see other corrections needed in dovecot apart from > >> command line doveadm fts which is not a show stopper. Via doveadm search > >> I confirm - on my simple

On 19/10/2020 01:49, PGNet Dev wrote: > > I've since rebuilt/reconfig'd all parts of my setup from scratch; some > good cleanup along the way. > > Atm, my entire system for send/recv, store/retrieve, + rules & search > is working as I intend.? Ok, mostly ... > > Except for this accented-character search mystery.? I've got a _lot_ > of mail with various

Hi I use roundcube as the webmail fronted to a dovecot server. It currently has squat enabled. When round cube performs a search, it does a compound search even if only one field is selected. >From another thread i read, dovecot in the v1 period did not support compound searches for squat. Does the latest version of V2 support compound searches with fts squat? If not, does fts with solr

Probably better to get the full protocol debug log from the Horde/IMP side. Instructions on how to enable that can be found in imp/config/backends.php. See: https://github.com/horde/imp/blob/master/config/backends.php#L288 rawlog output below only shows what Dovecot is returning - would be more useful to see the entire client round-trip transactions however. > On November 14, 2017 at 4:15

We recently upgraded from Dovecot 1.2.15 (on Debian squeeze) to Dovecot 2.1.7 (on Debian wheezy/stable). For now, we continue to use FTS with Squat indexes. We'd like to eventually switch to Lucene but it's not yet supported in Debian stable. Since upgrading to 2.1.7, we've seen some problems with IMAP search results when an FTS Squat index is present (i.e., when the

Hi! I have a patch and several thoughts about FTS in dovecot. I. SOLR v5.1 and above doesn't allow GET /select queries with Content-Type header set, so, I just removed it from the code: --- dovecot-2.2.18/src/plugins/fts-solr/solr-connection.c 2015-05-13 17:14:45.000000000 +0300 +++ dovecot-2.2.18.patch/src/plugins/fts-solr/solr-connection.c 2015-09-27 19:47:40.363843359 +0300 @@ -432,7

On dovecot 2.2.12 compiled from source I use ActiveSync with kolab-syncroton. When running a test i have this imap log: [29-Mar-2014 22:58:25 +0200]: [F658] S: A0004 OK Getmetadata completed. [29-Mar-2014 22:58:25 +0200]: [F658] C: A0005 SETMETADATA INBOX (/private/vendor/kolab/activesync "{\"DEVICE\":{\"601099122\":{\"ID\":

On 31/10/2020 22:01, PGNet Dev wrote: > On 10/31/20 9:55 AM, John Fawcett wrote: >> I can contribute a patch that solves the segfault. Unfortunately though >> fts search may be more broken than this. It does not give me search >> results, even though I see it querying solr and getting hits. > > Thx -- hopefully it moves this in the right direction. > > Also on the

> On 19/10/2020 02:49 PGNet Dev <pgnet.dev at gmail.com> wrote: > > > I've since rebuilt/reconfig'd all parts of my setup from scratch; some good cleanup along the way. > > Atm, my entire system for send/recv, store/retrieve, + rules & search is working as I intend. Ok, mostly ... > > Except for this accented-character search mystery. I've got a

I've been seeing the following wonky behavior with Dovecot. Currently this is with Dovecot 2.0.19, but I was also seeing it in earlier versions as well, including versions from the 1.x series. Some background, this is from Horde's ActiveSync library, when it is trying to determine what UIDs have recently been expunged. I can guarantee that when this command was sent, there was

Hi, after activating fts/solr, we can see a changed behavior of standard (not fulltext) searches. For example, when searching the 'From' field for something at example.com, before activating solr it was ok to start search for word 'some' and the result was correct and complete (all messages from that user was found). After activating fts/solr, searches like this are

On 2015-04-18 19:23, Kevin Laurie wrote: > Hello, Hello, > I have been trying to get full-text-search on dovecot. I followed the > tutorial on this site:- > https://extremeshok.com/6622/enabling-apache-solr-4-10-using-jetty-with-dovecot-2-2-for-fulltext-search-results-on-centos-6-iredmail-compatible/ > > The instruction on the page here seems wrong:- > sed -i -e

On 11/1/20 1:56 AM, John Fawcett wrote: > At the moment I don't see other corrections needed in dovecot apart from > command line doveadm fts which is not a show stopper. Via doveadm search > I confirm - on my simple config - that search for accented or non > accented characters works correctly as it does via imap connection. thx. hopefully it'll get considered for a next

hi i have dovecot 2.0.9 - the version from rhel6 - and the following setup: two imap-servers with distinct /var/indices. those directory is local only, no sharing. the users mailboxes life on a shared nfs-storage. the two servers are setup active/passive: only one server is active and in case of a problem or maintenance the second server jumps in. no director in place. we would like to