Transiever.SieveRuler 1.1.5

Transiever.SieveRuler library

The library exposes:

• RuleDocument and RuleDefinition as the JSON API.
• Schema v1 conditions, exceptions, explicit actions, and the simple targetFolder shortcut.
• JsonRuleSerializer with RuleDocument file and stream APIs.
• Action-aware rule optimization and Sieve generation.
• Strict Sieve import, byte-preserving composition, and source-aware reconciliation.
• Typed preview, deployment, rollback, and history workflows over Transiever.ManageSieve.

Install

dotnet add package Transiever.SieveRuler

The package is available on NuGet.org. For a tool-selection guide and local/export workflow, see Generate and deploy Sieve rules from JSON in .NET.

The package includes the v1 JSON schema. All asynchronous I/O accepts CancellationToken.

GitHub releases publish this library to NuGet.org. Release versions are calculated by semantic-release and are not committed into the project file.

Expected preview, deployment, rollback, and history outcomes use typed statuses. Malformed inputs, stale state, I/O, and protocol failures throw.

Policy Notes

The library owns the provider-neutral workflow behavior behind preview, deployment, rollback, and retained-history operations. The canonical workflow description lives in the synchronization policy. Rules contract and provider metadata details live in the rules and metadata guide.

In short:

• Preview writes separate reconciled ownership and rendered candidate rule documents.
• Preview capability checks accept both advertised ManageSieve extensions and active-script require evidence.
• Deployment plans are version 1 and preserve the current active script name by default.
• Active-script replacement creates a server-side backup before mutation.
• Rollback restores that backup, or reactivates the recorded source script when no backup was created.
• Generated managed rules include Open-Xchange-compatible ## Flag: comments with stable IDs and rule names for provider UIs.
• Deployment can prune inactive history in SieveRuler's reserved history namespace, keeping the oldest backup plus the newest 5 remaining history scripts by default.
• History restore creates a fresh backup before changing active filtering.
• History restore can restore the original unmanaged or no-active state when a retained marker exists.

SieveRuler is designed to stay Sieve-provider agnostic. However, provider UI metadata compatibility is currently only validated against mailbox.org's Open-Xchange implementation.

The library does not read environment variables or access Console.