5 Jul
2021
5 Jul
'21
8:34 p.m.
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.
Yeah, of course I won't -- but sieve filtering won't work as well without the symlink ...
Am Montag, 5. Juli 2021, 19:27:50 CEST schrieb dovecot@ptld.com:
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@domain/.
Such a directory looks like that: active-script.sieve -> USER.sieve USER.sieve some-script.sieve some-other-script.sieve