Hi Aki
with the following in dovecot.service unit file
ProtectSystem=full
ProtectHome=false
my logs still fill with RO warnings.
Only if I remove the ProtectSystem (comment out) dovecot runs without RO
errors for the home.
Cheers
tobi
Am 28.10.2017 um 12:47 schrieb Aki Tuomi:
>
>> On October
> On October 28, 2017 at 1:41 PM Tobi wrote:
>
>
> Hello list
>
> I saw the response from Vlad in my queue (as dovecot was broken there
> has been no delivery to mailbox) but after fix and queue flush Vlads
> message does not show up in my mailbox.
>
> > Check the systemd unit for ProtectHome
Hello list
I saw the response from Vlad in my queue (as dovecot was broken there
has been no delivery to mailbox) but after fix and queue flush Vlads
message does not show up in my mailbox.
> Check the systemd unit for ProtectHome, and make sure that is turned
> off.
Found these lines in unit fi
> On October 28, 2017 at 1:12 PM "Vlad K." wrote:
>
>
> On 2017-10-28 11:51, Tobi wrote:
> >
> > Does anyone have an idea why dovecot suddenly behaves like that?
> >
>
> Since that's CentOS 7, I've heard SystemD tends to go mad (madder than
> usual) and mount the service with readonly paths
On 2017-10-28 11:51, Tobi wrote:
Does anyone have an idea why dovecot suddenly behaves like that?
Since that's CentOS 7, I've heard SystemD tends to go mad (madder than
usual) and mount the service with readonly paths...
--
Vlad K.
:2017-10-28T11:51:Tobi:
> Oct 28 11:39:50 mbox1 dovecot: lmtp(tobs...@brain-force.ch): Error:
> ssY/MGZQ9FnoLgAAC4IaJw:2: sieve: failed to open logfile (LOGGING TO
> STDERR): open(/home/vmail/brain-force.ch/tobster/.dovecot.sieve.log)
> failed: Read-only file system
>
> But a test at cli shows th
Hi list
I have to dovecot instances running which host my mailboxes on Centos7
dovecot.x86_64 1:2.2.26.0-2.el7.centos
installed
dovecot-debuginfo.x86_641:2.2.26.0-2.el7.centos
installed
dovecot-mysql.x86_641:2.2.26.0-2.el7.centos
installed
dovecot-
