similar to: stats-writer error is back

service stats { unix_listener stats-reader { group = mail mode = 0666 user = } unix_listener stats-writer { group = mail mode = 0666 user = } } service anvil { unix_listener anvil { group = mail mode = 0666 } } in my local.conf. On Sat, Apr 20, 2019 at 2:46 PM @lbutlr via dovecot <dovecot at dovecot.org> wrote: > Afer a reboot (and

On 20 Apr 2019, at 14:05, Larry Rosenman via dovecot <dovecot at dovecot.org> wrote: > service stats { > unix_listener stats-reader { > group = mail Why would I change the group from the group the socket is using? > mode = 0666 That cannot possibly be best practice. I'm not opening up any part of my mail stack to all processes. >> # ls -ls

I?m running Dovecot 2.3.4 on FreeBSD 11.2 with qmail. In my mail log, I see messages like this on every delivery Jan 8 10:30:02 v1 qmail: 1546961402.314222 delivery 533: success: lda(matt,)Error:_net_connect_unix(/var/run/dovecot/stats-writer)_failed:_Permission_denied/did_0+0+1/ Searching for this error, I found a message on a support forum for a different server that suggested adding this to

Hi, We are getting very occasional messags from dovecot: > net_connect_unix(/var/run/dovecot/stats-writer) failed: Permission denied Over the last week, the message appeared five times. (on a mail server with over 100 users, to that's basically almost never) doveconf -n below > # 2.3.4.1 (f79e8e7e4): /etc/dovecot/dovecot.conf > # Pigeonhole version 0.5.4 () > # OS: Linux

Hi! You can ignore it, or you can change the socket permissions to 0666. service stats { unix_listener stats-writer { mode = 0666 } } Aki > On 23/10/2020 17:52 mj <lists at merit.unu.edu> wrote: > > > Hi, > > Nobody? > > It happens so rarely, and the system appears to be running fine > otherwise, should I just ignore it? > > Still

I am getting this error in logs net_connect_unix(/var/run/dovecot/stats-writer) failed: Permission den)) and I looked around the google results and it seems to be related to using service stats, which I am not using. # doveconf -n | grep stat # doveconf -n | head -3 # 2.3.5.1 (7ec6d0ade): /usr/local/etc/dovecot/dovecot.conf # Pigeonhole version 0.5.5 (2483b085) # OS: FreeBSD 11.2-RELEASE-p4

On Wed, 10 Apr 2019 at 17:50, @lbutlr via dovecot <dovecot at dovecot.org> wrote: > On 10 Apr 2019, at 08:36, @lbutlr via dovecot <dovecot at dovecot.org> wrote: > > net_connect_unix(/var/run/dovecot/stats-writer) failed: Permission den)) > > One other detail: > > /var/run/dovecot/stats-writer: > 0 srw-rw---- 1 root dovecot 0 Apr 10 08:47 stats-writer

Greetings, Well, I en devoured to install a copy of 7 as an effort to upgrade one of our servers. After installing a few ports, I began to notice: [: -le: argument expected messages being emitted during the configure/make process. I've already invested a fair amount of time on this upgrade, and /really/ don't want to wipe the disk(s) and start all over. This issue is not new to me - see

Hello, I am mosty done with the upgrade, but there is a problem that keeps me awake at night: file ownership and permissions. It would be most helpful to have the following from Aki's live system: ls -halFR /var/run/dovecot -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hello, Absolutely. Here is the output of doveconf -n: # doveconf -n # 2.2.31 (65cde28): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.19 (e5c7051) # OS: Linux 4.9.36-x86_64-linodexx x86_64 Arch Linux auth_mechanisms = plain login base_dir = /var/run/dovecot/ dict { expire = ldap:/etc/dovecot/dovecot-ldap.conf.ext quota = ldap:/etc/dovecot/dovecot-ldap.conf.ext } doveadm_password = #

Greetings, I'm setting up replication and am getting this error from the server where the replicated mails are being initially created: Aug 27 11:03:53 molecular dovecot: dsync-server(user at domain.org): Error: Couldn't create lock /vmail/domain.org/user/home/.dovecot-sync.lock: No such file or directory Can anyone shed some light on this? Here's the Replicator config of the

Hello! doveconf --version 2.2.36 I want to move to a new server with dovecot but get an error Error: service(quota-status): listen(*, 12340) failed: Permission denied when I define service quota-status { executable = quota-status -p postfix inet_listener { port = 12340 } client_limit = 1 } private]# ll insgesamt 0 srw-rw-rw-. 1 postfix postfix 0 14. Apr 15:05 anvil

On 21/02/2016 10:43 PM, aki.tuomi at dovecot.fi wrote: >> The PID-File seems to be expected under yet another sub-dir of >> /var/run/dovecot. >> >> Regards >> Thomas > > Hi, > > This is fixed in > https://github.com/dovecot/core/commit/22d75d47097ca83c6e824a5129d81e8f18fb589b > > --- > Aki Tuomi This doesn't seem to be fixed for me, with

http://hg.dovecot.org/dovecot-2.2/rev/64c73e6bd397 Today I finally committed the "imap-hibernate" feature that I first started developing about a year ago (and had been thinking about for several years before that). The main purpose here is to reduce the number of imap processes and the amount of memory they use by moving IDLEing connections into imap-hibernate processes where they are

HI, I'm trying to exclude some files & directories from a filesystem which I would like to copy to a different site. I did: # rsync -avz --exclude-file=/fs21/tmp/perl_scripts/exclude.txt /fs22/a/circuit_design mickey.willow.com:/cpu/store/design where file /fs21/tmp/perl_scripts/exclude.txt contains the following directories and files to be excluded from /fs22/a/circuit_design :

Hi, I am trying to use Quota in dovecot-2.0.11. I find as a sender(same user a receiver) I receive an email that receiver's Quota is exceeded , and receiver's mailbox is full . This is good, however the receiver whose MB is full isn't getting any quota-warning. Configuration is as below, dovecot -n # 2.0.11: /etc/dovecot/dovecot.conf # OS: Linux 2.6.35-gentoo-r8 x86_64 Gentoo Base

I have migrated from dovecot 1.2 to dovecot 2.0. When I connect via telnet to 110 port of the dovecot server the client hangs: telnet 192.168.4.80 110 Trying 192.168.4.80... /Connected to 192.168.4.80. Escape character is '^]'./ In syslog I got the following error: /Jan 12 12:14:44 buzon dovecot: imap-login: Error: auth: connect(login) in directory / failed: Permission denied

I have this[0] config, yet the /var/run/dovecot/login/director is not created, what to check in the config? dovecot: imap-login: Error: auth: connect(director) failed: No such file or directory [0] service director { unix_listener login/director { #mode = 0666 } fifo_listener login/proxy-notify { #mode = 0666 } unix_listener director-userdb { #mode = 0600 }

But if in the configuration of the director is stated login/director. Than I assume this socket should be in the login dir not? You have also the director activate with executable = imap-login director? -----Original Message----- Subject: Re: Login/director not created On my install the login/ dir is: drwxr-x--- 2 root dovenull 8 Nov 10 18:14:00 login/ srw-rw-rw- 1 root

Using rpms and converted dovecot.conf with doveconf. Need assistance to determine how to resolve 'auth-worker' and userdb complaint. logging into mysql from commandline with mail admin acct and using dovecot sql query is successful but the following fails: doveadm auth -x service=imap -x lip=127.0.0.1 john Password: passdb: john auth failed extra fields: temp doveadm(root): Fatal: