Re: Deleting an active sieve script leaves sieve unfunctional

5 Jul 2021

      There's no symlink pointing to that very script. I have virtual users, so I
keep the respective sieve scripts in /srv/sieve/user@domain/.
Such a directory looks like that:
active-script.sieve -> USER.sieve
USER.sieve
some-script.sieve
some-other-script.sieve
...
Where USER.sieve is the generated file which includes the activated scripts:
# USER Management Script
#
# This script includes the various active sieve scripts
# it is AUTOMATICALLY GENERATED. DO NOT EDIT MANUALLY!
# 
# For more information, see http://wiki.kolab.org/KEP:14#USER
#

require ["include"];

include :personal "some-script";
include :personal "some-other-script";
Am Montag, 5. Juli 2021, 18:46:30 CEST schrieb dovecot@ptld.com:
...
...
On 07-05-2021 10:29 am, Tobias Leupold wrote:
So, to avoid this, one has to FIRST deactivate the respectice script,
so that
USER.sieve is updated and THEN delete the script. Or to manually fix
USER.sieve on the server, which is surely not what's intended.
Curious, can you also fix the situation by just removing the symlink
pointing to the non existent script?