similar to: squat fts not working on 2.1rc1

I received this error at the end of a migration from imapc to mdbox. Is it because I wanted doveadm 'sync' instead of 'backup'? I didn't get time to do any testing, but since you're pushing for the release, here it is: kerio2:~ adminuser$ /opt/dovecot/bin/doveadm -o imapc_user=jsample -o imapc_password=****** -o imapc_host=*.*.*.* sync -R -u jsample_dc at mydomain.com

Hi: Just observing that there's been no trumpet blowing about Icecast 2.1RC1 being released, with no link on the website or nothing. For thems that want it, go to http://svn.xiph.org/releases/icecast Also, I presume that this release has the fallbackoverride functionality in it. Probably good to have this in the conf file. This release comes just at the right time for me - I will be

I''m working on porting our app. Do I need to upgrade rspec from 1.1.3? If so which version. BTW the installation doc at http://rspec.info/documentation/rails/install.html seems to be stuck in the pre-git days. -- Rick DeNatale My blog on Ruby http://talklikeaduck.denhaven2.com/

I can confirm the report posted in http://dovecot.org/list/dovecot/2011-November/062263.html that fts_squat no longer seems to be used after moving from 2.0.16->2.1 rc 1. I don't see crash reports in the logs, just "0 messages indexed". My search test tool just does a normal IMAP SEARCH for a long non-existent string. If there's another way to trigger re-indexing in 2.1, I

(anonymous post) I have a simple 2 interface firewall setup and all is good, almost. I am hosting virtual websites and DNS behind shorewall no problem. However I am trying to use SFTP via a different port number and have no luck even though Putty works well. Is there anything weird to sftp and shorewall? My lab uses a different firewall (firestarter) and it works OK. I am using; DNAT net

Hello Timo, I have installed 1.1 beta 8 with fts-squat enabled. I have added the plugin section in dovecot.conf. How can I actually make use of the full text index? Regards, - Joe

Timo, you mentioned you're getting tired of fighting Squat bugs lately. Does that mean you know all the bugs, and just need time to find and fix them? Or should instead I try harder to find bugs by using Dovecot 1.1 on a daily basis, and then sending you copies of mails that break it, like http://www.dovecot.org/list/dovecot/2007-October/026179.html ? -- Asheesh. -- Parting is such

The initial building (and an occational compression) performance just got a major boost. I knew there was a problem there, but I hadn't realized it was this easy to fix: http://hg.dovecot.org/dovecot-1.1/rev/4445415da4ff My 1,4 GB test lkml mbox can be now indexed in 7 minutes, doubling the speed form earlier 14 minutes. I added some more benchmark results here:

I know that a given search index doesn't get built the first time until you do an actual search on it from an IMAP client. I don't much care about that; I'm the only user, and I don't create new folders too often. At worst, I could create a script to go search every folder once. But what I'm not clear about: Does it then get updated on every delivery by LDA? Or does the

It seems, that dovecot-shared ignored by fts squat and dovecot.index.search/dovecot.index.search.uids created with wrong permissions. This makes squat unusable with symlinked shared maildirs. -- WBR, Anton Yuzhaninov

I've been reading about using Squat with Dovecot on large mailboxes. I was wondering if some of the memory usage during searching and indexing could be reduced by using a berkeley db? I've used this in the past for something similar and in BTREE mode it was very fast for millions of keys. I havent had time to look at how squat is implemented, but I thought I'd throw it out there...

Hi I turned on fts squat to speed up full text searches over webmail. This works absolutely fantastic once the mailboxes are indexed. But when they are indexed for the first time I'm getting a fastcgi timeout after 30 seconds resulting into a internal server error on the webserver. In the background the indexing job is getting finished after 80 seconds for a 25k emails, ~300MB mailbox. Does

Hi Im using dovecot 1.2.16 with Solr setup for FTS. When searching a single field such as subject Dovecot will use the solr index. When searching multiple fields such as subject and body it does not use the index and uses the standard built in search which takes much longer. Is there any way to get Dovecot to use the solr or squat index when searching multiple fields? -- View this message in

Hello folks, I use dovecot squat for indexing. I use to have fts_squat = partial=4 full=4 But i change to fts_squat = partial=4 full=8 My question is, do i need to delete older indexes to have it consistenly, or dovecot is able "update" the indexes or it sees that it is broken and rebuild it all? Other question, is there an comand line to update the indexes ? Thanks a lot!

I don't know if this was supposed to have changed with dovecot2, but http://wiki.dovecot.org/Plugins/FTS shows fts = squat solr so, since I have the lucene plugin?"fts = lucene" works by itself?I tried fts = squat lucene but: $ doveadm index '*' doveadm(dave): Error: fts: Failed to initialize backend 'squat lucene': Unknown backend So, is that syntax

Hi, I'm running Dovecot 2.1.12 on FreeBSD. I configured Dovecot to use the Squat plugin to provide faster full-text searches. The output of 'dovecot -n' is attached to this mail. However, I just noticed that this plugin doesn't seem to kick in. A raw telnet session seems to confirm this: [..] . SEARCH BODY abcdefg * OK Searched 57% of the mailbox, ETA 0:06 * SEARCH 3425 6254

Hi, I frequently get errors similar to this logged: Mar 5 17:49:20 alphonse dovecot: imap(roger): Error: Corrupted squat uidlist file /home/roger/Maildir/.Debian/dovecot.index.search.uids: wrong indexid I am running the Debian package version 1:2.1.7-7 on an up to date Debian Testing system with ext4 filing systems. 'doveadm index -A "*"' is run six nights a week and

Hi! I'm using Dovecot 2.1.7 on Debian Wheezy 32-bit (package version is 1:2.1.7-7+deb7u1) with maildirs. My problem is that the incremental indexing of maildirs with squat takes a very long time... I don't know if it reindexes anything, but it seems it iterates though all messages on each search query and reads them. It works fast only on successive queries within several minutes,

Hi Timo and All, after upgrading to 2.1.2 i'm getting a lot of these messages: Error: Corrupted squat uidlist file XXXXXX wrong indexid I did not have them before. Ideas? Luca

Hello, Recently, we had a file system problem. After fsck we started to get some core dump with imap process. Nov 4 15:15:04 mail_server1 dovecot: imap(user at domain.tld): Panic: file squat-trie.c: line 293 (squat_trie_lock): assertion failed: (trie->fd != -1) Nov 4 15:15:04 mail_server1 dovecot: imap(user at domain.tld): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0x4892a)