BeMail
In productionOutbound-only mail transfer agent
An outbound-only mail server, built for senders who have to prove what left the building — and when, and to whom.
Why BeMail exists
Most mail servers are built to do everything: receive, store, compose, send. BeMail does one thing. It accepts authenticated submissions, enforces relay policy, and delivers outbound mail — with the authentication, throttling and audit properties that regulated senders need and general-purpose mail servers treat as add-ons.
It runs on our own infrastructure, collecting delivery evidence from our outbound relay fleet and generating the delivery notifications our recipients see. Moving the relay fleet itself onto BeMail is in progress — we run our own mail on it before we ask anyone else to.
BeMail is the one product here you can buy today. It has its own site, with the plans, the comparison and the trial.
In operation
What is running today
The precise scope of its use right now — not what it could do.
- Running on Braincap infrastructure as the audit collector for the outbound relay fleet
- Generating and delivering the delivery status notifications recipients receive
- Migration of the outbound relay fleet onto BeMail is in progress
- Available as a managed service or a self-hosted licence — see bemail.ro
Capabilities
What it does
Mail that only leaves over connections it trusts
MTA-STS and DANE enforcement, with STARTTLS policy per destination domain. A receiving server that fails its own published policy does not get the message.
Fully authenticated outbound
DKIM signing chosen by sending domain, SPF and DMARC policy per domain, ARC sealing and BIMI — with key generation and DNS records handled in the console rather than by hand.
Delivery that protects your reputation
Per-destination connection limits, backoff that recognises a rate limit for what it is instead of treating it as a failure, and shared throttling for domains that sit behind one provider.
Separate reputations, separate addresses
Outbound IP pools, so transactional mail and bulk mail do not share a reputation, and a new address can be warmed without risking an established one.
Bounces handled properly
Bounce classification, a suppression list that stays consistent across sending nodes, feedback-loop handling, and one-click unsubscribe.
An audit trail, not a debug log
Message bodies are never logged. Headers only, personal data redacted, recipients hashed — so the evidence of what you sent survives an audit without becoming a breach of its own.
Roadmap
What comes next
- Cutover of our outbound relay fleet onto BeMail
- Highly available console across both data centres
Interested in BeMail?
Plans, comparison and a trial are on the BeMail site. If you would rather just describe the problem, an engineer answers here.