On 05/06/2020 05:29, ellie timoney wrote:
> Hi David,
>
>> Is it possible to enable the "editheaders" sieve extension? if so, how?
>
> Not in 3.0, but it's available in 3.2
I plan to update to 3.2 once I have 3.0 working in my environment (I'm
migrating an existing legacy 2.5.3 server).
>
>> Are sieve actions logged anywhere, e.g. to aid with debugging?
>
> Generally? I don't know. Maybe if you increase your syslog log level to
> "debug" and add "debug: yes" to your imapd.conf?
>
> 3.2 has an experimental "x-cyrus-log" extension, which adds an action that
> produces a log line. You probably don't want to allow this for user-supplied
> sieve scripts, but if you have some sort of "sieve builder" system that your
> users use (rather than uploading their own handcrafted sieve scripts), then,
> if you were running 3.2, this extension could be useful. On the master
> branch, and therefore in the next major release (2021), this extension will
> be formalised as "vnd.cyrus.log".
thanks. I have a number of questions around logging; I'll post another
question about that.
----
Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
To Unsubscribe:
https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
