I do believe that imap reader processes write stats as the *USER*.
On Sat, Apr 20, 2019 at 3:41 PM @lbutlr via dovecot
wrote:
> On 20 Apr 2019, at 14:21, Larry Rosenman via dovecot
> wrote:
> > Then figure out what user/group needs the access and set the perms.
>
> Well, stats-write has an
On 20 Apr 2019, at 14:21, Larry Rosenman via dovecot
wrote:
> Then figure out what user/group needs the access and set the perms.
Well, stats-write has an owner and group of dovecot, as I showed.
dovecot dovecot 0 Apr 20 04:34 /var/run/dovecot/stats-writer
--
'I thought dwarfs didn't
Then figure out what user/group needs the access and set the perms.
I can't help you other than what I've shown you.
(my box doesn't have foreign users on it, so this was the most espedient
route for me).
On Sat, Apr 20, 2019 at 3:16 PM @lbutlr via dovecot
wrote:
> On 20 Apr 2019, at 14:05,
On 20 Apr 2019, at 14:05, Larry Rosenman via dovecot
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
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.
Maybe a resend (sorry
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
Afer a reboot (and installation of postfix-3.4.5) I am getting the stat-writer
permission denied error again.
from doveconf -n
service stats {
unix_listener stats-reader {
user = dovecot
}
unix_listener stats-writer {
user = dovecot
}
}
# ls -ls /var/run/dovecot/stats-writer
0
I have no idea how to use git-bitsec
On 2019-04-15 15:31, Josef 'Jeff' Sipek wrote:
On Sun, Apr 14, 2019 at 21:09:54 +0800, Joan Moreau wrote:
...
THe "loop" part seems the most urgent : It breaks everything (search
timeout 100% of the time)
Any luck with git-bisect?
Jeff.
On
