search for: grosjo

...uery. If it's not set, then Dovecot core doesn't think that the arg was part of the FTS search and it processes it itself. Meaning that it opens all the emails and does the search the slow way, practically making the FTS lookup ignored. > On 21 Apr 2019, at 19.50, Joan Moreau <jom at grosjo.net> wrote: > > No, the parsing is made by dovecot core, that is nothing the backend can do about it. The backend shall *never* reveive this. (would it be buggy or no) > > > > PLease, have a look deeper > > And the loop is a very big problem as it times out all the...

Inbox appears in the list of arguments, because fts_backend_xapian_lookup() is parsing the search args wrong. Not sure about the other issue. > On 21 Apr 2019, at 19.31, Joan Moreau <jom at grosjo.net> wrote: > > For this first point, the problem is that dovecot core sends TWICE the request and "Inbox" appears in the list of arguments ! (inbox shall serve to select teh right mailbox, never sent to the backend) > > And even if this would be solved, the dovecot core...

On 3 Apr 2019, at 20.30, Joan Moreau via dovecot <dovecot at dovecot.org> wrote: > doveadm search -u jom at grosjo.net mailbox inbox text milan > output > > doveadm(jom at grosjo.net): Info: Query : ( bcc:inbox OR body:inbox OR cc:inbox OR from:inbox OR message-id:inbox OR subject:inbox OR to:inbox OR uid:inbox ) AND ( bcc:milan OR body:milan OR cc:milan OR from:milan OR message-id:milan OR subject:mi...

...t in any of the backend functions) On 2019-04-21 10:42, Timo Sirainen via dovecot wrote: > Inbox appears in the list of arguments, because fts_backend_xapian_lookup() is parsing the search args wrong. Not sure about the other issue. > > On 21 Apr 2019, at 19.31, Joan Moreau <jom at grosjo.net> wrote: > > For this first point, the problem is that dovecot core sends TWICE the request and "Inbox" appears in the list of arguments ! (inbox shall serve to select teh right mailbox, never sent to the backend) > > And even if this would be solved, the dovecot cor...

...vecot core sends TWICE the request and "Inbox" appears in the list of arguments ! (inbox shall serve to select teh right mailbox, never sent to the backend) And even if this would be solved, the dovecot core loops *after* the backend hs returneds the results # doveadm search -u jom at grosjo.net mailbox inbox text milan doveadm(jom at grosjo.net): Info: Get last UID of INBOX = 315526 doveadm(jom at grosjo.net): Info: Get last UID of INBOX = 315526 doveadm(jom at grosjo.net): Info: Query: FLAG=AND doveadm(jom at grosjo.net): Info: Query(1): add term(wilcard) : inbox doveadm(jom at grosj...

