Re: Pigeonhole Sieve only runs scripts if in users' home directories, or if Sieve is purposely broken

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 mirroring the default configuration but in a non-home top-level-directory (TLD):

/var/spool/dovecot/home/m/user/morse/.dovecot.sieve -> /var/spool/dovecot/home/m/user/morse/sieve/default.sieve

which does not work, and as follows when it does (with the warning that specified sieve location is a file rather than a script):

/var/spool/dovecot/home/m/user/morse/.dovecot.sieve -> /var/spool/dovecot/home/m/user/morse/sieve

Am 15.05.2024 um 18:18 schrieb Douglas Morse via dovecot dovecot@dovecot.org:

However, if I then set sieve to file:/var/spool/dovecot/home/%1n/user/%n/sieve;active=file:/var/spool/dovecot/home/%1n/user/%n/.dovecot.sieve, again a default.sieve in each of these user’s centralized sieve directories, sieve scripts silently fail to run. No messages of any kind found in any log files.