Convert classic Outlook rules to server-side Sieve.

olrx exports supported classic Outlook receive rules so that a Sieve-capable mail server can apply them before mail reaches your phone, webmail, or another desktop client.

Check the fit

You need Windows x64 and configured classic Outlook. Your provider must accept Sieve files for server-side filtering, or expose ManageSieve for remote synchronization.

Review the export: only supported receive rules can be converted. Read the diagnostics and inspect the generated script before deployment.

Install on Windows

With Scoop already installed, add the Transiever bucket once. Install olrx for Outlook export and srtx for local Sieve generation.

PowerShell

scoop bucket add transiever https://github.com/SeWieland/Transiever.ScoopBucket
scoop install transiever/olrx
scoop install transiever/srtx

Export a local Sieve script

Use a new working directory so you do not overwrite earlier exports. These commands read Outlook rules and write local files; they do not change your mail server.

PowerShell

olrx export --rules outlook-rules.json
srtx generate --rules outlook-rules.json --sieve outlook.sieve

The result is outlook-rules.json and outlook.sieve. Review export diagnostics and folder names in the generated script before using it with your provider.

Preview a server sync

For a ManageSieve-capable provider, replace the example host and username below. In an interactive terminal, the tool prompts for a missing password without echoing it. The dry run does not write files or change server rules.

PowerShell

$env:TRANSIEVER_SIEVE_HOST = "sieve.example.com"
$env:TRANSIEVER_SIEVE_USERNAME = "user@example.com"
olrx run --no-optimize --dry-run

After reviewing the preview, run the guided workflow separately. It asks before deployment and creates a server-side backup when replacing the active script.

olrx run --no-optimize

See the olrx CLI guide for authentication options, rollback, and workflow details, and the Outlook mapping guide for supported rules.