On 15/05/2024 18:27, Douglas Morse via dovecot wrote:
My apologies, a small inaccuracy:
Below where I mention .svbin files being created, I incorrectly described what
is occurring. If the `sieve` is set to the default of users’ home directories
etc., the file `.dovecot.svbin` is created in the
Apologies, just to be completely explicit, I should have stated that of course
in every configuration I mentioned the `.dovecot.sieve` file always pointed to
the user’s main sieve script, wherever I may have placed it at the time.
So for example my centralized configuration is as follows when m
My apologies, a small inaccuracy:
Below where I mention .svbin files being created, I incorrectly described what
is occurring. If the `sieve` is set to the default of users’ home directories
etc., the file `.dovecot.svbin` is created in the user’s home directory. If
`sieve` is set to the centr
Hi,
Dovecot version is 2.3.19.1 (9b53102964) running on fully up-to-date Debian 12
(Bookworm) operating system.
For the life of me I cannot figure out how to get sieve scripts working
correctly in a central directory location. Calling them from users’ home
directories works fine (as describe
