Export Thunderbird filters to server-side Sieve.

The tbrx beta reads supported Thunderbird version-9 filters from msgFilterRules.dat, without installing, starting, or modifying Thunderbird.

Check the beta requirements

You need Windows x64 or Linux x64 and supported Thunderbird version-9 filters. Server sync uses one resolved IMAP account per invocation.

Beta safety: tbrx never modifies Thunderbird data. It skips an enabled rule when it cannot preserve its meaning. Review partial-export diagnostics before using the result.

Install for your platform

Choose one installation method. tbrx reads your filters; srtx generates a local Sieve script.

Windows x64 · PowerShell

Requires Scoop. Add the Transiever bucket once.

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

Linux x64 · Bash

Requires Homebrew. These commands use the Transiever tap.

brew install SeWieland/transiever/tbrx
brew install SeWieland/transiever/srtx

Export a local Sieve script

Replace the quoted path with your Thunderbird profile directory. For multiple accounts, choose the intended account when prompted. Use a new working directory so you do not overwrite earlier exports.

PowerShell or Bash

tbrx export --profile "path/to/profile" --rules thunderbird-rules.json
srtx generate --rules thunderbird-rules.json --sieve thunderbird.sieve

The result is thunderbird-rules.json and thunderbird.sieve. These commands write local files without changing Thunderbird or your mail server. Review diagnostics, skipped rules, and target folders before deployment.

Preview a server sync

For a ManageSieve-capable provider, replace the filter-file path, host, and username. In an interactive terminal, a missing password is prompted without echoing it. The dry run does not write files or change server rules.

PowerShell or Bash

tbrx run --filters "path/to/msgFilterRules.dat" --sieve-host sieve.example.com --sieve-username user@example.com --no-optimize --dry-run

After reviewing a complete preview, run the guided workflow separately. It asks before deployment. Do not bypass partial-export checks without understanding the skipped rules.

tbrx run --filters "path/to/msgFilterRules.dat" --sieve-host sieve.example.com --sieve-username user@example.com --no-optimize

Undo a deployment when needed

This is a recovery action, not the next quickstart step. With the same server connection options, tbrx rollback restores the newest inactive SieveRuler backup and changes server-side filtering.

Read the tbrx CLI guide for connection options and rollback, and the compatibility guide for supported formats and profile layouts.