Dear devs,
I noticed this using Dovecot 2.3.7.2, set up on a newly created Ubuntu
20.04
server.
If I delete a sieve script via KMail's managesieve interface, and the
script
is active, it leaves sieve unfunctional afterwards.
What's happening is this:
Dovecot creates a USER.sieve script con
:14#USER
#
require ["include"];
include :personal "some-script";
include :personal "some-other-script";
Am Montag, 5. Juli 2021, 18:46:30 CEST schrieb dove...@ptld.com:
> > On 07-05-2021 10:29 am, Tobias Leupold wrote:
> >
>
omatically, or if Dovecot should remove
a script to delete from USER.sieve before deleting it. Or if I did something
wrong configuring Dovecot ;-)
Am Montag, 5. Juli 2021, 18:58:15 CEST schrieb Benny Pedersen:
> On 2021-07-05 16:29, Tobias Leupold wrote:
> > So the question is now: Is
:14#USER
#
require ["include"];
include :personal "some-script";
include :personal "some-other-script";
Am Montag, 5. Juli 2021, 18:46:30 CEST schrieb dove...@ptld.com:
> > On 07-05-2021 10:29 am, Tobias Leupold wrote:
> >
> > So, to avoid
Juli 2021, 19:27:50 CEST schrieb dove...@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/.
> >
> &
com:
> > On 07-05-2021 1:34 pm, Tobias Leupold wrote:
> >> 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 cour
> My educated guess is, yes this is a KMail issue.
Okay, thanks :-) I'll file a bug report there.
Am Montag, 5. Juli 2021, 21:30:54 CEST schrieb dove...@ptld.com:
> > On 07-05-2021 2:04 pm, Tobias Leupold wrote:
> >
> > When I delete a sieve script via the manages
