search for: rawlog_dir

...)?{ >> ????????????i_error("fts_solr:?received?invalid?uid?'%s'",?t_strndup(str,?len)); >> It means that plugin tries to parse '0' when in state of parsing uid >> in xml response from solr or there is a bug in xml response parser. >> I would enable rawlog_dir in config and look there for unusual >> response or extra tags near usual uid in xml response. For example: >> |plugin { fts = solr fts_solr = url=... rawlog_dir=/var/log/fts-solr/ }| >> > > Thanks for this tip!?The rawlog_dir option is not yet supported in our > versio...

...received invalid uid '%s'", t_strndup(str, len)); > > >>> > >>> It means that plugin tries to parse '0' when in state of parsing uid > >>> in xml response from solr or there is a bug in xml response parser. > >>> I would enable rawlog_dir in config and look there for unusual > >>> response or extra tags near usual uid in xml response. For example: > >>> |plugin { fts = solr fts_solr = url=... > >>> rawlog_dir=/var/log/fts-solr/ }| > >>> > >> > >> Thanks for this tip!...

...364f93e2cd1b716b9ab61bd39656a6c5b1ea04 100644 --- a/src/plugins/fts-solr/solr-connection.c +++ b/src/plugins/fts-solr/solr-connection.c @@ -103,7 +103,7 @@ int solr_connection_init(const struct fts_solr_settings *solr_set, http_set.ssl = ssl_client_set; http_set.debug = solr_set->debug; http_set.rawlog_dir = solr_set->rawlog_dir; -solr_http_client = http_client_init(&http_set); +solr_http_client = http_client_init_private(&http_set); } *conn_r = conn; diff --git a/src/plugins/fts/fts-parser-tika.c b/src/plugins/fts/fts-parser-tika.c index a4b8b5c3034f57e22e77caa759c090da6b62f8ba..b8b57a35...

...gt; > > >>> > > >>> It means that plugin tries to parse '0' when in state of > > parsing uid > > >>> in xml response from solr or there is a bug in xml response > > parser. > > >>> I would enable rawlog_dir in config and look there for unusual > > >>> response or extra tags near usual uid in xml response. For > > example: > > >>> |plugin { fts = solr fts_solr = url=... > > >>> rawlog_dir=/var/log/fts-solr/ }| > > >>>...

...us sends for these folders that have special characters. > We have been able to work around some of the broken mUTF7 implementations with some BROKENCHAR magic. > > Sami Hi Sami, Thanks for your support. I have tried the following... Added this to conf.d/20-imap.conf: protocol imap { rawlog_dir = /tmp/rawlog/%u } Then restarted Dovecot, and re-run the following dsync migration: $ doveadm -o mail_fsync=never backup -R -u <username> imapc: dsync(<username>): Info: imapc(imap.example.com:993): Connected to x.x.x.x:993 (local y.y.y.y:45726) dsync(<username>): Error: Failed...

...16 drwx------ 4 kaka kaka 4096 Dec 12 15:36 . drwxr-xr-x 12 root root 4096 Dec 12 12:41 .. drwx------ 2 kaka kaka 4096 Dec 12 12:41 dovecot.rawlog drwx------ 2 kaka kaka 4096 Dec 12 12:41 Maildir Added into dovecot.conf: protocol imap { rawlog_dir = /tmp/rawlog/%u } service imap { executable = imap postlogin } service postlogin { executable = script-login -d rawlog unix_listener postlogin { } } But /tmp/rawlog/kaka/ and /home/kaka/dovecot.rawlog/ are empty. What did I miss? The whole conf: listen = * plugin { mail_log_events =...

...644 > --- a/src/plugins/fts-solr/solr-connection.c > +++ b/src/plugins/fts-solr/solr-connection.c > @@ -103,7 +103,7 @@ int solr_connection_init(const struct fts_solr_settings *solr_set, > http_set.ssl = ssl_client_set; > http_set.debug = solr_set->debug; > http_set.rawlog_dir = solr_set->rawlog_dir; > - solr_http_client = http_client_init(&http_set); > + solr_http_client = http_client_init_private(&http_set); > } > > *conn_r = conn; > diff --git a/src/plugins/fts/fts-parser-tika.c b/src/plugins/fts/fts-parser-tika.c > index a4b8b5...

...gt; 100644 > --- a/src/plugins/fts-solr/solr-connection.c > +++ b/src/plugins/fts-solr/solr-connection.c > @@ -103,7 +103,7 @@ int solr_connection_init(const struct > fts_solr_settings *solr_set, > http_set.ssl = ssl_client_set; > http_set.debug = solr_set->debug; > http_set.rawlog_dir = solr_set->rawlog_dir; > -solr_http_client = http_client_init(&http_set); > +solr_http_client = http_client_init_private(&http_set); > } > > *conn_r = conn; > diff --git a/src/plugins/fts/fts-parser-tika.c > b/src/plugins/fts/fts-parser-tika.c > index > a4b8b...

...0 || ctx->uid == 0) { > i_error("fts_solr: received invalid uid '%s'", t_strndup(str, len)); > It means that plugin tries to parse '0' when in state of parsing uid in xml response from solr or there is a bug in xml response parser. > I would enable rawlog_dir in config and look there for unusual response or extra tags near usual uid in xml response. For example: > plugin { > fts = solr > fts_solr = url=... rawlog_dir=/var/log/fts-solr/ > } > Thanks for this tip! The rawlog_dir option is not yet supported in our version 2.3.4. What w...

..._error("fts_solr:?received?invalid?uid?'%s'",?t_strndup(str,?len)); >>> >>> It means that plugin tries to parse '0' when in state of parsing uid >>> in xml response from solr or there is a bug in xml response parser. >>> I would enable rawlog_dir in config and look there for unusual >>> response or extra tags near usual uid in xml response. For example: >>> |plugin { fts = solr fts_solr = url=... >>> rawlog_dir=/var/log/fts-solr/ }| >>> >> >> Thanks for this tip!?The rawlog_dir option is not...

Aki Tuomi wrote: > > Can you do > > doveconf -a | grep auth_mech > auth_mechanisms = plain login P.S. Seems this 2.2.24 is the last win10 compatible version (as my testserver doesn't have win10 users and thunderbird works well), any never version gives an error. However I didn't find any hint from http://www.dovecot.org/list/dovecot-news/2016-July/000324.html etc. --

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

...quot;,?t_strndup(str,?len)); > > >>> > >>> It means that plugin tries to parse '0' when in state of > parsing uid > >>> in xml response from solr or there is a bug in xml response > parser. > >>> I would enable rawlog_dir in config and look there for unusual > >>> response or extra tags near usual uid in xml response. For > example: > >>> |plugin { fts = solr fts_solr = url=... > >>> rawlog_dir=/var/log/fts-solr/ }| > >>> > >> >...

...rob? >> > (1) I can't, I'm still on an earlier version I'll look for the 8.6.3, rather than 'current' (8.7.0) bins, spin up an instance, and do some dubl-checking > (2) see here: https://wiki.dovecot.org/Plugins/FTS/Solr > > two useful settings are debug and rawlog_dir=whatever to be added in the same line as fts_solr ah, thx! > (3) strange you don't see anything on the solr server. Something is giving a 401 response so if it's not solr what is it? head-scratcher, atm. the logging^ should help. > Are you now using apache in front of solr? nope...

...2017 um 01:04 schrieb Matt Bryant: > > Hi, > > > > Trying to get rawlog working on dovecot 2.2.31 configured as per > > > > https://wiki2.dovecot.org/Debugging/Rawlog > > > > but > > > > a) it doesnt appear to be loggin anything > > b) rawlog_dir which is supposed to be v2.2.26+ seems no where in site .. > > in fact complains about unknown variable > > > > So does rawlog still do anything ???? Or am I missing something ... > > config is below .... > > > > > > # 2.2.19: /etc/dovecot/dovecot.conf &...

...644 > --- a/src/plugins/fts-solr/solr-connection.c > +++ b/src/plugins/fts-solr/solr-connection.c > @@ -103,7 +103,7 @@ int solr_connection_init(const struct fts_solr_settings *solr_set, > http_set.ssl = ssl_client_set; > http_set.debug = solr_set->debug; > http_set.rawlog_dir = solr_set->rawlog_dir; > - solr_http_client = http_client_init(&http_set); > + solr_http_client = http_client_init_private(&http_set); > } > > *conn_r = conn; > diff --git a/src/plugins/fts/fts-parser-tika.c b/src/plugins/fts/fts-parser-tika.c > index a4b8b5...

Hi, Trying to get rawlog working on dovecot 2.2.31 configured as per https://wiki2.dovecot.org/Debugging/Rawlog but a) it doesnt appear to be loggin anything b) rawlog_dir which is supposed to be v2.2.26+ seems no where in site .. in fact complains about unknown variable So does rawlog still do anything ???? Or am I missing something ... config is below .... # 2.2.19: /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.9 (357ac0a0e68b+) doveconf: Warning: service a...

...-connection.c >> +++ b/src/plugins/fts-solr/solr-connection.c >> @@ -103,7 +103,7 @@ int solr_connection_init(const struct fts_solr_settings *solr_set, >> http_set.ssl = ssl_client_set; >> http_set.debug = solr_set->debug; >> http_set.rawlog_dir = solr_set->rawlog_dir; >> - solr_http_client = http_client_init(&http_set); >> + solr_http_client = http_client_init_private(&http_set); >> } >> *conn_r = conn; >> diff --git a/src/plugins/fts/fts-parser-tika.c b/src/plugins/fts/...

Matt Bryant wrote: > a) it doesnt appear to be loggin anything > b) rawlog_dir which is supposed to be v2.2.26+ seems no where in site .. > in fact complains about unknown variable > ... > service postlogin { > executable = script-login -d rawlog > unix_listener postlogin { > group = atmail > mode = 0660 > } > } In my test setup, I use the...

> On 28 Sep 2019, at 12.52, Philip Iezzi via dovecot <dovecot at dovecot.org> wrote: >> >> Hi Sami, >> >> Thanks for your support. I have tried the following... >> Added this to conf.d/20-imap.conf: >> >> protocol imap { >> rawlog_dir = /tmp/rawlog/%u >> } just add setting imapc_rawlog_dir=/path/to/%u and make sure the directory exists and is writable. Sami