Martin F. Foster wrote:
I'm new to dovecot's internals, it looks like it just needs some environment variables provided, but I'm puzzled as to how this is to be done. I've traced it through sievec.c -> sieve_tool_sieve_env -> sieve_tool_get_setting -> getenv() call.
Hmm, yeah, this is still somewhat stupid. Sievec does not use the global Dovecot config directly, which is something that can be solved for v2.0. Thus far this was no problem as the Sieve engine had no interesting settings to configure for command line use, but now apparently it does :)
More info:
- I've traced the process, there's no attempt to open or stat any dovecot.conf
- using tip dovecot-1.2, dovecot-1.2-sieve, pigeonhole-sieve-extdata.
I pulled+updated & rebuilt and confirmed the above behaviour just prior to sending this message.- The test scripts run because the test framework uses the test_config mechanism to provide sieve_extdata_dict_uri.
Any hints on how to get the dovecot.conf data to sievec?
Manual:
bash$ export SIEVE_EXTDATA_DICT_URI=file:/etc/dovecot/frop.dict bash$ /usr/local/bin/sievec -d -P sieve_extdata frop.sieve
Using dovecot.conf:
/usr/sbin/dovecot --exec-mail ext /usr/bin/sievec frop.sieve
Regards,
Stephan