Hi,

auth_cache_ttl docs

https://doc.dovecot.org/main/core/config/auth/caching.html

say:

"

We also try to handle password changes automatically: If user's previous

authentication was successful, but this one wasn't, the cache isn't used.

"

but seems that this doesn't work in such way for sieve_enabled flag changes.

So changing sieve_enabled from 0 to 1 means user still has to wait until cache expires and new value is noticed by dovecot... which is not desired.

Could sieve_enabled be also treated in similar way as incorrect authentication?

-- Arkadiusz Miśkiewicz, arekm / ( maven.pl | pld-linux.org )