This looks close to how it should be (judging by the same attribute format on my production Zimbra server, which was created using the filters GUI in the web interface). Unfortunately, I still don't see any filters in the web interface for this account, and I still can't create new ones (I get the error mentioned in my previous post).

The filters UI doesn't really support this (yet), but you can specify the comparator when submitting the raw sieve filter via zmprov. After adding this filter, messages with uppercase "STUFF" in the subject get the "STUFF" tag, but messages with lowercase "stuff" don't:

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.

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?

For the record, while it might be a little annoying to have to restart Tomcat to make this show up to the web interface, what we're doing here is scripting for a large number of users the migration of their Cyrus/Horde filter rules into Zimbra. Once we have the process working and tested, we'll probably do it all at once, in which case restarting Tomcat once to propagate the changes to the web interface is a reasonable thing to do.

As long as we can use zmprov to migrate the filters and make them visible through the web interface somehow, that's good enough for me. This might be a nice thing to 'fix' in a future release, but as we've noted elsewhere in this thread zmprov isn't really the right tool to begin with. I'd rather use zmprov and restart Tomcat than parse several thousand filter rules and rewrite them into something that zmmailbox understands.

The filters UI doesn't really support this (yet), but you can specify the comparator when submitting the raw sieve filter via zmprov. After adding this filter, messages with uppercase "STUFF" in the subject get the "STUFF" tag, but messages with lowercase "stuff" don't

Does this mean that if I import a filter using zmprov that contains a (for example) :comparator directive, the filter will work but won't show up in the ZWC GUI?

I ask because I've been able to get some filters to work properly (properly meaning I import them using zmprov ma account@domain zimbraMailSieveScript ..., and I can both test that they work and edit them from the ZWC), and some that do not work. In some cases, the zmprov import seems to work, but the filter doesn't appear to be active, and more importantly it breaks the filter portion of the web client for the affected account - not only can I not see the newly added filter(s), I get an error if I try to create a new one.