Event 0x560045857eb0 leaked
what do these logs mean in mail.log? Nov 18 10:23:03 mx dovecot: auth: Warning: Event 0x560045857eb0 leaked (parent=(nil)): auth-client-connection.c:338 Nov 18 10:23:03 mx dovecot: auth: Warning: Event 0x560045894390 leaked (parent=(nil)): auth-client-connection.c:338 Nov 18 10:23:03 mx dovecot: auth: Warning: Event 0x56004589d3e0 leaked (parent=(nil)): auth-client-connection.c:338 Nov 18 10:23:03 mx dovecot: auth: Warning: Event 0x56004588f810 leaked (parent=(nil)): auth-client-connection.c:338 Nov 18 10:23:03 mx dovecot: auth: Warning: Event 0x560045857240 leaked (parent=(nil)): auth-client-connection.c:338 Nov 18 10:23:03 mx dovecot: auth: Warning: Event 0x56004589cfd0 leaked (parent=(nil)): auth-client-connection.c:338 Nov 18 10:23:03 mx dovecot: auth: Warning: Event 0x56004586b130 leaked (parent=(nil)): auth-client-connection.c:338 I am using this version dovecot in a ubunto 20.04 box. # dovecot --version 2.3.7.2 (3c910f64b) thanks.
Compression: all or nothing?
Using 2.3.13 (89f716dc2) (debian package), with mdbox storage. I considering adding the zlib plugin. I understand that reading mail can cope with either compressed or uncompressed mailboxes. I'm wondering if I can leave the main storage uncompressed, while having the alternate storage compressed. There does not seem to be a way to configure this, from https://doc.dovecot.org/settings/plugin/zlib-plugin/ it seems compression (on saving emails) is an all-or-nothing option? Can I leave zlib_save unset in my main configuration, and have doveadm use some alternate configuration with zlib_save set? It doesn't look hopeful because I don't see the ability to use a different config at https://wiki.dovecot.org/Tools/Doveadm/Altmove. Perhaps I would need multiple copies of the daemon running? Or is it better just to compress everything? I plan to store older mails (perhaps 3months+) in the alternative storage, and was thinking it would be nice to have those compressed, while I don't need to compress the main store. Any feedback welcome. Thanks, Alex
Re: Dovecot 2.2 to 2.3 migration
On 11/17/22 09:28, Oscar del Rio wrote: I believe there is no Dovecot APT repo for Ubuntu 22 (yet) https://repo.dovecot.org/ Very true. I believe I read somewhere that there will not be a Dovecot 2.3 repo for jammy, but there will be one for 2.4 when it is released. Thanks, Shawn
Re: Dovecot 2.2 to 2.3 migration
On 2022-11-17 10:26 a.m., Shawn Heisey wrote: On 11/15/22 03:29, Markus Wienhöfer wrote: we are currently using Dovecot 2.2 (from the Ubuntu 18.04 repos) and would like to migrate to 2.3 I have read the migration documentation regarding the configuration changes. Apart from that, is it feasible/possible to change from Ubuntu to official Dovecot repositories and upgrade the dovecot package this way? This is what I did. After upgrading from Ubuntu 18 to Ubuntu 20, I added the dovecot APT repo and installed from there. It all went smoothly, and the migration notes were sufficient. At some point I will upgrade that system to Ubuntu 22... I believe there is no Dovecot APT repo for Ubuntu 22 (yet) https://repo.dovecot.org/
Re: Dovecot 2.2 to 2.3 migration
On 11/15/22 03:29, Markus Wienhöfer wrote: we are currently using Dovecot 2.2 (from the Ubuntu 18.04 repos) and would like to migrate to 2.3 I have read the migration documentation regarding the configuration changes. Apart from that, is it feasible/possible to change from Ubuntu to official Dovecot repositories and upgrade the dovecot package this way? This is what I did. After upgrading from Ubuntu 18 to Ubuntu 20, I added the dovecot APT repo and installed from there. It all went smoothly, and the migration notes were sufficient. At some point I will upgrade that system to Ubuntu 22, but I will be waiting until all the PHP webapps I am using are upgraded to support PHP 8.1. If you use a lot of PHP apps, the upgrade from PHP 7.4 in Ubuntu 20 to PHP 8.1 in Ubuntu 22 is probably going to break at least one of them. App developers are not adjusting to PHP 8.x very quickly. For the gurus: Is there an expected ballpark release date for 2.4 and/or 3.0? Thanks, Shawn
