similar to: dovecot 2.2.10 & fts_lucene: Failed to initialize backend

Hi ML! Please look at this: - I've got no lucene-index: > # ls /dane/domeny/mejor.pl/mail/marcin/.maildir/lucene-indexes > ls: cannot access /dane/domeny/mejor.pl/mail/marcin/.maildir/lucene-indexes: No such file or directory - run search in body: > echo -e "a select bugzilla\na search body flto\na logout\n" | /usr/libexec/dovecot/imap -u marcin at mejor.pl > * PREAUTH

Hi everybody... I've inherited 2 servers with dovecot and fts_lucene enabled, which I plan to switch to fts-solr instead. My plan is to disable lucene in dovecot.conf, delete all cache associated files, and start configuring the fts plugin from scratch. I need to make sure that I don't mess up things pretty bad and delete the correct files. Are those to be deleted all dovecot.index*

Hi, Is there any way to hide this folder from IMAP clients? I can see it is not runtime configurable and just #defined as LUCENE_INDEX_DIR_NAME in fts-backend-lucene.c. -- Nicholas Riley <njriley at illinois.edu>

Hi, Darix, Marcus Rueckert <darix at opensu.se> schrieb: >On Sun, 17 May 2015 17:29:54 +0200 >Hanns Mattes <hanns at hannsmattes.de> wrote: >> [lucene-fts error] >I asked Timo about it already on irc but no answer yet. could be >related to enabling textcat support, which might have indirectly turn >on some libstemmer code. Ah, good to know. I've switched to

Am 12.02.2015 um 15:47 schrieb Martin ?tefany: > Hello, > > I've ran into problem with Dovecot and dsync replication. Everything > works perfectly, including replication of sieve scripts, except fact > that if user activates the 'managesieve' ruleset (I'm using currently > Roundcubemail) on "mail1" host, it wouldn't be activated on

Hi, after upgrading to 2.2.18 I get the following error: lmtp(root at bruecko.de): Error: Couldn't load required plugin /usr/lib64/dovecot/modules/lib21_fts_lucene_plugin.so: dlopen() failed: /usr/lib64/dovecot/modules/lib21_fts_lucene_plugin.so: undefined symbol: _ZN6lucene8analysis8snowball16SnowballAnalyzerC1EPFiPKvmP6bufferEPKc Running Opensuse 13.2 I'm using the RPMs from the

Hello, I've ran into problem with Dovecot and dsync replication. Everything works perfectly, including replication of sieve scripts, except fact that if user activates the 'managesieve' ruleset (I'm using currently Roundcubemail) on "mail1" host, it wouldn't be activated on "mail2" host, by creating symlink ".dovecot.sieve ->

hi all, I've been tasked to add sieve/managesieve to an existing dovecot cluster running 2.1.7 on debian wheezy which is made up of 2 dovecot-proxy hosts as directors and some back end dovecot imap hosts all running the same version. My problem is that I thought to put the service on the director/proxy hosts since they wouldn't have too much load on it, but when I do I get the

> We'll need the `dovecot -n` output first. Here we go: > # 2.2.devel (933d16f): /etc/dovecot/dovecot.conf > # Pigeonhole version 0.4.devel (63f9b42) > # OS: Linux 3.13.0-98-generic x86_64 Ubuntu 14.04.5 LTS > default_vsz_limit = 2 G > lmtp_user_concurrency_limit = 10000 > mail_attachment_dir = /home/copymail/attachments > mail_location = mdbox:~/mdbox >

I set up system copying all mails to a backup system. This used to work without a hitch - now in the last few days mails would pile up in the Postfix Queue, waiting to be delivered using the lmtp transport into dovecot. So dovecot was being slow, but why? After all, nothing changed. After reading some articles on stackoverflow I found a way of finding out which file gets the most IO: % sysdig

On 13/11/2020 14:56, PGNet Dev wrote: > I've built a new dovecot + fts-solr instance; I've now picked up & am > running the recently released solr 8.7.0. > > In a test account, I've one message -- in the 'Drafts' folder. > > On exec of fts 'index' > > ????doveadm index -u testuser at example.com -q '*' > > I get a > >

Hi, I am trying to update my old mails servers from dovecot 2.1.15 to 2.2.12 (freebsd ports) and upgrade to FreeBSD 10.0-P3. My mail storage are on NFS with index also. On 2.1.15 everything is ok, and in 10-mail.conf I have the good things to be added as wiki tell me (eg http://wiki2.dovecot.org/NFS). BUT, when I try a single connection like : $ telnet ::1 110 Trying ::1... Connected to

I'm using release 2.2.12, during a copy operation i get segfault on imap process. I have full bt of the issue: (gdb) bt #0 0x00007fcc521029cd in mail_cache_header_fields_read (cache=0x15c7210) at mail-cache-fields.c:369 #1 0x00007fcc52100664 in mail_cache_open_and_verify (cache=0x15c7210) at mail-cache.c:497 #2 0x00007fcc5210244d in mail_cache_register_get_list (cache=0x15c7210,

Hello Aki. Here it is. Some sensitive data was replaced by ***. # 2.2.25 (7be1766): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.15 (97b3da0) # OS: Linux 3.10.0-***.el7.x86_64 x86_64 CentOS Linux release 7.*** (Core) ext4 auth_cache_negative_ttl = 15 secs auth_cache_size = 8 M auth_cache_ttl = 15 secs auth_default_realm = *** auth_mechanisms = plain login digest-md5 cram-md5 ntlm

Hi, since migration to Dovecot 2.2 I have troubles with lazy_expunge as soon as a user shares a folder. The user the folder is shared to cannot login anymore, dovecot logs Fatal: lazy_expunge: Unknown namespace: '.EXPUNGED/' - When no folder is shared lazy_expunge is working fine, deleted mails are moved to the expunged namespace and can be recovered without any problems. - Sharing

Hi, I've setup FTS using lucene and it should be working, the lucene index is updated when mail arrives. I also managed to reindex my INBOX: doveadm index -u foo -q INBOX However, when I try to index an Archives folder: doveadm index -u foo -q Archives, the index-work crashed with this log message: dovecot: indexer-worker(foo): Panic: file message-decoder.c: line 363

Op 22-8-2017 om 13:03 schreef Darac Marjal: > On Tue, Aug 22, 2017 at 01:55:45PM +0300, Aki Tuomi wrote: >> >> >> On 22.08.2017 13:37, Darac Marjal wrote: >>> Hello all, >>> >>> Hopefully this is something fairly simple. >>> >>> I've been trying to set up the Sieve Antispam system as detailed at >>>

* Timo Sirainen via dovecot <dovecot at dovecot.org>: > > And alas, I had a look at the monitoring and found that disk IO has > > increase A LOT after the update: https://www.arschkrebs.de/images/dovecot-disk-io-increase.png > > > > I zoomed in and found that the sudden increace in IO coincides with > > the update to 2.3.7 (14:35):

Hi everyone, I have a dovecot 2.1.6 setup with fts_lucene. The lucene indexes get created/updated fine when I do a manual search thru telnet. However, if I run a webapp that uses the php::imap_search function, the index never gets created/updated. I run indo the same problem with thunderbird and full-body search. Anyone has some insight into this? Regards, -Joe

Hello, About once or twice a week, dovecot's imap-login process on my system seems gets out of control, eating 100% CPU for about 2 hours. Afterwards everything seems to go back to normal. I am using Dovecot 2.1.7 on a 64 bit Debian wheezy system. When running gdb on the process in this stage, I get the following traceback: #0 0x00007fcba50c5a90 in read () from