similar to: better body and text search?

I've noticed that when using Lucene full text search, most queries use the indexes and/or header cache and are fast: . SEARCH BODY test . OK Search completed (0.001 secs). . SEARCH SUBJECT test . OK Search completed (0.053 secs). . SEARCH BODY test SUBJECT test . OK Search completed (0.002 secs). . SEARCH OR SUBJECT test FROM test . OK Search completed (0.093 secs). But an OR query that

There are now two full text search backends in CVS HEAD: - squat: My own full text search index based on ideas from Cyrus Squat indexes. Supports substring searches. - lucene: Uses CLucene library. It should be pretty easy to add support for more backends. As I've explained a couple of times already, IMAP RFC says that searches are done by matching substrings, so the Lucene backend

As described earlier (http://dovecot.org/list/dovecot/2006-December/018055.html), Dovecot nowadays has full text search indexing support in CVS HEAD. Currently there are two backends: Lucene and Squat. Lucene's problem is that standard IMAP SEARCH command can't be used with it without breaking IMAP RFC. So Lucene can be used only with non-standard X-BODY-FAST and X-TEXT-FAST search

http://saunderslog.com/2009/03/03/voxeo-launches-tropocom-mashup-platfor m/ I'll pay anyone a $20 bounty for someone to replicate the USA Asterisk Weather App on Tropo. Would like to see how quickly this is implemented. Regards, Dean Collins Cognation Inc dean at cognation.net <mailto:dean at cognation.net> +1-212-203-4357 New York +61-2-9016-5642 (Sydney

On 2 July 2013 09:58, Martin Kletzander <mkletzan@redhat.com> wrote: > I'd say this is a problem with sasl, nothing else. "No mechanism found" > may mean that libraries for configured mechanism aren't found or unknown > mechanism is being requested. I doubt that access to those libraries > would be a permisison problem, but you might be missing some >

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

Hello! Dovecot uses it's own SASL implementation, doesn't it? Aug 14 23:45:23 example.com auth[10428]: GSSAPI client step 1 Aug 14 23:45:23 example.com auth[10428]: encoded packet size too big (813804546 > 65536) Aug 14 23:45:23 example.com dovecot[10085]: auth-worker(10428): Error: LDAP: Can't connect to server: ldap://ipa2.example.com Aug 14 23:45:23 example.com

I suspect the problem is that dovecot tries to report LDAP error over GSSAPI. So the best fix is to make sure your LDAP server does not return error. =) Aki On 15.8.2019 14.56, Eugene Bright wrote: > That's right. > GSS-API is not used anywhere else. > Do you like to inspect my full configuration? > I can dump connection session and send pcap file here. > > On August 15,

Hello all. Apologies... I was a little too eager in my earlier annoucement about the Indexed Search Engine for Rails apps. The DB migration file contained an error that had to be worked around. I''ve fixed that, added more (and clearer) documentation, and a sample application. You can find most everything you want to know about Indexed Search Engine here:

> On 15/08/2019 00:34 Eugene via dovecot <dovecot at dovecot.org> wrote: > > > The next combination of parameters makes 100% LDAP connections unsuccessful (the log snippet form the previous mail). > sasl_bind = yes > sasl_mech = gssapi > tls = yes > > Looks like this combination is utterly incorrect and should be prohibited (tls must not be used when mech is

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

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

http://dovecot.org/test/ Should work again with maildir. - Some bugfixes to indexes (possibly fixing the still persisting maildir sync errrors?) - Enabled cache file again. If client asks about something that can be cached for future, it's done. There's currently no smart logic about when not to do it or when to cache more than was asked for future use. Currently nothing is ever

So, to follow up to my previous thread, we just successfully migrated our NFS-based mail cluster from qmail pop, courier imap, and bincimap to dovecot 1.1rc1. Overall the transition was very smooth, the only unexpected adjustment was having to implement ntpd on each box, rather than doing an hourly ntpdate against our local ntpd server, to prevent dovecot from crashing itself from too much

Hi, When Jason Goecke talks, VoIP ideas become reality, and this makes my day. On this call we?ll talk about the newest features in Tropo and how to get started with telephony apps in the cloud without adding new infrastructure. Here's a chance to speak directly to Jason (or JSON as we now call him) to ask your questions about VoIP cloud apps. Tropo is a cloud communications platform that to

Hourly I have an rsync job backup /home to /home/backup. I have 24 directories (one for each hour): home.0 ... home.23 Here is the script I am running via cron: #! /usr/local/bin/bash dest=`date +%k | sed 's/ //g'` linkdir=`date -v-1H +%k | sed 's/ //g'` chflags -R noschg /home/backup rm -rf /home/backup/home.$dest rsync -ahHP --numeric-ids --delete --stats --link-dest=../

Hi all I discovered that the full-text search (fts) plugin can work without SQUAT/LUCENE/SOLR backend. I.e., Dovecot creates separate indexes for header search in files dovecot.index and dovecot.index.cache. Even, the search by headers is fast enough, and can search for phrases. Also, it seems that this buillt-in search is faster than Solr-based search. But if I enable the Solr backend (fts_solr),

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

Hello I have a question about live migration when libvirt requires sasl authentication. I have managed to configure remote access for user nova with sasl enabled (credentials stored in auth.conf - https://review.openstack.org/#/c/12706/). It looks like live migration do not use these credentials at all. What is more it thinks that sasl is not not configured: 2013-07-01 09:49:09.317+0000: 17997:

I am using dovecot and trying to make it compatible with my a BincIMAP installation. BincIMAP uses a scheme similar to Courier-IMAP, so I set up this default_mail_env: default_mail_env = maildir:~/Maildir And this namespace: namespace private { separator = . prefix = INBOX. inbox = yes } Which mostly works as expected, but I now see an "INBOX" subfolder of "INBOX" in