...and the plugin shall purge the redundant UID (i..e UID present in the index but not in the list sent by dovecot) and send back the list of UID not in its indexes to dovecot, so Dovect can send one by one the missing emails WHat do you think ? -------- Original Message -------- SUBJECT: [grosjo/fts-xapian] `doveadm fts rescan` removes all indices (#15) DATE: 2019-02-08 08:28 FROM: Leonard Lausen <notifications at github.com> TO: grosjo/fts-xapian <fts-xapian at noreply.github.com> CC: Subscribed <subscribed at noreply.github.com> REPLY-TO:...

...If it's not set, then Dovecot core doesn't think that the arg was part of the FTS search and it processes it itself. Meaning that it opens all the emails and does the search the slow way, practically making the FTS lookup ignored. > > On 21 Apr 2019, at 19.50, Joan Moreau <jom at grosjo.net> wrote: > > No, the parsing is made by dovecot core, that is nothing the backend can do about it. The backend shall *never* reveive this. (would it be buggy or no) > > PLease, have a look deeper > > And the loop is a very big problem as it times out all the time (and...

Duh... src/lib/restrict-process-size.h Should be in the installed include files as well, /usr/include/dovecot/restrict-process-size.h Aki > On 06/11/2020 15:56 Joan Moreau <jom at grosjo.net> wrote: > > > Hello > I can't find "src/lib/restrict.h" . Is it in dovecot source ? > > > On 2020-11-06 13:20, Aki Tuomi wrote: > > Seems I had forgotten that you can use src/lib/restrict.h, in particular, restrict_get_process_size() to figure out...

...e redundant UID (i..e UID present in the index but not in the list sent by dovecot) and send back the list of UID not in its indexes to dovecot, so Dovect can send one by one the missing emails > > WHat do you think ? > > -------- Original Message -------- > > SUBJECT: > [grosjo/fts-xapian] `doveadm fts rescan` removes all indices (#15) > > DATE: > 2019-02-08 08:28 > > FROM: > Leonard Lausen <notifications at github.com> > > TO: > grosjo/fts-xapian <fts-xapian at noreply.github.com> > > CC: > Subscribed <subscribed at...

<!doctype html> <html> <head> <meta charset="UTF-8"> </head> <body> <div> Did you remember to load fts first? </div> <div> <br> </div> <div> mail_plugins =$mail_plugins fts fts_xapian </div> <div> <br> </div> <div> Aki </div>

On 7 Jan 2019, at 16.05, Joan Moreau via dovecot <dovecot at dovecot.org> wrote: > > Hi > > ANyone to answer specifically ? > > Q1 : get_last_uid -> Is this the last UID indexed (which may be not the greatest value), or the gratest value (which may not be the latest) (the code of existing plugins is unclear about this, Solr looks for the greatest for insance) All the

You could also add it as setting for the fts_xapian plugin parameters? Aki > On 04/11/2020 08:42 Joan Moreau <jom at grosjo.net> wrote: > > > For machines with low memory, I would like to detect how much ram remains available before starting indexing a mail, so I can commit everything on disk before the ram is exhausted (and break the process) > I tried to put a "fake" allocation to test if it...

...n the index but not in the list sent by dovecot) and send back the list of UID not in its indexes to dovecot, so Dovect can send one by one the missing emails > > > > WHat do you think ? > > > > -------- Original Message -------- > > > > SUBJECT: > > [grosjo/fts-xapian] `doveadm fts rescan` removes all indices (#15) > > > > DATE: > > 2019-02-08 08:28 > > > > FROM: > > Leonard Lausen <notifications at github.com> > > > > TO: > > grosjo/fts-xapian <fts-xapian at noreply.github.com> >...

...ecot.org <mailto:dovecot at dovecot.org>> wrote: > > Can you send the log part that includes the "init" of the plugins (something similar as below) ? > > WHich version of Xapian are you on ? > > Jan 14 09:10:04 gjserver dovecot[31082]: indexer-worker(admin at grosjo.net <mailto:admin at grosjo.net>)<14725><apZfHexRPFy9QAAA0thIag:UL+TNOxRPFyFOQAA0thIag>: FTS Xapian: Partial=2, Full=20 DB_PATH=/data/mail/grosjo.net/admin/xapian-indexes <http://grosjo.net/admin/xapian-indexes> > Jan 14 09:10:04 gjserver dovecot[31082]: indexer-worker(ad...

.../dovecot.service.d/coredump.conf to no avail). Custom Dovecot 2.3.4 on Debian Stretch. Thanks, Paul > On 14. Jan 2019, at 07:42, Joan Moreau via dovecot <dovecot at dovecot.org> wrote: > > Thank you Stephan. > > The version here shall be up and running : https://github.com/grosjo/fts-xapian > > > > > > > On 2019-01-14 00:07, Stephan Bosch wrote: > >> >> >> Op 13/01/2019 om 21:25 schreef Joan Moreau via dovecot: >>> >>> I tried to combined it, the "autoreconf" errors are solved >>> &gt...

...019 om 13:40 schreef Aki Tuomi: > > Just to remind that now that there is a github repo for fts-xapian, > you could maybe open these issues there instead? > Although README.md currently says: "Please feel free to send your questions, together with the dovecot log file, to jom at grosjo.net <mailto:jom at grosjo.net> or to the dovecot ML dovecot at dovecot.org <mailto:dovecot at dovecot.org>." Regards, Stephan. > Aki > > On 14.1.2019 14.29, Odhiambo Washington wrote: >> Testing a compile on FreeBSD. >> >> gmake[2]: Entering directo...

The change of "Extern C" suggested by Timo actually solved the situation Now, further question : I put a "i_warning" at each of my functions, and I see in the log : Jan 12 10:33:27 indexer-worker(jom at grosjo.net)<30970><ms9zEnfCOVyHegAA0thIag:8IhwIHfCOVz6eAAA0thIag>: Warning: fts_backend_xapian_alloc Jan 12 10:33:27 indexer-worker(jom at grosjo.net)<30970><ms9zEnfCOVyHegAA0thIag:8IhwIHfCOVz6eAAA0thIag>: Warning: fts_backend_xapian_init Jan 12 10:33:27 indexer-worker(jom at grosj...

Seems I had forgotten that you can use src/lib/restrict.h, in particular, restrict_get_process_size() to figure out the limit. You can combine this with getrusage to find out current usage. Aki > On 06/11/2020 13:26 Joan Moreau <jom at grosjo.net> wrote: > > > yes, will do so. > It would be nice however to be able to access the actual dovecot config from the plugin side > > > > On 2020-11-04 06:46, Aki Tuomi wrote: > > You could also add it as setting for the fts_xapian plugin parameters? > >...

On 2 Apr 2019, at 6.38, Joan Moreau via dovecot <dovecot at dovecot.org> wrote: > > Further on this topic: > > > > When choosing any headers in the search box, dovecot core calls the plugin TWICE (and returns the results quickly, but not immediatly after getting the IDs from the plugins) > > When choosing the BODY search, dovecot core calls the plugin ONCE (and

Please kindly check https://github.com/grosjo/fts-xapian On 2019-01-13 20:11, Aki Tuomi wrote: > If you had looked at what I sent, you'd seen it's quite different from what you sent. > > Anyways, put the contents of skeleton.tar.gz and > > ./src/plugins/fts-xapian/fts-xapian-plugin.h > ./src/plugins/fts-xapian/f...