similar to: [PATCH]: libexttextcat from libreoffice

Hello, I am a complete newbie to dovecot, but do have reasonable experience in compiling Unix/Linux software. I am currently trying to do a cross-compile of dovecot-2.29.1 to be used on my home office Thecus NAS (host: Thecus kernel 2.6.33 on 32-bit Intel Atom: "i686-nptl-linux-gnu"; my build machine has Ubuntu 16.04.2 LTS) "from ground up", i.e. I need to build and

This happens on configure, I only ran ./configure. This error is logged to stderr: [root at host1 dovecot]# wget https://dovecot.org/releases/2.2/dovecot-2.2.27.tar.gz [root at host1 dovecot]# tar xzf dovecot-2.2.27.tar.gz [root at host1 dovecot]# cd dovecot-2.2.27 [root at host1 dovecot-2.2.27]# ./configure --with-ldap=yes --with-zlib --with-bzlib --with-solr > foo configure: error:

Hi, I'm testing out 2.1.rc1, building against clucene 2.3.3.4. Without libstemmber, the build fails because it attempts to include SnowballAnalyzer.h which is not part of "core" clucene. Simple patch below to make dovecot 2.1.rc1 build with clucene but without libstemmer (or textcat). Looking at libstemmer itself, there are multiple versions. The version in clucene is put into

Hello, A set of patches was created by Lawrence Chen for the Dovecot2 port so that it could recognise and use libstemmer and libexttextcat. They can't be used as is as he's replacing statements with something that works only on FreeBSD, but I think it would be a good idea to try and include some of his fixes. http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/175813 Cheers, Olivier

Not sure if I mentioned it but I'm on FreeBSD too. I wonder if any of the patches FreeBSD applies automatically is causing this. I looked through them but couldn't find anything obvious that might cause this --- configure.orig? ? ? 2020-08-12 12:20:51 UTC +++ configure @@ -28901,13 +28901,13 @@ fi ? ?if test $want_stemmer != no; then -? ? { $as_echo "$as_me:${as_lineno-$LINENO}:

I don't see it, and can't really think of a good reason why it would happen. This happens in configure? And the first thing you ran was configure, right? No autogen.sh or autoconf/automake? -bash-4.1# cat /etc/redhat-release CentOS release 6.8 (Final) -bash-4.1# uname -a Linux test-centos6.dovecot.net 2.6.32-642.6.1.el6.x86_64 #1 SMP Wed Oct 5 00:36:12 UTC 2016 x86_64 x86_64 x86_64

Hi Dovecot folks, I recently reported this bug in Debian (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939442) after a stretch -> buster upgrade, however since I can reproduce it using the latest 2.4 from git I thought perhaps I ought to take it straight upstream. Here's the text I provided Debian about the issue, and below that I've included a syslog snip showing the same issue

I'm running, dovecot --version 2.3.11.3 (502c39af9) solr -version 8.6.3 uname -rm 5.8.13-200.fc32.x86_64 x86_64 grep _NAME /etc/os-release PRETTY_NAME="Fedora 32 (Server Edition)" CPE_NAME="cpe:/o:fedoraproject:fedora:32" Solr FTS plugin is enabled/configured, mail_plugins = virtual acl fts fts_solr plugin { fts = solr fts_autoindex = yes

> On 02/11/2020 15:11 PGNet Dev <pgnet.dev at gmail.com> wrote: > > > On 11/2/20 12:44 AM, Aki Tuomi wrote: > > you should try removing use_libfts from your config line and let solr do that part. > > sry, i'm a bit confused. > > you'd suggested I _add_ it, > > https://dovecot.org/pipermail/dovecot/2020-October/120258.html > > > I

Mike McCarthy, W1NR <sysop at w1nr.net> ? 2020?11?3? ?? ??7:56??? > > > Can you reproduce the problem with this document? > > > > And, when the crash happened, could you still ping the computer from > > another device in the network? > > > > Crashing hard so that only a reset helps is usually only possible with a > > kernel bug or hardware issue,

Hi, after the upgrade to Dovecot 2.3.11.3, from 2.3.10.1, I see frequently these errors from different users: Aug 18 11:02:35 Panic: indexer-worker(info at domain.com) session=<g71KISOttvS5LNVj:O3ahCyuZO18cYAAAEPCW+w>: file http-client-request.c: line 1232 (http_client_request_send_more): assertion failed: (req->payload_input != NULL) Aug 18 11:02:35 Error: indexer-worker(info at

I was recently asked to upgrade some neolithic aged software (UW-IMAP, sendmail 8.12.x, apache 1.3, amongst other horrors). The box is physically remote, so an aggressive "new flush" wasn't an option. I've been able to upgrade the compiler to gcc-3.4, openssl to 1.0.2k, glibc, php to something in the 5.4-branch, etc. I have CLucene working, even. I know should take a shotgun

FTS indexing is something I hear quite often nowadays. I?ve added some hacks to make it work better for some installations, but it?s about time to think about the whole design and how it could be improved for everyone in future. Here are some of my initial thoughts. Currently Dovecot supports 3 full text search engines: Solr, CLucene and Dovecot Squat. CLucene plugin has various features built

On Sun, 17 May 2015 17:29:54 +0200 Hanns Mattes <hanns at hannsmattes.de> wrote: > 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 I

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

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

On 8/05/2017 11:44 PM, Aki Tuomi wrote: > > > On 2017-05-08 16:23, Reuben Farrelly wrote: >> >> >> On 8/05/2017 9:13 PM, Aki Tuomi wrote: >>> >>> >>> On 2017-05-08 13:52, Reuben Farrelly wrote: >>>> Hi, >>>> >>>> Following up on this as there has been no response and the problem >>>> is still

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 gssapi). https://lists.fedorahosted.org/archives/list/sssd-users at

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, 2019 7:27:20 AM GMT+03:00, Aki Tuomi <aki.tuomi at open-xchange.com> wrote: >> On 15/08/2019 00:34 Eugene via dovecot <dovecot at dovecot.org> wrote: >> >> >> The next combination of

I see nothing suspicious in FreeIPA slapd logs because connection drops before SASL negotiation completion. Network analysis shows client sending RST after receiving `bindResponse(7) saslBindInProgress`. On 8/15/19 3:07 PM, Aki Tuomi via dovecot wrote: > 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