Permissions for dovecot logging
Aki Tuomi
aki.tuomi at open-xchange.com
Fri Dec 30 07:17:08 UTC 2022
> On 30/12/2022 05:25 EET James Moe <moe.james at sma-inc.us> wrote:
>
>
> On 2022-12-28 00:27, Aki Tuomi wrote:
>
> > The `log` service runs by default as root, not as dovecot.
> >
> Then I do not understand why there is a permissions problem at all. It is root!
>
> > If data01 is a NFS mount, then root may become squashed.
> >
> Not an NFS mount. It is local.
>
> > If you want to run log as `dovecot`, you can do so with
> >
> > service log {
> > user = dovecot
> > }
> >
> Permission is still denied.
> Where do I find information about "status=80/n/a"?
>
> I did not include all two of the syslog entries in the previous message:
> 2022-12-29T20:17:56-0700 sma-server3 dovecot[12102]: Can't open log file
> /data01/var/log/dovecot.log: Permission denied
> 2022-12-29T20:17:56-0700 sma-server3 systemd[1]: dovecot.service: Main process
> exited, code=exited, status=80/n/a
>
>
> --
> James Moe
> moe dot james at sohnen-moe dot com
> 520.743.3936
> Think.
Maybe you have selinux or apparmor involved? On rhel based systems, selinux logs into /var/log/audit/audit.log, dmesg -T is another good thing to check.
Aki
More information about the dovecot
mailing list