Linus Rath e0bfdfa437 fix: stop filter rule data from breaking out into the Sieve script ...

The generator wrote several rule fields into the script unescaped. A
`*/` in a rule name ended the `@metadata` comment, a line break ended
the `# Rule:` comment, a custom header name could close its string, and
a size value was written as-is, so each could add live commands such as
`redirect "attacker@..."` to the active script. Rules reach the
generator from plugins holding `filters:write` and from imported filter
sets, not only from the editor.

The metadata JSON now escapes `*/` (JSON reads `\/` back as `/`), the
rule-name comment is kept on one line, header names are escaped like
other strings, and a size that is not a number becomes 0.

2026-09-26 14:56:01 +02:00

..

__tests__

fix: stop filter rule data from breaking out into the Sieve script

2026-09-26 14:56:01 +02:00

generator.ts

fix: stop filter rule data from breaking out into the Sieve script

2026-09-26 14:56:01 +02:00

parser.ts

fix: keep filter flags and folder targets when mail is moved

2026-09-22 20:09:19 +02:00