similar to: dovecot fts_lucene indexes not being updated

I found this in mail.err. Anyone ever experience this? May 22 14:51:51 mba dovecot: imap(formulaire): Panic: file lucene-wrapper.cc: line 196: unreached May 22 14:51:51 mba dovecot: imap(formulaire): Error: Raw backtrace: /opt/dovecot-2.1.6-lucene/lib/dovecot/libdovecot.so.0(+0x4200a) [0x7f7e0edfd00a] -> /opt/dovecot-2.1.6-lucene/lib/dovecot/libdovecot.so.0(+0x4204e) [0x7f7e0edfd04e] ->

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 'good news' page, it appears there's been some progress on

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>

According to the IMAP spec if I do a search for "TO isocpp.org" it should find all the messages whose To: field contains the string "isocpp.org", but dovecot is returning me an empty list. However, a search for "TO tm at isocpp.org" produces a long list of messages. This behavior is present if I *even load* the lucene fts plugin. Note that lucene isn't in use

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

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

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

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 there! I compiled dovecot 2.3 from git. Because there is already a bug in virtual-plugin, and i hoped, it get fixed... but it doesn't. So this is the error-message from the log J?n 03 16:27:08 aldebaran dovecot[26460]: indexer-worker(jakob)<26476><qQ6g1+BhIJvAqAAO:sjYhMTH2TFpsZwAAk1Mx3g>: Panic: file unichar.c: line 160 (uni_ucs4_to_utf8_c): assertion failed:

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

Hi everyone, I have a question concerning UIDs. How persistant are they? I am thinking about building some form of webmail specialized for some specific business purpose and I am thinking of building a sort of cache in a DB by storing the email addr, date, subject and UID for quick lookups and search of correspondance. I am doing this because I am having issue with multiple people searching

Dear list, We been having some issues where the indexer-worker is crashing. This happens on production servers which are handling a slight amount of mail, but is also reproducible by moving messages. Also, users on my server are complaining about "Trashed" items coming back etc. Some details: - Dovecot 2.3.2.1 in alpine:3.8 based Docker container. As part of the Mailu distribution.

Hi, On 30/10/2017 7:22 PM, dovecot-request at dovecot.org wrote: > Message: 6 > Date: Mon, 30 Oct 2017 10:22:42 +0200 > From: Teemu Huovila <teemu.huovila at dovecot.fi> > To: dovecot at dovecot.org > Subject: Re: dovecot-2.3 (-git) Warning and Fatal Compile Error > Message-ID: <7d2c0b5b-019a-067c-c6be-f36571ed9a96 at dovecot.fi> > Content-Type: text/plain;

Hi, I am planning on running on test between maildir and mdbox to see which is a better fit for my use case. And I'm just looking for general advice/recommendation. I will post any results I obtain here. Important question: I have multiple users hitting the same email account at the same time. Can be a problem with mdbox? (either via thunderbird or with custom webmail apps). I remember

Hello, I have an "archive" folder in my inbox, where I manually stick old mails into a compressed mbox format. Since upgrading to Dovecot 2.2.1, I've started seeing messages like the following in my log files: imap(...): Error: lucene: Failed to sync mailbox INBOX: Mailbox isn't selectable indexer-worker(...): Error: lucene: Failed to sync mailbox INBOX: Mailbox

Hi list, This issue was raised here by John Fawcett on 12/02/19 but got no response. So, as I'm facing the same issue, I would like to try again: When using the vacation sieve extension, if I send an email to user.name at mydomain.com it will work, but not to User.Name at mydomain.com. Is there a way to make the user part case insensitive so that the vacation auto-reply is fired whatever

Hi, When I enable (and it only happens when it is actually running) replication over TCP my users get duplicate mails via pop3. Here?s what happens: * User gets mail * Mail appears in (Maildir) new/ folder on both replicas * user retrieves mail (retr), calls dele. Mail still exists in new/ folder on both replicas. * user runs retr (and gets the duplicate) and dele a second time, the mail is

Hi all, are there any pitfalls known for the migration from 2.0.18 to 2.1? Can I simply stop dovecot, make install and start again? --Frank Elsner

Currently I'm having massive problems with LMTP delivery into dovcot. dovecot/lmtp processes are piling up, eas using considerable amounts of CPU: # ps auxwww|fgrep dove root 20537 0.0 0.0 18124 1196 ? Ss 15:18 0:00 /usr/sbin/dovecot -c /etc/dovecot/dovecot.conf dovecot 20541 0.0 0.0 9620 1084 ? S 15:18 0:00 dovecot/anvil root 20542 0.0 0.0 9752

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