Am 10.11.21 um 13:31 schrieb João Silva:
That was the first thing I thought, I checked a user (where I saw that
happening) Trash folder and it was empty (maybe I need to check more
cases).
I can search but maybe somebody already knows, I can put on the sieve
one exception that prevents the pi
Alexander Dalloz:
You are just using a flase configration option which makes 2.3.17 fail
in your case.
You might be right, but I also think that if Dovecot needs a fix, it
would be also a good thing to provide an updated online version
including the fix instead of an unfixed version @ doveco
I've just removed dummy-c-1's mailbox completely on the target server,
removed the quota plugin, forced a sync for dummy-c-1 only and once it
was done reactivated the quota plugins: double usage again.
I also downgraded from dovecot 2.3.17 to 2.2.27 on the target server in
order to have both s
That was the first thing I thought, I checked a user (where I saw that
happening) Trash folder and it was empty (maybe I need to check more cases).
I can search but maybe somebody already knows, I can put on the sieve
one exception that prevents the pipe action in the case of the
destination d
> On 10/11/2021 14:22 João Silva wrote:
>
>
> Hi
>
> I'm having a problem related to Dovecot (version 2.2.36) sieves and I'm
> not finding information.
>
> I'm calling a sieve with
>
> 90-sieve.conf: imapsieve_mailbox2_name = *
> 90-sieve.conf: imapsieve_mailbox2_from = SPAM
> 90-sieve.
Hi
I'm having a problem related to Dovecot (version 2.2.36) sieves and I'm
not finding information.
I'm calling a sieve with
90-sieve.conf: imapsieve_mailbox2_name = *
90-sieve.conf: imapsieve_mailbox2_from = SPAM
90-sieve.conf: imapsieve_mailbox2_causes = COPY
90-sieve.conf: imapsieve_ma
