Support for managing Sieve filters through JMAP with a ManageSieve backend?

[dververis]

Hi,
first of all, thanks for the legacy proxy — I've successfully set it up in front of an existing Dovecot/Postfix installation and it works really well with Bulwark Webmail.
My current setup involves a Dovecot and a Postfix server.
I configured the sieve provider to point to Dovecot's ManageSieve service on port 4190.
What I'm trying to understand is whether the proxy currently supports managing normal Sieve filter rules from Bulwark Webmail through the ManageSieve backend.

I noticed that the proxy already has ManageSieve support, but I couldn't get the Filters section to appear in Bulwark Webmail.
So my questions are:

1. Is managing regular Sieve filters through the legacy proxy already supported?
2. If yes, is there some additional provider or Webmail configuration that I may have missed?
3. If not, is the current ManageSieve integration intended only for specific functionality such as vacation responses, or is general Sieve/

JMAP support planned?
Thanks!

[NotAFlightRisk]

No, not with the current proxy (latest image, commit d34a01b) - there's no config you've missed. It only uses ManageSieve for the vacation responder and doesn't implement any of the SieveScript/* methods the Filters page needs.

Bulwark 1.12.0 only shows Filters when the session advertises urn:ietf:params:jmap:sieve (client.ts). The proxy advertises its own urn:bulwark:params:jmap:sieve instead, which the README calls the "vendor capability used by the vacation handler" (README).

Heads up if you manage filters some other way (Roundcube etc): ManageSieve only has one active personal script, and the vacation responder takes it. Saving vacation as on in Bulwark switches your filter script off, and saving it as off leaves none active (vacation.ts). Logging in or opening settings doesn't touch it, only hitting save on the Vacation page.