[Feature]: Bulwark plugin to mange sieve filters by eg. Nextcloud mail app

[BlackAlpha700]

Description

If a sieve filter rule is set from outside bulwark (e.g. Nextcloud) , it is deleted when editing filter rules with bulwark.

Steps to Reproduce

1. Set a filter rule from outside Bulwark (e.g. Nextcloud) and save it
2. Open filter editor (not raw filter editor!) in Bulwark and edit a bulwark rule or create a new one
3. Save Bulwark rules
4. Open sieve filter rules raw - all other rules were deleted

Expected Behavior

External filter rules should not be harmed.

A possible solution is to set all Bulwark filter rules between special markers using comments (Idea inspired from Nextcloud):

### Bulwark Mail Filters - Start ### DON'T EDIT ###
...filter rules...
### Bulwark Mail Filters - End ### DON'T EDIT ###

Actual Behavior

All rules created outside from Bulwark were deleted

Bulwark Version

1.4.13

Stalwart Mail Server Version

No response

Browser

No response

Operating System

None

Screenshots / Screen Recording

No response

Relevant Logs or Error Output

Additional Context

No response

[chrilep]

This is not a bug. It is caused by sieve clients. Why adapt Bulwark to Nextcloud. Adapt Nextcloud to Bulwark instead! 😉

What about all the other Sieve clients with all their various ways to parse the raw data into their interfaces... 🙄

Maybe the plugin system could be used to have plugins which "adapt sieve filter set to nextcloud format" to mimic what Nextcloud does with raw data.

Other potential plugin candidates:

• SOGo
• GroupOffice
• SnappyMail
• Roundcube
• Afterlogic
• Various other clients or extension eg. for Thunderbird

[BlackAlpha700]

I think you missunderstood me. If I create filters in Nextcloud, Nextcloud only changes the rules between his own markers and does not harm any other rules created from the outside.
Bullwark should do it the same way. Bullwark should only shows his own rules in the gui - and any other rules should only be visible via raw editor. But Bullwark should not kill the complete sieve script existing on the sieve account.

I don't want Bulwark to adapt the rules of any other application and show them in his own editor!

[chrilep]

That's nice of Nextcloud then. From the past I remember Roundcube kills Nextcloud rules and vice versa. One should only use one webmail per server I guess.

There still is no standard for sieve filter parsing. Waiting for @rathlinus's feedback for this.

[BlackAlpha700]

I agree to you. But why should Bulwark do things bad (like Roundcube) if it's possible to manage his own filters by simple comments before and after (like Nextcloud)? ;-)

Anything that protects against data loss should be considered, especially when it seems so easy to implement. ;-)

[rathlinus]

How about managing it like this:

[BlackAlpha700]

This looks great and is much more than I expected! 😀

[BlackAlpha700]

I've installed the new version and it looks very good. One thing I'd found: The first Nextcloud-rule is recognized as Nextcloud and any other Nextcloud-rules are shown as external. Maybe it's enough to show the complete Nextcloud-block as one Nextcloud-rule-entry. Or what do you think?

My script looks like this:

### Nextcloud Mail: Filters ### DON'T EDIT ###
require ["imap4flags", "fileinto"];
### Nextcloud Mail: Filters ### DON'T EDIT ###

### Nextcloud Mail: Filters ### DON'T EDIT ###
# FILTER: [{"name":"Wetterwarnungen","enable":true,"operator":"allof","tests":[{"field":"from","operator":"is","values":["xxx@xxx.com"]}],"actions":

<...>

# PayPal
if address :contains :all "From" ["@paypal.de", "@paypal.com"] {
	addflag "$paypal";
}

<...>
### Nextcloud Mail: Filters ### DON'T EDIT ###

[BlackAlpha700]

Found a little Bug:

You save:

/* @metadata:begin
{"version":1,"rules":[{"id":"4482f7ca-9f1e-4f96-b8c1-82c19cabc28a","name":"Test","enabled":true,"matchType":"all","conditions":[{"field":"from","comparator":"contains","value":"test"}],"actions":[{"type":"star"}],"stopProcessing":false}]}
@metadata:end */

require ["fileinto", "imap4flags"];

# Rule: Test
if header :contains "From" "test" {
    addflag "\\Flagged";
}

# --- External rules (managed outside Bulwark) ---

### Nextcloud Mail: Filters ### DON'T EDIT ###

### Nextcloud Mail: Filters ### DON'T EDIT ###

<Nextcloud rules>

But it should look like this (watch the Nextcloud comments!):

/* @metadata:begin
{"version":1,"rules":[{"id":"4482f7ca-9f1e-4f96-b8c1-82c19cabc28a","name":"Test","enabled":true,"matchType":"all","conditions":[{"field":"from","comparator":"contains","value":"test"}],"actions":[{"type":"star"}],"stopProcessing":false}]}
@metadata:end */

require ["fileinto", "imap4flags"];

# Rule: Test
if header :contains "From" "test" {
    addflag "\\Flagged";
}

# --- External rules (managed outside Bulwark) ---

### Nextcloud Mail: Filters ### DON'T EDIT ###

<Nextcloud rules>

### Nextcloud Mail: Filters ### DON'T EDIT ###