-
Hi, I have a Sieve script When the script is inlined in the config as follows it forwards mail as expected:
When the same script is referenced externally as described in the docs it fails:
with I verified that the file is readable via
The complete startup log with level `trace`
I am running on version I also considered using the Thanks for your considerations. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 2 replies
-
Hi, Sieve scripts are stored in the database by default and these types of settings do not support macros. You need to make the |
Beta Was this translation helpful? Give feedback.
-
Hi, thanks for your hints. With them I was able to produce a working config. However, it diverges from the format mentioned in the docs on Sieve Trusted Interpreter from which I would expect
to work without using macros. Might that be a documentation bug? The working config is:
|
Beta Was this translation helpful? Give feedback.
Hi,
Sieve scripts are stored in the database by default and these types of settings do not support macros. You need to make the
sieve.trusted.scripts
prefix local for this to work.