Re: Solr and FTS - assertion failure

On 30/12/2020 16:04, Antonino Esposito wrote: > Hi, > > in the latest weeks i'm working on the Solr integration and > immediately i've faced the assertion failure errors, on 2.0.19, 2.2.9 > and 2.3.11.3 servers in our network. > Reading the thread on debian ML, I realize this issue is related to >

RE: Imap client with ~7500 imap cmds ~250/~500 read() syscall

> >> >metric imap_command { >> > event_name = imap_command_finished >> > filter { >> > user = anomalous >> > } >> > exporter = cmd_export >> >} >> > >> >> Is there also a way to do this on dovecot 2.2? > >With rawlogs, I suppose. > If I get this raw log, I am getting huge amount of lists cut -d ' ' -f2 20201230-181651-16624.out |sort | uniq -c | sort -n .. 17 FLAGS 20 0 328 NO 1284 ) 1284 9021 OK 133350 LIST

Re: import_environment = $import_environment DEBUG=1 where should this be logged?

Hi Marc, The same document says this: rawlog binary It works by checking if dovecot.rawlog/ directory exists in the logged in user's home directory, and writing the traffic to mmdd-HHMMSS-pid.in and .out files. Each connection gets their own in/out files. *Rawlog will simply skip users who

RE: import_environment = $import_environment DEBUG=1 where should this be logged?

You know by any chance how to limit this only for one user? -Original Message- From: Odhiambo Washington [mailto:odhia...@gmail.com] Sent: 30 December 2020 18:00 To: dovecot Subject: Re: import_environment = $import_environment DEBUG=1 where should this be logged? Hi Marc, If you

RE: import_environment = $import_environment DEBUG=1 where should this be logged?

Yes thanks was missing the dovecot.rawlog dir. -Original Message- From: Odhiambo Washington [mailto:odhia...@gmail.com] Sent: 30 December 2020 18:00 To: dovecot Subject: Re: import_environment = $import_environment DEBUG=1 where should this be logged? Hi Marc, If you read the link

Re: import_environment = $import_environment DEBUG=1 where should this be logged?

Hi Marc, If you read the link keenly - Debugging/Rawlog - Dovecot Wiki - you will realize that you need to do some stuff. I have done them and they produced the results. Edit /path/to/dovecot/conf.d/10-master.conf and add the following: Under this bloc

import_environment = $import_environment DEBUG=1 where should this be logged?

You can also set DEBUG environment to have rawlog log an info message why it's not doing anything: import_environment = $import_environment DEBUG=1 Where should this message appear, I also don't have this one. [1] https://wiki2.dovecot.org/Debugging/Rawlog

RE: Getting rawlogging working with dovecot 2.2

Anyone using this with CentOS7 and dovecot-2.2.36-6.el7_8.1.x86_64?

RE: Getting rawlogging working with dovecot 2.2

> >According to this manual[1] I just have to add these lines to my config, >not? > >protocol imap { > rawlog_dir = /tmp/rawlog/%u >} > >I should be seeing something in this /tmp/rawlog if I delete an message >via imap not? I have already made this folder 777 and /tmp/rawlog/test >777, but st

Solr and FTS - assertion failure

Hi, in the latest weeks i'm working on the Solr integration and immediately i've faced the assertion failure errors, on 2.0.19, 2.2.9 and 2.3.11.3 servers in our network. Reading the thread on debian ML, I realize this issue is related to nested MIME and it affects large mailboxes In my case, the

Getting rawlogging working with dovecot 2.2

According to this manual[1] I just have to add these lines to my config, not? protocol imap { rawlog_dir = /tmp/rawlog/%u } I should be seeing something in this /tmp/rawlog if I delete an message via imap not? I have already made this folder 777 and /tmp/rawlog/test 777, but still nothing

Re: Virtual folder with 'younger' not updating

On 30/12/2020 10:22, Aki Tuomi wrote: On 30/12/2020 12:11 Jonathan Casiot wrote: On 30/12/2020 10:00, Aki Tuomi wrote: On 30/12/2020 11:52 Jonathan Casiot wrote: On 30/12/2020 06:25, Aki Tuomi wrote: On 29/12/2020 21:15 Jonathan Casiot wrote: I have a virtual folder set

