similar to: removing 'use_libfts' from dovecot fts_solr config; docs/examples of solr-backend-only tokenizer config for dovecot?

On 11/1/20 10:35 AM, John Fawcett wrote: > Yes, getting more data about any potential problem would be useful. > > Just to clarify: I have a fully working search setup for some time now > over various dovecot releases, so no patches needed to get it working. > > My setup does use fts plugin and fts-solr plugin, but it does not use > lib-fts functionality (that has many

sending to the list as well On 02/11/2020 17:40, PGNet Dev wrote: > On 11/1/20 10:35 AM, John Fawcett wrote: >> Yes, getting more data about any potential problem would be useful. >> >> Just to clarify: I have a fully working search setup for some time now >> over various dovecot releases, so no patches needed to get it working. >> >> My setup does use fts

> 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

> On 19/10/2020 02:49 PGNet Dev <pgnet.dev at gmail.com> wrote: > > > I've since rebuilt/reconfig'd all parts of my setup from scratch; some good cleanup along the way. > > Atm, my entire system for send/recv, store/retrieve, + rules & search is working as I intend. Ok, mostly ... > > Except for this accented-character search mystery. I've got a

Hi all! We are pleased to release v2.3.18 of Dovecot. Debian/Stretch support has now been dropped. CentOS 8 packages have been replaced with RedHat Enterprise Linux 8 packages. These should be compatible with all the various variants. https://dovecot.org/releases/2.3/dovecot-2.3.18.tar.gz https://dovecot.org/releases/2.3/dovecot-2.3.18.tar.gz.sig Binary packages in https://repo.dovecot.org/

Hi all! We are pleased to release v2.3.18 of Dovecot. Debian/Stretch support has now been dropped. CentOS 8 packages have been replaced with RedHat Enterprise Linux 8 packages. These should be compatible with all the various variants. https://dovecot.org/releases/2.3/dovecot-2.3.18.tar.gz https://dovecot.org/releases/2.3/dovecot-2.3.18.tar.gz.sig Binary packages in https://repo.dovecot.org/

On 10/18/20 10:28 PM, Aki Tuomi wrote: > Dovecot FTS tokenization is not done, unless you have `use_libfts` in fts_solr setting, in your case > > fts_solr = url=https://solr.example.com:8984/solr/dovecot/ use_libfts changing - fts_solr = url=https://solr.example.com:8984/solr/dovecot/ soft_commit=yes batch_size=250 + fts_solr = url=https://solr.example.com:8984/solr/dovecot/ use_libfts

On 19/10/2020 16:20, PGNet Dev wrote: > On 10/18/20 10:28 PM, Aki Tuomi wrote: >> Dovecot FTS tokenization is not done, unless you have `use_libfts` in >> fts_solr setting, in your case >> >> fts_solr = url=https://solr.example.com:8984/solr/dovecot/ use_libfts > > changing > > -??? fts_solr = url=https://solr.example.com:8984/solr/dovecot/ >

On 11/1/20 1:56 AM, John Fawcett wrote: > At the moment I don't see other corrections needed in dovecot apart from > command line doveadm fts which is not a show stopper. Via doveadm search > I confirm - on my simple config - that search for accented or non > accented characters works correctly as it does via imap connection. thx. hopefully it'll get considered for a next

However, Solr crashes and Dovecot plugin ftS_solr returns multitude of errors Dec 09 09:21:09 imap(jom at grosjo.net)<3349><DiRnXpN8Lux/AAAB>: Error: fts_solr: received invalid uid '0' Dec 09 09:21:10 imap(jom at grosjo.net)<3349><DiRnXpN8Lux/AAAB>: Error: fts_solr: received invalid uid '0' And returns are totaly funny (keywords not presentin teh

After some testsing, I managed to get proper functionning - The schema.xml is attached below (quite different from the one provided on teh wiki) (in bold the core differences) (NGramFilterFactory is the class that replace the fts_squat "partial=3 full=15", everything else is just a big hammer to smash a tiny fly) - One need to remove the "managed-schema" file in the

> On 01/11/2020 20:35 John Fawcett <john at voipsupport.it> wrote: > > > On 01/11/2020 15:20, PGNet Dev wrote: > > On 11/1/20 1:56 AM, John Fawcett wrote: > >> At the moment I don't see other corrections needed in dovecot apart from > >> command line doveadm fts which is not a show stopper. Via doveadm search > >> I confirm - on my simple

Hi Daniel, THere is no need of all this, just the command (on Solr 7.5) "create -c dovecot " is enough The chema.xml provided on the wiki basically does not work on 7.5 Here the latest one I am working on , but nothing works properly (bad search results, errors in ftp_solr, etc..) <?xml version="1.0" encoding="UTF-8"?> <schema name="dovecot"

On 13/11/2020 21:32, PGNet Dev wrote: > On 11/13/20 11:37 AM, John Fawcett wrote: >>> still dunno why the 401. :-/ >> >> So I just did a quick check of running dovecot with a standalone >> solr-8.7.0 instance and I'm not seeing any issues. > > +1 > >> I confirm I haven't configured anything for indexer or indexer-worker in >> dovecot, just

I've been running Solr for a while (4.10.3) - wanted to make the jump to the latest & greatest. I installed 6.4.1, copied over my schema.xml - and after a couple false starts where I needed to tweak it work with the new version...it works! I did not copy the database, started from scratch, and executed a "doveadm fts rescan -A". But... Judging solely from at least one

I shared the errors already so many times (check this mailinling for "solr" in teh title) Contrary to what you say, with SOlr 7.5 and Dovecot git, I had to remove the "managed-schema" to make solr respond a bit properly. It relies on schema.xml In order to create the instance, no, it copies the default config in the dovecot instance. Bottom line, the end results is that

Joan, I understand and sympathize with your frustration - trying to get multiple applications to work together, particularly given the lack of documentation for some of them, can be extremely challenging.? That said, I suggest you consider an alternative viewpoint.? Frequently being misunderstood myself I apologize in advance if I'm reading you wrong - but it appears your view towards

The one on the Wiki is mine...which I'm using now.? So it certainly does work - but perhaps there's a setting you have differently from me. Performing a "create -c dovecot" creates a Solr instance *named* dovecot - that does *not* initialize it with the necessary schema.? You need to specify "-d dovecot", with a dovecot configset already setup, to do that. The

Additionally, here the errors I get in logs: Dovecot: Dec 09 09:21:09 imap(jom at grosjo.net)<3349><DiRnXpN8Lux/AAAB>: Error: fts_solr: received invalid uid '0' Dec 09 09:21:10 imap(jom at grosjo.net)<3349><DiRnXpN8Lux/AAAB>: Error: fts_solr: received invalid uid '0' or 11 03:36:03 indexer-worker(jom at

On 13/11/2020 22:04, PGNet Dev wrote: >> I guess you didn't need to enclose username and password in quotes, i.e. >> >> fts_solr = >> url=https://myuser:my%40pass at solr.example.com:8984/solr/dovecot/ >> use_libfts soft_commit=yes batch_size=250 > > On 11/13/20 12:56 PM, John Fawcett wrote: > >> I guess you didn't need to enclose username and