similar to: fts-lucene vs SEARCH HEADER

I turned on fts_autoindex today, and wanted to rescan all my mailboxes.... Ran doveadm -Dv fts rescan, and garnered: thebighonker.lerctr.org /home/ler/mail $ doveadm -Dv fts rescan doveadm(ler): Debug: Loading modules from directory: /usr/local/lib/dovecot doveadm(ler): Debug: Module loaded: /usr/local/lib/dovecot/lib20_fts_plugin.so doveadm(ler): Debug: Module loaded:

On 15 Jun 2015, at 21:22, Felix Zielcke <fzielcke at z-51.de> wrote: > > Hi, > > I'm currently looking over the FTS pages to enable it in my dovecot. > But I'm unsure what the best settings of the lucene plugin are, if you > receive german and english mails. > Wiki says: > > textcat_conf=<path> textcat_dir=<path>: If specified, enable

Hi List, Since we migrated from dovecot 1.2.4 to 2.2.12 with lucene as FTS engine, I have this in my error log: Apr 22 14:01:14 indexer-worker(username): Error: lucene index /var/vmail/username/lucene-indexes: IndexWriter() failed (#1): Lock obtain timed out Apr 22 14:01:14 indexer-worker: Error: indexer-worker [username at mydomain.com MailBox-1 - 20800/22707]:

Hi, It looks like I've found something strange. It looks like dovecot updates fts-lucene index every time I'm opening virtual folder that contains FTS query: indexer-worker(dion): Warning: fts-lucene: Settings have changed, rebuilding index for mailbox dovecot-virtual is pretty simple: archive/INBOX BODY "test" first of all, I'm trying to perform FTS in archive/INBOX

Hi, I'm currently looking over the FTS pages to enable it in my dovecot. But I'm unsure what the best settings of the lucene plugin are, if you receive german and english mails. Wiki says: textcat_conf=<path> textcat_dir=<path>: If specified, enable guessing the stemming language for emails and search keywords. This is a little bit problematic in practice, since indexing and

On 2012-11-07 15:14, Timo Sirainen wrote: > On 7.11.2012, at 15.01, Charles Marcus wrote: > >> As one who is interested in implementing FTS sometime in the future, >> I'm curious about what is in store as far as improvements go... >> >> Specifically, any plans for implementing immediate/automatic index >> updates at delivery time? The lack of automatically

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all, Is there a configuration option to set where fts-lucene stores its indexes? I know it defaults to lucene-indexes in the mail root directory. I'm looking to store it in the home directory. Thank you, Greg -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (MingW32) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

I'm getting some log errors with clucene that I am having no luck tracking down on the interwebs. Errors: May 19 05:05:16 indexer-worker(gessel at blackrosetech.com)<62971><aPAEI3zLw17A/QAA0J78UA:EF25M3zLw1779QAA0J78UA>: Error: lucene index /mail/blackrosetech.com/gessel//lucene-indexes: IndexWriter::addDocument() failed (#4): language not available for stemming May 19 05:05:16

Hi Timo, As one who is interested in implementing FTS sometime in the future, I'm curious about what is in store as far as improvements go... Specifically, any plans for implementing immediate/automatic index updates at delivery time? The lack of automatically updated indexes is one downside for its implementation... Also, does the release of Solr 4.0 mean anything for the lucene library

Hello, (recent 2.1alpha2 variant - my test setup known to Timo). No time to diagnose in depth at the moment, but I just noticed that SEARCHing in virtual mailboxes seems not to create lucene index content of its own but use those of referenced mailboxes? The problem is that no new indexing takes place. Example: with INBOX INBOX.in% all in dovecot-virtual, for a given query I only get

Hi, I've just set up fts-lucene and when I run searches on my inbox or when I run the indexer (`doveadm index INBOX`) I get the following segfault. I've run it multiple times and noticed that the data value is different each time so I guess it doesn't always crash at the same point. I'm running dovecot 2.2.13-1 with clucene 2.3.3.4-8 on Arch Linux. If you need any more

Hi, I'm using dovecot (version 2.2.13 on archlinux) in the simplest, no-brainer way possible. It sits between mbsync, which I use to fetch mail from servers, and Gnus, my MUA. Both mbsync and Gnus connect to dovecot with an invocation like this: /usr/lib/dovecot/imap -o mail_location=maildir:$HOME/.mail/ea/ I have three different mail accounts, all that changes is the final directory on the

Hello, as the dovecot documentation is only trivial for FTS Search options, I can't find information on advanced options. I have enabled it but it seems I can only search for entire words, i.e. the word Dovecot can be found by searching "dovecot", but not "dove". Is it possible to achieve this using FTS Lucene? I know that using Solr that achievable setting n-gram.

Hello list, * apache-solr-3.6.2 * dovecot-2.1.7 I configured fts_solr for dovecot, but I have two issues When doing a search request within telnet 127.0.0.1 143 it connects to solr. Jul 21, 2013 4:38:15 PM org.apache.solr.core.SolrCore execute INFO: [] webapp=/solr path=/select params={rows=1&q=box:10361d30f8c4ea51ad7c00002ecaff3b+user:" tom at

Hi all, I'm planning to migrate my courier-imap imap server to dovecot, but I'm experiencing a strange issue with fts-lucene plugin. Basically, every time I start a search, the log starts to write: Apr 05 19:30:53 indexer: Error: Indexer worker disconnected, discarding 1 requests for XXXXXX Apr 05 19:30:53 indexer-worker(XXXXX): Fatal: master: service(indexer-worker): child 809 killed

Hi, I've just enabled FTS via Lucene on my Dovecot 2.2.24 installation but I see the indexer crashing ?always?. This simple testcase with a very tiny testing mailbox exposes the issue immediately: doveadm -v index -u anmesse INBOX Program received signal SIGSEGV, Segmentation fault. rescan_clear_unseen_mailbox (rescan_ctx=rescan_ctx at entry=0x0, vname=0x555555839820 "INBOX.Testfolder

Upgraded to dovecot-1.1.0 today, and activated the fts_lucene plugin. On login with Thunderbird-2.0.0.14, dovecot crashes over and over: Jun 21 14:07:17 airframe dovecot: imap-login: Login: user=<user>, method=CRAM-MD5, rip=192.168.1.1, lip=192.168.1.3, TLS Jun 21 14:07:17 airframe dovecot: child 5712 (imap) killed with signal 11 Jun 21 14:07:17 airframe dovecot: imap-login: Login:

Hi, I've tryed build dovecot with the lucene plugin but I have this is output: /bin/sh ../../../libtool --tag=CXX --mode=compile c++ -DHAVE_CONFIG_H -I. -I../../.. -I../../../src/lib -I../../../src/lib-mail -I../../../src/lib-index -I../../../src/lib-storage -I../../../src/plugins/fts -I../../../src/doveadm -I/usr/local/include -I/usr/local/lib -O2 -pipe -fno-strict-aliasing

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 get an compile error security -Werror=format-security -MT lucene-wrapper.lo -MD -MP -MF .deps/lucene-wrapper.Tpo -c lucene-wrapper.cc -fPIC -DPIC -o .libs/lucene-wrapper.o lucene-wrapper.cc: In function 'lucene_index* lucene_index_init(const char*, mailbox_list*, const fts_lucene_settings*)': lucene-wrapper.cc:128:2: error: 'else' without a previous 'if' make[5]: