search for: mail_search_args

...* *** 5,18 **** #include "mail-search-build.h" #include "imap-expunge.h" ! int imap_expunge(struct mailbox *box, struct mail_search_arg *next_search_arg) { struct mail_search_context *ctx; struct mailbox_transaction_context *t; struct mail *mail; struct mail_search_args *search_args; bool expunges = FALSE; if (mailbox_is_readonly(box)) { /* silently ignore */ return 0; --- 5,21 ---- #include "mail-search-build.h" #include "imap-expunge.h" ! int imap_expunge(struct client *client, struct mail_search_arg *next_search_arg) {...

I am looking through the logging options and wondering if there are a couple of things that we can do 1. Logouts don't seem to show the IP address of the logout, we typically see multiple sessions at a time and wondering if there is a way to tie the logouts to an IP 2. POP logouts show the number of messages retrieved/deleted but I don't see a way to do this with IMAP, is there a logout

...sqlite=auto --with-solr=auto --with-xapian=auto --with-gssapi=auto --with-libwrap=auto; \ rm -rf scan-reports; \ scan-build -o scan-reports make 2>&1 || exit 1; \ if ! rmdir scan-reports 2>/dev/null; then \ WHAT ABOUT THE OTHER QUESTIONS ? 1 - WHat does represent "subargs" in mail_search_args 2 - for rescan : who is responsible for passing again the new email ? Is the Dovecot core sending again all the emails to index ? or the fts shall somehow access the mailbox and read all emails ? Wouldn't just be saying "delete all index and get_last_uid is now 0" the easy way ?...

Also, 1 - WHat does represent "subargs" in mail_search_args 2 - I made my first code, and the error I get compiling within the dovecot architecture is "In file included from fts-xapian-plugin.c:4: fts-xapian-plugin.h:6:1: error: unknown type name 'using'; did you mean 'uint'? using namespace std;" if I remove this, the Xapian...

...<div> I figured out the "namespace" issue </div> <div> <br> </div> <div> Remaining questions are : </div> <div> <br> </div> <div> 1 - WHat does represent "subargs" in mail_search_args </div> <div> <br> </div> <div> 2 - for rescan : who is responsible for passing again the new email ? Is </div> <div> the Dovecot core sending again all the emails to index ? or the fts </div> <div> shall s...

Implements more verbose imap logging (when client exits). Similar to existing logging in POP3. Due to the nature of imap and my incomplete understanding (of the dovecot code) the session statistics reported have varying accuracy. Much better than nothing IMO. Cheers, Jens ----------------------------------------------------------------------- 'This mail automatically becomes portable

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

...ror: conflicting declaration of 'ssize_t i_my_pwrite(int, const void*, size_t, __off_t)' with 'C' linkage # define pwrite i_my_pwrite Any help welcome Hi, I figured out the "namespace" issue Remaining questions are : 1 - WHat does represent "subargs" in mail_search_args 2 - for rescan : who is responsible for passing again the new email ? Is the Dovecot core sending again all the emails to index ? or the fts shall somehow access the mailbox and read all emails ? Wouldn't just be saying "delete all index and get_last_uid is now 0" the easy way ? or...

...39; >> linkage >> # define pwrite i_my_pwrite >> >> Any help welcome >> >> Hi, >> >> I figured out the "namespace" issue >> >> Remaining questions are : >> >> 1 - WHat does represent "subargs" in mail_search_args >> >> 2 - for rescan : who is responsible for passing again the new email ? Is >> the Dovecot core sending again all the emails to index ? or the fts >> shall somehow access the mailbox and read all emails ? Wouldn't just be >> saying "delete all index an...

...<br> </div> <div> Your help very welcome </div> <div> <br> </div> <div> PENDING QUESTIONS </div> <div> <br> </div> <div> 1 - WHat does represent "subargs" in mail_search_args </div> <div> <br> </div> <div> 2 - for rescan : who is responsible for passing again the new email ? Is </div> <div> <br> </div> <div> the Dovecot core sending again all the emails to index ? or the...

...gt; >> + #ifdef __cplusplus >> + extern "C" { >> + #endif > > You should put this extern "C" into the C++ file you're creating. See for example how fts-lucene/lucene-wrapper.cc does this. > >> 1 - WHat does represent "subargs" in mail_search_args > > It's set only for SEARCH_OR and SEARCH_SUB. So for example: > > SEARCH TEXT foo TEXT bar TEXT baz > > results in: > > type=SEARCH_SUB > value.subargs = ( > { type=SEARCH, value.str="foo" }, > { type=SEARCH, value.str="bar" }, > { t...

