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.
0 replies
-
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.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi,
I have a Sieve script
redirects
that is supposed to redirect some mail. Because the mapping from addresses to their destination is supposed to be private and will be long I want to move the script in its own file to separate it from the config. The script will then be deployed in a different way.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
ERROR Configuration build error (config.build-error) details = "Build error for key "sieve.trusted.scripts.redirects.contents": Failed to compile Sieve script: Expected token "command" but found "file" at line 0, column 0."
at service startup time and mail is not forwarded.I verified that the file is readable via
The complete startup log with level `trace`
I am running on version
v0.9.2
.I also considered using the
include
feature of Sieve (RFC 6609) to load the file but that seems to expect an already loaded script and not a file.Thanks for your considerations.
Beta Was this translation helpful? Give feedback.
All reactions