Page 1 of 1

Issue setting zimbraAdminSieveScriptBefore at Server-Level

Posted: Fri Sep 10, 2021 6:56 pm
by deion
Hello,

I've been following the sieve filters tutorial (https://blog.zimbra.com/2021/07/zimbra- ... on-zimbra/) which states 'You can set zimbraAdminSieveScriptBefore per account, COS, domain or server'.

There was no issues settings the zimbraAdminSieveScriptBefore at the account-level, domain-level, and cos-level but I haven't had any luck at the server-level.

Code: Select all

cat /tmp/sieve.server | xargs -0 zmprov ms example.domain.com zimbraAdminSieveScriptBefore
ERROR: service.FAILURE (system failure: unable to modify attrs: object class violation - unable to modify attributes: ldap host=example.domain.com:389: attribute 'zimbraAdminSieveScriptBefore' not allowed)
Am I doing something wrong or is there an inaccuracy with the tutorial?

Thanks for the help!

Re: Issue setting zimbraAdminSieveScriptBefore at Server-Level

Posted: Sun Sep 12, 2021 2:45 am
by fs.schmidt
Hello,

The zimbraAdminSieveScriptBefore parameters is not implemented on server level.

Re: Issue setting zimbraAdminSieveScriptBefore at Server-Level

Posted: Mon Sep 13, 2021 9:01 pm
by deion
Thanks for the confirmation about setting zimbraAdminSieveScriptBefore at the server level. Can I ask how you retrieved the attribute information from the image. Did you run a script or utility that's already included with Zimbra?

Otherwise, the Zimbra Team should resolve the inaccuracy in the sieve filter tutorial. Does anyone know any alternative method to set a sieve filter at the server level besides setting the sieve filter on each individual account, domain, or cos.

Re: Issue setting zimbraAdminSieveScriptBefore at Server-Level

Posted: Tue Sep 14, 2021 5:44 am
by barrydegraaff
You can find them in
/opt/zimbra/conf/attrs/zimbra-attrs.xml

Re: Issue setting zimbraAdminSieveScriptBefore at Server-Level

Posted: Tue Sep 14, 2021 4:58 pm
by fs.schmidt
deion wrote:Thanks for the confirmation about setting zimbraAdminSieveScriptBefore at the server level. Can I ask how you retrieved the attribute information from the image. Did you run a script or utility that's already included with Zimbra?

Otherwise, the Zimbra Team should resolve the inaccuracy in the sieve filter tutorial. Does anyone know any alternative method to set a sieve filter at the server level besides setting the sieve filter on each individual account, domain, or cos.
Hello, I just ran the "zmprov desc -a zimbraAdminSieveScriptBefore" command. You can find this information on https://files.zimbra.com/docs/config-guide/index.html as well.