Hi all, ive seen a few segfaults in RC15. It's hard for me to reproduce but I was able to get a core when it happened with one of our customers. RC15 FreeBSD 4.10 X86 NFS/NetApp It's squirrelmail/webmail client. Can't reproduce it, cant turn on dovecot.rawlog because I dont know in advance which customer will hit this. See it about 5 times per hour, with thousands of logins per hour.

and finally , for fts_backend_xxxx_lookup_multi, why is that backend dependent ? Would- nt the below function below be the same for any backend ? Waiting fro your feedback on all those questions Thank you JM ----------------- static int fts_backend_xapian_lookup_multi(struct fts_backend *_backend, struct mailbox *const boxes[], struct mail_search_arg *args, enum fts_lookup_flags flags,

...e_full_value = 0} ret = 0 #16 0x080b537a in search_arg_foreach (arg=0x90ef6c0, callback=0x80abe09 <search_header_arg>, context=0xbfe92f80) at mail-search.c:85 subarg = (struct mail_search_arg *) 0x0 __PRETTY_FUNCTION__ = "search_arg_foreach" #17 0x080b53a4 in mail_search_args_foreach (args=0x90ef6c0, callback=0x80abe09 <search_header_arg>, context=0xbfe92f80) at mail-search.c:98 result = 1 #18 0x080ac2f7 in search_header (hdr=0x90fec80, ctx=0xbfe92f80) at index-search.c:491 No locals. #19 0x080ed97e in message_parse_header (input=0x90fa8f8, hdr_size=0x0, f...

Ok. Additional question : - for rescan : who is responsible for passing again the new email ? Is the Dovecot core sending again all the emails to index ? or the fts shall somehow access the mailbox and read all emails ? Wouldn't just be saying "delete all index and get_last_uid is now 0" the easy way ? or the fts must process all emails (and block the current thread as a mailbx

...); > #endif > > + #ifdef __cplusplus > + extern "C" { > + #endif > > You should put this extern "C" into the C++ file you're creating. See for example how fts-lucene/lucene-wrapper.cc does this. > > 1 - WHat does represent "subargs" in mail_search_args > It's set only for SEARCH_OR and SEARCH_SUB. So for example: > > SEARCH TEXT foo TEXT bar TEXT baz > > results in: > > type=SEARCH_SUB > value.subargs = ( > { type=SEARCH, value.str="foo" }, > { type=SEARCH, value.str="bar" }, > { type=S...

...lib/dovecot/lib21_fts_xapian_plugin.so (...) lib20_fts_plugin.so => /usr/lib/dovecot/lib20_fts_plugin.so (0x00007f25f75e0000) (...) libxapian.so.30 => /usr/lib/libxapian.so.30 (0x00007fe3a51e2000) Your help very welcome PENDING QUESTIONS 1 - WHat does represent "subargs" in mail_search_args 2 - for rescan : who is responsible for passing again the new email ? Is the Dovecot core sending again all the emails to index ? or the fts shall somehow access the mailbox and read all emails ? Wouldn't just be saying "delete all index and get_last_uid is now 0" the easy way ?...

...t iov_len); > #endif > > + #ifdef __cplusplus > + extern "C" { > + #endif > You should put this extern "C" into the C++ file you're creating. See for example how fts-lucene/lucene-wrapper.cc does this. > 1 - WHat does represent "subargs" in mail_search_args It's set only for SEARCH_OR and SEARCH_SUB. So for example: SEARCH TEXT foo TEXT bar TEXT baz results in: type=SEARCH_SUB value.subargs = ( { type=SEARCH, value.str="foo" }, { type=SEARCH, value.str="bar" }, { type=SEARCH, value.str="baz" }, ) Or similar...

...ovecot/lib20_fts_plugin.so >> (0x00007f25f75e0000) >> (...) >> libxapian.so.30 => /usr/lib/libxapian.so.30 (0x00007fe3a51e2000) >> >> Your help very welcome >> >> PENDING QUESTIONS >> >> 1 - WHat does represent "subargs" in mail_search_args >> >> 2 - for rescan : who is responsible for passing again the new email ? Is >> >> the Dovecot core sending again all the emails to index ? or the fts >> shall somehow access the mailbox and read all emails ? Wouldn't just be >> saying "delete al...

...); > #endif > > + #ifdef __cplusplus > + extern "C" { > + #endif > > You should put this extern "C" into the C++ file you're creating. See for example how fts-lucene/lucene-wrapper.cc does this. > > 1 - WHat does represent "subargs" in mail_search_args > It's set only for SEARCH_OR and SEARCH_SUB. So for example: > > SEARCH TEXT foo TEXT bar TEXT baz > > results in: > > type=SEARCH_SUB > value.subargs = ( > { type=SEARCH, value.str="foo" }, > { type=SEARCH, value.str="bar" }, > { type=S...