RE: Imap client with ~7500 imap cmds ~250/~500 read() syscall

> On 30/12/2020 12:06 Marc Roos wrote: > > > > > >> > >> > >> I am playing a bit with the monitoring, and I have noticed there is > one > >> client of the chart with ~7500, while the others are between ~17 and > ~60 > >> (dovecot_user_num_cmds). > >> > >> I assume this is related to t

Re: Virtual folder with 'younger' not updating

> On 30/12/2020 12:11 Jonathan Casiot wrote: > > > On 30/12/2020 10:00, Aki Tuomi wrote: > > > >> On 30/12/2020 11:52 Jonathan Casiot wrote: > >> > >> > >> On 30/12/2020 06:25, Aki Tuomi wrote: > >>> > On 29/12/2020 21:15 Jonathan Casiot wrote: > > > I have a vir

RE: read state not propagated

> On 30/12/2020 12:19 Marc Roos wrote: > > > >Can you somehow confirm that the "read" status is not available > >for the 2nd user in dovecot indexes? Maybe use mail_log plugin to > > see when the flag changes occur? > > Is it possible to configure this logging for only one users, maybe via

RE: read state not propagated

>Can you somehow confirm that the "read" status is not available >for the 2nd user in dovecot indexes? Maybe use mail_log plugin to > see when the flag changes occur? Is it possible to configure this logging for only one users, maybe via this special-userdb? This would be sufficient not?

Re: Virtual folder with 'younger' not updating

On 30/12/2020 10:00, Aki Tuomi wrote: On 30/12/2020 11:52 Jonathan Casiot wrote: On 30/12/2020 06:25, Aki Tuomi wrote: On 29/12/2020 21:15 Jonathan Casiot wrote: I have a virtual folder set up with the following in dovecot-virtual: INBOX INBOX.temp ALL YOUNGER 86400 The pro

RE: Imap client with ~7500 imap cmds ~250/~500 read() syscall

> >> >> >> I am playing a bit with the monitoring, and I have noticed there is one >> client of the chart with ~7500, while the others are between ~17 and ~60 >> (dovecot_user_num_cmds). >> >> I assume this is related to the client, or is it possible something is >> wrong on the server si

Re: Virtual folder with 'younger' not updating

> On 30/12/2020 11:52 Jonathan Casiot wrote: > > > On 30/12/2020 06:25, Aki Tuomi wrote: > > > >> On 29/12/2020 21:15 Jonathan Casiot wrote: > >> > >> > >> I have a virtual folder set up with the following in dovecot-virtual: > >> > >> INBOX > >> INBOX.temp > >>ALL YOUNGER 86400 > >>

Re: Imap client with ~7500 imap cmds ~250/~500 read() syscall

> On 30/12/2020 11:46 Marc Roos wrote: > > > I am playing a bit with the monitoring, and I have noticed there is one > client of the chart with ~7500, while the others are between ~17 and ~60 > (dovecot_user_num_cmds). > > I assume this is related to the client, or is it possible something

Re: Virtual folder with 'younger' not updating

On 30/12/2020 06:25, Aki Tuomi wrote: On 29/12/2020 21:15 Jonathan Casiot wrote: I have a virtual folder set up with the following in dovecot-virtual: INBOX INBOX.temp ALL YOUNGER 86400 The problem is that messages older than 86,400 seconds (24 hours) never disappear from the folder.

Imap client with ~7500 imap cmds ~250/~500 read() syscall

I am playing a bit with the monitoring, and I have noticed there is one client of the chart with ~7500, while the others are between ~17 and ~60 (dovecot_user_num_cmds). I assume this is related to the client, or is it possible something is wrong on the server side? Is someone having also suc

Re: AUTH command behaviour when authentication process failed or aborted by user is changed

I found that the problem was already fixed in https://github.com/dovecot/core/commit/d0ea7f9f4530878a40ae0275cf0c36d3ff9111fc. So, I'm going to wait until the new dovecot release. Thank you for your help! сб, 26 дек. 2020 г. в 19:59, John Fawcett : > On 24/12/2020 08:42, Михаил Сандаков wrote: >