mirror of https://github.com/spartanz51/tutabridge.git synced 2026-06-24 10:54:32 +02:00

Files

T

Anthony MandGitHub e58ee86bed Restructure into Cargo workspace with Tauri desktop GUI (#1 )

Split the bridge into a tutabridge-core crate, a Tauri v2 desktop app
(src-tauri) and a React/TS UI (ui), keeping the CLI entrypoint at the
workspace root.

Add encrypted local storage (SQLCipher metadata index + encrypted .eml
files) so mail persists across launches and only the delta is fetched.

Wire the bridge to the Tuta Rust SDK via the tuta-repo submodule
(batch loading, MailDetailsBlob reading, interactive 2FA login).

Implement SMTP sending: build the draft and send it through Tuta's
DraftService/SendDraftService, mirroring the web client (body in
compressedBodyText, non-empty sender/recipient names, populated
SendDraftParameters). Add unit tests for the draft/send payload building.

2026-05-27 14:03:15 +02:00

2.2 KiB

Raw Permalink Blame History

TutaBridge

Architecture

TutaBridge is an IMAP/SMTP bridge for Tuta encrypted email. It exposes a local IMAP+SMTP server that mail clients (Thunderbird, etc.) connect to.

Core principle: syncer-driven, store-backed

Tuta API  ←──  Syncer (background)  ──→  MailStore (in-memory)  ←──  IMAP server  ──→  Thunderbird
                                                                 ←──  Tauri UI (stats)

The syncer (sync.rs) runs independently in a background tokio task. It pulls emails from the Tuta API and populates the MailStore.
The IMAP server (imap/) ONLY reads from the MailStore. It NEVER makes API calls for reads.
The only IMAP→network calls are mutations: marking read/unread (STORE \Seen) and trashing (EXPUNGE).

Syncer two-phase cycle

Phase 1 (fast, ~3s): Sync mail lists for ALL 6 folders. Store gets populated with mail metadata immediately.
Phase 2 (slow, ~2min): Prefetch mail details (body) one by one with rate limiting (150ms/mail). Bodies become available progressively.
Wait 60s, repeat.

Testing

Unit tests

cargo test --workspace        # 113 bridge tests + SDK tests

Integration test (IMAP)

Requires a running bridge instance (either cargo run or ./dev.sh for GUI).

python3 scripts/test_imap.py

This connects to the local IMAP server and verifies: TLS, auth, folder list, mail count, body fetch, search. It reads the bridge password from ~/Library/Application Support/tutabridge/config.toml automatically.

Manual Thunderbird test

Start bridge: ./dev.sh (GUI) or cargo run (CLI)
Wait for "Pre-fetching N mail details for Inbox" in logs
In Thunderbird: IMAP server 127.0.0.1:1143 SSL/TLS, SMTP 127.0.0.1:1025 SSL/TLS
Username: your tuta email, Password: bridge_password from config
Accept self-signed cert

Build

cargo build                   # CLI + GUI
cargo build -p tutabridge-core  # Core library only

SDK branches (tuta-repo submodule)

feat/rust-sdk-blob-read — blob element reading (MailDetailsBlob)
feat/rust-sdk-load-multiple — batch entity loading (load_multiple)
Locally, feat/rust-sdk-blob-read has both merged for development

2.2 KiB Raw Permalink Blame History