Our Mission
Every organization sends email, but few can say exactly what it sends, which applications send it, or which providers carry it. OutboxServer exists to change that.
We believe the best way to keep control over your outgoing email, or even just to see it, is to put a mail server you own between your applications and your email providers.
What You’ll Find
- Resources - Books, articles, courses, and talks on email delivery and security
- Security News - Incidents and research showing what goes wrong when email isn’t controlled
- News - Updates on OutboxServer and the ideas behind it
The Problem: Nobody Is Watching the Outbox
In most organizations, each development team wires its applications directly to an email provider. One team uses one provider’s SDK, another uses SMTP with credentials in a config file, and a third signed up for a different service on a company card. Each app holds its own API keys, builds its own retry logic, and logs (or doesn’t log) in its own way.
The result is that no one has the full picture. Ask how many applications send email on your organization’s behalf, which providers they use, or what went out last Tuesday, and the honest answer is usually “we’d have to check with every team.” When a key leaks, a provider has an outage, or a compromised app starts sending spam, you find out late and fix it in many places.
The Idea: A Server Between You and Your Providers
OutboxServer is a proxy for your outgoing email. Your applications, and the developers who build them, send messages to OutboxServer over your own network. OutboxServer holds the provider credentials, applies your policies, records what happened, and passes the message on to whichever provider you’ve chosen.
Because every message passes through one place that you own and operate:
- You can see everything. Which application sent what, to whom, through which provider, and whether it was delivered, bounced, or flagged. You don’t have to piece it together from each provider’s dashboard.
- You decide the rules. Allowed senders, rate limits, and recipient restrictions are enforced once, for every application, instead of trusted to each team.
- You own the provider relationship. Developers code against OutboxServer, not a vendor’s API. OutboxServer acts as an anti-corruption layer that keeps provider-specific details out of your applications, so you can add, switch, or fail over between providers without touching application code.
- You keep the keys. Provider credentials live in one hardened place instead of in every app’s configuration.
You don’t need to want tight control to benefit. Even if you never block a single message, simply having one place where all outgoing email is visible is a big improvement over not knowing.
Who It’s For
OutboxServer is for organizations with more than one application that sends email: password resets, one-time codes, notifications, receipts. It’s for platform and security teams who need to answer questions about outgoing email, and for development teams who would rather call one internal API than research providers and maintain email plumbing in every codebase.
Who We Are
OutboxServer is built by NimblePros. Have questions or want to talk about centralizing your organization’s email? Get in touch.