On Thu, Aug 29, 2019 at 01:08:32PM +0300, Timo Sirainen wrote: > On 29 Aug 2019, at 3.57, Josh Triplett <j...@joshtriplett.org> wrote: > > > > On Wed, Aug 28, 2019 at 05:43:27PM -0700, Josh Triplett wrote: > >> So if the stats sockets don't exist at *all*, deliver won't complain. > >> > >> To disable those stats sockets, add the following configuration to a > >> file in /etc/dovecot/conf.d/ : > > > > Update: sadly this doesn't fully work, as it produces the following > > spurious errors in the logs: > > > > Aug 28 17:54:27 cloud dovecot[3168]: imap-login: Error: > > net_connect_unix(/var/run/dovecot/stats-writer) failed: No such file or > > directory > > Aug 28 17:54:27 cloud dovecot[3168]: auth: Error: > > net_connect_unix(/var/run/dovecot/stats-writer) failed: No such file or > > directory > > Aug 28 17:54:27 cloud dovecot[3168]: auth: Error: stats: > > open(old-stats-user) failed: No such file or directory > > Aug 28 17:54:28 cloud dovecot[3168]: auth: Error: > > net_connect_unix(/var/run/dovecot/stats-writer) failed: No such file or > > directory > > Aug 28 17:54:28 cloud dovecot[3168]: auth-worker(3182): Error: stats: > > open(old-stats-user) failed: No such file or directory > > Aug 28 17:54:28 cloud dovecot[3168]: imap: Error: > > net_connect_unix(/var/run/dovecot/stats-writer) failed: No such file or > > directory > > > > So while deliver has no problem ignoring such errors, the rest of > > dovecot unfortunately doesn't like that configuration. > > > > I'd like to have a "disable all stats" configuration, rather than having > > to make a stats socket available to the user running deliver. > > Add to dovecot.conf: stats_writer_socket_path=
Interesting! I'll try that and see how it goes.
