This is still not working in the way we expect. When I execute the following script:
Code:
#!/usr/bin/perl
$s='require ["fileinto", "reject", "tag", "flag"];
# tag special
if anyof (header :contains "subject" "special" )
{
tag "special";
stop;
}
';
$c="zmprov modifyAccount dflynn zimbraMailSieveScript '$s'";
system($c); I can then examine my account:
Which shows for the zimbraMailSieveScript attribute:
Code:
zimbraMailSieveScript: require ["fileinto", "reject", "tag", "flag"];
# tag special
if anyof (header :contains "subject" "special" )
{
tag "special";
stop;
} All of this looks correct. When I log into the web client, however, and go to my filters, I do not see the one I set through zmprov. If I then set up a filter through the GUI, the zimbraMailSieveScript attribute is overwritten; for example, below is what I see after adding a very simple filter through the web interface immediately after I ran the perl script above.
Code:
zimbraMailSieveScript: require ["fileinto", "reject", "tag", "flag"];
# test
if anyof (header :is "subject" "test" )
{
discard;
stop;
} It isn't immediately clear if the first filter is still working or not, but it is definitely not visible in the web interface. Am I still doing something wrong? Am I wrong to think that a filter I configure through zmprov in this way should be visible (and configurable!) through the web interface?
Thanks,
~Dave