On 20/05/24 01:55, Richard Rosner via dovecot wrote:
Am 19.05.24 um 15:29 schrieb Friedrich Kink via dovecot:
chmod 775 /var/log/dovecot will solve the problem. Without execute
permission the process can't access the logfile.
Why on earth does a process supposed to write to a file need
> Am 19.05.2024 um 16:49 schrieb Richard Rosner via dovecot:
> > It most certainly isn't. nginx isn't running as root, yet it can log
> > without execution permissions just fine. Absolutely nothing should have
> > execution permissions if they aren't meant to be executed, which should
> > only be
Am 19.05.2024 um 16:49 schrieb Richard Rosner via dovecot:
It most certainly isn't. nginx isn't running as root, yet it can log
without execution permissions just fine. Absolutely nothing should have
execution permissions if they aren't meant to be executed, which should
only be true for a
As Alexander wrote - posix behaviour. To change into a directory the directory
itself needs execute permission for owner/group/other (what ever is meant). Not
the file itself. BTW even a chmod 110 /var/log/dovecot (so only execute and no
read/write) would work.
On 19.05.24 16:49, Richard
Am 19.05.24 um 16:02 schrieb Alexander Dallou via dovecot:
Am 19.05.2024 um 15:55 schrieb Richard Rosner via dovecot:
Am 19.05.24 um 15:29 schrieb Friedrich Kink via dovecot:
chmod 775 /var/log/dovecot will solve the problem. Without execute permission
the process can't access the logfile.
Am 19.05.2024 um 15:55 schrieb Richard Rosner via dovecot:
Am 19.05.24 um 15:29 schrieb Friedrich Kink via dovecot:
chmod 775 /var/log/dovecot will solve the problem. Without execute
permission the process can't access the logfile.
Why on earth does a process supposed to write to a file need
Am 19.05.24 um 15:29 schrieb Friedrich Kink via dovecot:
chmod 775 /var/log/dovecot will solve the problem. Without execute permission
the process can't access the logfile.
Why on earth does a process supposed to write to a file need execution
permission? This most certainly is very unwelcome
chmod 775 /var/log/dovecot will solve the problem. Without execute permission
the process can't access the logfile.
On 19.05.24 12:25, Richard Rosner via dovecot wrote:
Am 19.05.24 um 04:02 schrieb Peter via dovecot:
> Check the permissions of the entire path, as dovecot:
>
> namei -l
Am 19.05.24 um 04:02 schrieb Peter via dovecot:
Check the permissions of the entire path, as dovecot:
namei -l /var/log/dovecot/error.log
It might be selinux, check your audit.log file, or set selinux to permissive
mode and see if it works:
setenforce 0
This can't be the case, there is no
On 19/05/24 04:31, Richard Rosner via dovecot wrote:
I have a mailing server setup based on Debian Stable that uses postfix
(v3.7.10) for SMTP and dovecot (v2.3.19.1 (9b53102964)) for IMAP. I now
wanted to set dovecot to not write to syslog, but to dedicated files in
/var/log/dovecot. While
I have a mailing server setup based on Debian Stable that uses postfix
(v3.7.10) for SMTP and dovecot (v2.3.19.1 (9b53102964)) for IMAP. I now wanted
to set dovecot to not write to syslog, but to dedicated files in
/var/log/dovecot. While everything indicates that this happens successfully as
11 matches
Mail list logo
