Proxmox Mail Gateway, operated by our team, sitting in front of whatever mail backend you already run. Inbound filtering, outbound abuse controls, a real quarantine portal.
Managed Mail Gateway is Proxmox Mail Gateway, deployed and operated by our team, in front of your existing mail server. We become your MX record. Inbound mail is scored, filtered, and either delivered to your backend or held in quarantine. Outbound mail picks up DKIM signing and rate limiting on the way through.
It fits Microsoft 365 and Google Workspace customers who want a real second layer of filtering with explicit rule visibility, organizations running their own Exchange or Postfix that need a gateway in front, and anyone whose current spam story is one tenant-wide setting they don't fully control. Pairs with Managed mailcow for customers who also want the mailbox layer operated by us.
Open-source mail security on our cloud, in front of whatever mail backend you already run.
Open-source mail security stack. ClamAV, SpamAssassin, custom rule sets, content scanning, and a quarantine portal.
Inbound mail is scored on multiple signals before it ever reaches your mailbox server. Rules tune per domain or per recipient.
DKIM signing, per-sender rate limiting, and abuse detection on the way out. Catches a compromised account before the receiving side does.
Provisioning is ours. We stand up the gateway with your domains configured, point it at your existing mail backend, configure inbound and outbound routes, set up the per-user quarantine portal with SSO where you want it, and run a staged cutover so production MX flips when you're ready and not before.
Day-2 operations are ours too. Gateway updates, signature and rule updates, antivirus database refreshes, DKIM key rotation, and quarantine pruning run on a schedule we hold. Deliverability is monitored from outside: backscatter, queue depth, sender-reputation signals, and bounce patterns are tracked so a problem gets caught before users start filing tickets.
Rule tuning is collaborative. False positives get reviewed and the rule set adjusts. Recurring spam patterns get blocked at the gateway instead of by every user individually. If you ever need to roll back to direct MX during a debug session, the path is documented and the change is a DNS update away. Coverage and credit terms are written into the SLA so the bar is in writing.
The ones we hear from teams sizing a real spam-filtering layer instead of a checkbox one.
No. The gateway sits in front of whatever mail backend you already run. Your mailboxes stay where they are. We become your MX record; the gateway filters and forwards clean mail to your existing server, with quarantines and rejections handled in our portal. Your users keep their inbox; you change where the internet drops mail off.
Different engine, different vantage point, and a separate quarantine you control. Built-in filtering in M365 or Workspace is one set of rules tuned for the median customer. A gateway gives you a second layer in front, with full rule visibility, per-domain and per-recipient tuning, and explicit DMARC enforcement before mail crosses into your tenant. Outbound controls aren't usually available in suite-level filtering at all.
We provision the gateway with your domains pre-configured and a test MX you can route a copy of traffic to first. Once you're satisfied with the filtering, the cutover is a DNS change to point production MX records at us. Forwarding to your backend stays continuous through the change; there's no period where mail goes nowhere.
Yes. Each user gets access to their own quarantine through a web portal we run. They can review held messages, release the ones that were caught by mistake, and add safe senders. Admins see the full quarantine across all users and tune the rules from the same UI. Daily digest emails are configurable per user or per domain.
Tell us your domains, your mailbox count, and what you're running on the backend. We'll quote a gateway sized to your traffic and a cutover plan to land it cleanly.
Get in Touch