Mail rules on your server. Sieve tools in your code.

Move supported Outlook and Thunderbird filters to server-side Sieve, or build Sieve and ManageSieve into your .NET application.

Move your mail rules

Give your mail client the evening off. Move supported filters to the server, starting with a local export and a review before you sync.

Build with .NET

Take the part that fits your code. Both .NET 10 libraries have a short C# quickstart to get you going.

Check your provider before you sync

Sieve runs mail filters on the server. ManageSieve is the separate protocol for managing those scripts remotely.

No ManageSieve? Export a local Sieve script if your provider accepts one. Without Sieve support, your provider cannot run Transiever-generated rules.

mailbox.org

Validated with mailbox.org and its Open-Xchange rule editor.

Check Sieve and ManageSieve requirements before changing server rules.

Already working with Sieve?

Use the msieve command-line quickstart to inspect a server directly, or generate a script from JSON with srtx.

How server sync works

From your mail client

Classic Outlook · olrx

Thunderbird · tbrx

Through the shared tools

SieveRuler
Reconcile, preview, back up, and roll back.

ManageSieve
Connect to a compatible server.

On your mail server

Sieve applies the rules before mail reaches your devices.

When ManageSieve is available, your client rules go through one shared pipeline to a compatible mail server.

A small project, with a human behind it.

Transiever started with practical mail problems I wanted to solve for myself. It is still a personal hobby project, shaped by those problems.

I use AI heavily for research, design exploration, implementation, debugging, and documentation. I develop the project using test-driven development and review the work myself. Its direction, behavior, and quality remain my responsibility.