dovecot - Jul 2021 - Deleting an active sieve script leaves sieve unfunctional

There's no symlink pointing to that very script. I have virtual users, so I 
keep the respective sieve scripts in /srv/sieve/user at 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 at
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?

> On 07-05-2021 1:04 pm, Tobias Leupold wrote:
> There's no symlink pointing to that very script. I have virtual users, 
> so I
> keep the respective sieve scripts in /srv/sieve/user at domain/.
> 
> Such a directory looks like that:
> 
>     active-script.sieve -> USER.sieve
>     USER.sieve
>     some-script.sieve
>     some-other-script.sieve
Yes, that is the one im talking about: active-script.sieve
Just remove that symlink and sieve will be disabled for that user and 
you shouldn't have any errors.