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 dir is Trash. What is the most effective way of doing that?

Thanks

On 10/11/2021 12:24, Aki Tuomi wrote:

...

On 10/11/2021 14:22 João Silva <joaopfmlist@lipc.fis.uc.pt> 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.conf:  imapsieve_mailbox2_causes = COPY 90-sieve.conf:  imapsieve_mailbox2_before = file:/etc/dovecot/sieve/learn-ham.sieve

The SPAM folder have a autoexpunge set.

From the log analysis I have a very strong suspect that the sieve is being called when the mails from the Spam folder are expunged, is that possible? Is any other imapsieve_mailbox2_causes that could be used to prevent that?

Thanks I'd guess this is happening because mail is being moved from SPAM to Trash.

Aki