Hi everyone 👋
I’ve been working with email protocols (IMAP, SMTP) for a while — enough to know how painful they can be when you're building something serious. A lot of tools out there either:
- Don’t give you full control,
- Rely on external services like Redis or heavy databases,
- Or are simply too expensive to scale.
So I built RustMailer — clean, async, self-contained, and fast.
🛠 What is RustMailer?
RustMailer is a self-hosted email API engine, written in Rust, built to sync, send, and manage email with performance and reliability in mind.
No Redis. No Postgres. No cloud vendor lock-in.
It supports:
- ✅ Multi-account IMAP sync (UID-based, selective folders, date/window range)
- ✅ SMTP sending with connection pooling
- ✅ Webhooks powered by VRL (filter/edit payloads before sending)
- ✅ gRPC + OpenAPI interfaces with multi-version docs
- ✅ Built-in web UI for viewing messages & configuring accounts
- ✅ OAuth2 & proxy support for Gmail and other providers
And yes — it’s designed for real production use, not just a toy.
💰 Why RustMailer?
Because I needed something I could run cheaply, with full control, and no external dependencies.
RustMailer runs well on a small VPS with 512MB RAM and 1 CPU.
It’s source-available and requires a license only if you're using it in production beyond 10 accounts.
🤖 Built for Developers
I made RustMailer for people like me — backend developers who don’t want to rebuild email infrastructure over and over again.
If you’ve ever tried wiring together email sync, delivery, retries, webhooks, and token refresh, you know how chaotic it can get.
RustMailer handles all of that — so you can focus on building your app.
That’s it for now. I’ll write more about how it works under the hood soon (OAuth flow, sync strategy, webhook pipeline, etc).
If you have any questions or want to share your thoughts, feel free to ask in the comments — I’m happy to help and discuss!
GitHub:
github.com/rustmailer/rustmailerWebsite:
rustmailer.comDiscord:
https://discord.gg/3R4scWCsxK
Top comments (0)