On 30 December 2022 22:25:09 CET, James Moe wrote:
>On 2022-12-27 16:19, James Moe wrote:
>
>> I changed logging to use a path rather than syslog. Doing so makes it
>> easier
>> to work with fail2ban.
>> Dovecot fails to start with the error:
>> Can't open log file
On 2022-12-27 16:19, James Moe wrote:
> I changed logging to use a path rather than syslog. Doing so makes it easier
> to work with fail2ban.
> Dovecot fails to start with the error:
> Can't open log file /data01/var/log/dovecot.log: Permission denied
>
Yes, it was apparmor. It has been
On Thursday, December 29, 2022 10:17:08 PM AKST Aki Tuomi wrote:
> > On 30/12/2022 05:25 EET James Moe wrote:
> > 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:
> >
> On 30/12/2022 05:25 EET James Moe 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
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
> On 28/12/2022 01:19 EET James Moe wrote:
>
>
> dovecot 2.3.15
> opensuse LEAP 15.4
>
> I changed logging to use a path rather than syslog. Doing so makes it easier
> to work with fail2ban.
> Dovecot fails to start with the error:
> Can't open log file /data01/var/log/dovecot.log:
dovecot 2.3.15
opensuse LEAP 15.4
I changed logging to use a path rather than syslog. Doing so makes it easier
to work with fail2ban.
Dovecot fails to start with the error:
Can't open log file /data01/var/log/dovecot.log: Permission denied
Permissions:
drwxrwxr-x 1 root users 104 Feb
