5 Jul
2021
5 Jul
'21
7:46 p.m.
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?