Re: dsync does not like sieve

Hi,

Thank you for your suggestion. Yes, this is more or less what I’ve done and the spam filtering is working correctly. But then, the backup is failing with the error message I wrote below. I can make the backup work by adding the following lines :

sieve_script personal { path = ~/sieve active_path = ~/.dovecot.sieve }

But it then makes spam filtering fail, probably because my users are virtual and do neither have a sieve nor an active_path path.

Any other suggestion ?