kopano server cannot write attachment folder

gmcpaul

changing
ProtectHome=yes to no
then
systemctl daemon-reload
then
/etc/init.d/kopano-server restart

now seems good according to server.log :D

fbartels

@gmcpaul an update safe way would be to create an override file. First run
sudo systemctl edit kopano-server and in the resulting editor paste the following:

[Service]
ProtectHome=no

gmcpaul

@fbartels said in kopano server cannot write attachment folder:

[Service]
ProtectHome=no

@fbartels many thanks!!
have a nice weekend

case can be closed from my side.

longsleep

@gmcpaul said in kopano server cannot write attachment folder:

changing
ProtectHome=yes to no

This is less secure and cannot be recommended. It would be much better if your attachments were stored outside of /home and the setting is kept as is. See https://www.freedesktop.org/software/systemd/man/systemd.exec.html#ProtectHome= for exact details on the protection offfered when ProtectHome is enabled.

gmcpaul

Hi @longsleep
well thank you for the input.
I will keep in mind for future projects.
in my case the machine was historically (beginning from zarafa) set up with the use of /home to let large amounts of data outsourced on an seperate partition for a service to run in a “bubble” and to keep the files out of default system paths.
Since the filese are locked in run_as environments i thougt that wa a good design. Also when space is eaten up and you need to enlarge the hdd in a vm for example… so all was done in good intension so to speak.

Well… lessons learned for me :D
Thank you all