Re: How to use mail_user_session_finished? (was Re: [Dovecot-news] Dovecot v2.3.19 released)
> On 12/05/2022 01:15 Sylvain Robitaille wrote:
>
>
> On Tue, 10 May 2022, Aki Tuomi via Dovecot-news wrote:
>
> > + Added mail_user_session_finished event, which is emitted when the mail
> > user session is finished (e.g. imap, pop3, lmtp). It also includes
> > fields with some process statistics information.
> > See https://doc.dovecot.org/admin_manual/list_of_events/ for more
> > information.
>
> We thought that this might give us some useful information in our logs,
> especially when investigating user complaints (thanks, by the way, both
> for Dovecot itself, and for the new logging functionality). I added to
> our 10-logging.conf file:
>
> --- .../10-logging.conf 2022-02-02 09:53:52.0 -0500
> +++ .../10-logging.conf 2022-05-11 16:40:48.116914000 -0400
> @@ -44,8 +44,13 @@ plugin {
>#mail_log_events = delete undelete expunge copy mailbox_delete
> mailbox_rename
>#mail_log_events = mailbox_delete mailbox_rename
># 2022-01-02 Anne Bennett: per RT#461889, log more
> - mail_log_events = delete undelete expunge copy mailbox_delete
> mailbox_rename append flag_change
> + # 2022-05-11 Sylvain Robitaille: per RT#478860, log new
> + #mail_user_session_finished event
> + mail_log_events = delete undelete expunge copy mailbox_delete
> mailbox_rename append flag_change mail_user_session_finished
># Available fields: uid, box, msgid, from, subject, size, vsize, flags
># size and vsize are available only for expunge and copy events.
> - mail_log_fields = uid box msgid size
> + # mail_user_session_finished adds: utime, stime, minor_faults,
> + #major_faults, vol_cs, invol_cs, rss, vsz, rchar, wchar, syscr,
> + #syscw
> + mail_log_fields = uid box msgid size rss vsz
> }
>
> ... and reloaded ("dovecot reload"), following which the log
> informed me:
>
> May 11 16:56:45 lust dovecot: master: Warning: SIGHUP received -
> reloading configuration
> May 11 16:56:46 lust dovecot: imap(syl)<27995>:
> Disconnected: Server shutting down. in=20441 out=1721757 deleted=42
> expunged=40 trashed=0 hdr_count=89 hdr_bytes=147223 body_count=81
> body_bytes=1504010
> ...
> May 11 16:58:05 lust dovecot: imap-login: Login: user=,
> method=GSSAPI, rip=132.205.2.217, lip=132.205.96.89, mpid=26509, TLS,
> session=
> May 11 16:58:05 lust dovecot: imap(syl)<26509>: Fatal:
> Unknown field in mail_log_fields: 'rss'
>
> Hrmmm ... Ok, remove "rss" and reload:
>
> May 11 16:58:44 lust dovecot: master: Warning: SIGHUP received -
> reloading configuration
> May 11 16:58:50 lust dovecot: imap-login: Login: user=,
> method=GSSAPI, rip=132.205.2.217, lip=132.205.96.89, mpid=26573, TLS,
> session=
> May 11 16:58:50 lust dovecot: imap(syl)<26573>: Fatal:
> Unknown field in mail_log_fields: 'vsz'
>
> Not what I was expecting, of course, but can we at least see the
> events logged? remove "vsz" and reload again:
>
> May 11 16:59:02 lust dovecot: master: Warning: SIGHUP received -
> reloading configuration
> May 11 16:59:06 lust dovecot: imap-login: Login: user=,
> method=GSSAPI, rip=132.205.2.217, lip=132.205.96.89, mpid=26606, TLS,
> session=
> May 11 16:59:06 lust dovecot: imap(syl)<26606>: Fatal:
> Unknown event in mail_log_events: 'mail_user_session_finished'
>
> Alright, remove mail_user_session_finished and reload, and it's ok
> again. I *must* be doing something wrong here, but I can't figure
> out what that it, and it seems that mail_user_session_finished has not
> reached any of the documentation within the source tree. Can someone
> point me to documentation for how to use this? Am I jumping the gun
> here, or am I just doing it wrong?
>
> --
> --
> Sylvain Robitaille s...@encs.concordia.ca
>
Hi!
Can you provide us with the configuration you attempted?
AKi
How to use mail_user_session_finished? (was Re: [Dovecot-news] Dovecot v2.3.19 released)
On Tue, 10 May 2022, Aki Tuomi via Dovecot-news wrote:
+ Added mail_user_session_finished event, which is emitted when the mail
user session is finished (e.g. imap, pop3, lmtp). It also includes
fields with some process statistics information.
See https://doc.dovecot.org/admin_manual/list_of_events/ for more
information.
We thought that this might give us some useful information in our logs,
especially when investigating user complaints (thanks, by the way, both
for Dovecot itself, and for the new logging functionality). I added to
our 10-logging.conf file:
--- .../10-logging.conf 2022-02-02 09:53:52.0 -0500
+++ .../10-logging.conf 2022-05-11 16:40:48.116914000 -0400
@@ -44,8 +44,13 @@ plugin {
#mail_log_events = delete undelete expunge copy mailbox_delete
mailbox_rename
#mail_log_events = mailbox_delete mailbox_rename
# 2022-01-02 Anne Bennett: per RT#461889, log more
- mail_log_events = delete undelete expunge copy mailbox_delete
mailbox_rename append flag_change
+ # 2022-05-11 Sylvain Robitaille: per RT#478860, log new
+ #mail_user_session_finished event
+ mail_log_events = delete undelete expunge copy mailbox_delete
mailbox_rename append flag_change mail_user_session_finished
# Available fields: uid, box, msgid, from, subject, size, vsize, flags
# size and vsize are available only for expunge and copy events.
- mail_log_fields = uid box msgid size
+ # mail_user_session_finished adds: utime, stime, minor_faults,
+ #major_faults, vol_cs, invol_cs, rss, vsz, rchar, wchar, syscr,
+ #syscw
+ mail_log_fields = uid box msgid size rss vsz
}
... and reloaded ("dovecot reload"), following which the log
informed me:
May 11 16:56:45 lust dovecot: master: Warning: SIGHUP received - reloading
configuration
May 11 16:56:46 lust dovecot: imap(syl)<27995>:
Disconnected: Server shutting down. in=20441 out=1721757 deleted=42
expunged=40 trashed=0 hdr_count=89 hdr_bytes=147223 body_count=81
body_bytes=1504010
...
May 11 16:58:05 lust dovecot: imap-login: Login: user=, method=GSSAPI,
rip=132.205.2.217, lip=132.205.96.89, mpid=26509, TLS, session=
May 11 16:58:05 lust dovecot: imap(syl)<26509>: Fatal:
Unknown field in mail_log_fields: 'rss'
Hrmmm ... Ok, remove "rss" and reload:
May 11 16:58:44 lust dovecot: master: Warning: SIGHUP received - reloading
configuration
May 11 16:58:50 lust dovecot: imap-login: Login: user=, method=GSSAPI,
rip=132.205.2.217, lip=132.205.96.89, mpid=26573, TLS, session=
May 11 16:58:50 lust dovecot: imap(syl)<26573>: Fatal:
Unknown field in mail_log_fields: 'vsz'
Not what I was expecting, of course, but can we at least see the
events logged? remove "vsz" and reload again:
May 11 16:59:02 lust dovecot: master: Warning: SIGHUP received - reloading
configuration
May 11 16:59:06 lust dovecot: imap-login: Login: user=, method=GSSAPI,
rip=132.205.2.217, lip=132.205.96.89, mpid=26606, TLS, session=
May 11 16:59:06 lust dovecot: imap(syl)<26606>: Fatal:
Unknown event in mail_log_events: 'mail_user_session_finished'
Alright, remove mail_user_session_finished and reload, and it's ok
again. I *must* be doing something wrong here, but I can't figure
out what that it, and it seems that mail_user_session_finished has not
reached any of the documentation within the source tree. Can someone
point me to documentation for how to use this? Am I jumping the gun
here, or am I just doing it wrong?
--
--
Sylvain Robitaille s...@encs.concordia.ca
Systems analyst / AITSConcordia University
Faculty of Engineering and Computer Science Montreal, Quebec, Canada
--
Re: [EXT] Re: Dovecot v2.3.19 released
So there's an "honest abe" -- with a "dv" attached the name -- and it's time to change the locks on the doors -- because apparently a couple of girls at the bank are working overtime doing loans and repossessions online and something is being served at a local bar or pub and a SWAT team is being called out Friday night or very early Saturday with fabricated criminal charges on any "hackers" who happen to be posting here On May 11, 2022 1:43:39 PM AKDT, "A. Schulze" wrote: > > >Am 11.05.22 um 07:26 schrieb Michael Tokarev: >>> You are using something like `libssl-dv` instead of libssl, hence me >>> asking. It does not appear to be using the stock libssl. > >Hello Aki & Michael > >I reviewed my build and indeed found a glitch. So: sorry for the noise. >dovecot-2.3.19 can be built with Debian/11 + Debian/openssl-1.1.1n > >I'm also able to build with my own openssl-1.1.1 version. >The error occurred because I tried to build with my own openssl-3.0.2 which >worked with dovecot-2.3.18 >But maybe this was unsupported anyway. > >Andreas > > -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
Re: [EXT] Re: Dovecot v2.3.19 released
Am 11.05.22 um 07:26 schrieb Michael Tokarev: You are using something like `libssl-dv` instead of libssl, hence me asking. It does not appear to be using the stock libssl. Hello Aki & Michael I reviewed my build and indeed found a glitch. So: sorry for the noise. dovecot-2.3.19 can be built with Debian/11 + Debian/openssl-1.1.1n I'm also able to build with my own openssl-1.1.1 version. The error occurred because I tried to build with my own openssl-3.0.2 which worked with dovecot-2.3.18 But maybe this was unsupported anyway. Andreas
Re: Dovecot v2.3.19 released
On Tue, 2022-05-10 at 09:33 +0300, Aki Tuomi wrote: > Hi all! > > We are pleased to release v2.3.19 of Dovecot. On Sun, 2022-02-06 at 14:25 +, Alan Swanson wrote: > On Sat, 2022-02-05 at 14:55 +1300, Peter wrote: > > On 8/12/21 2:12 am, Alan Swanson wrote: > > > Reverting commit "fts: Use mailbox-match-plugin API for > > > fts_autoindex_exclude" resolved this core dump in > > > lib20_fts_plugin.so for me. > > > > > > https://github.com/dovecot/core/commit/9d02ac2e4232cc69bc37344c6341674b87078301 > > > > Is this fixed yet in 2.3.18? > > > No, still broken and core dumping (there's been no changes > to src/plugins/fts/fts-storage.c) and the commit still > needs reverted on 2.3.18. Unfortunately this is still not fixed in 2.3.19 and continues to core dump at fts_user_autoindex_exclude(). Reverting the referenced commit still fixes it. -- Alan.
Re: [EXT] Re: Dovecot v2.3.19 released
Yes, thats me. I tried to use Debian ssl, but maybe I made something wrong. I will Check that later. Thanks!
