Email deliverability is one of the hardest operational problems in shared hosting. One compromised account sending spam from your server can get the IP blacklisted, and suddenly none of your customers' emails reach the inbox. The damage is immediate, the delisting process is slow, and the support tickets pile up.
The problem has gotten harder over the past two years. Google, Yahoo, and Microsoft now enforce SPF, DKIM, and DMARC authentication for inbound email. Managing per-domain authentication across hundreds of domains on a shared server is a real operational burden, and most hosting control panels don't handle it natively. The result: email deliverability now requires specialized tooling that goes beyond what a standard server setup provides.
Today, we're announcing Imunify Email Gateway, a cloud-based outbound email relay built for hosting providers. It's entering private beta, and we're looking for hosting companies to help us test it.
There are two complementary approaches to email protection in a hosting environment. Each solves a different part of the problem, and they work well together. But each one also stands on its own.
On-server filtering scans every outbound message before it leaves the server. It catches spam and compromised account abuse at the source, stopping bad email before it ever reaches the internet. This is what Imunify Email does. It reduces the volume of problematic outbound email, protects the server's sending reputation, and gives hosting providers visibility into what's happening across their accounts.
A cloud email relay takes a different approach. Instead of filtering email on the server and then delivering it from the server's IP, the relay routes outbound email through its own managed IP pool. Per-domain authentication (DKIM, SPF, DMARC) is handled automatically. The hosting server's IP never appears in email headers.
This solves a problem that on-server filtering alone cannot: even with excellent filtering, the server's IP is still the one delivering mail. If that IP ends up on a blocklist for any reason, every customer on the server is affected. A cloud relay removes the server from the delivery chain entirely, so the server's IP reputation is never at stake. The relay also adds its own layer of filtering, bounce handling, and deliverability optimization.
On-server filtering keeps bad email from entering the relay. The relay ensures that everything delivered goes out from clean, authenticated IPs. Together, they cover the full email chain from composition to inbox.
If you already use Imunify Email, the Gateway adds managed delivery and IP isolation on top of your existing filtering. Because on-server filtering catches spam and abuse before email reaches the relay, less unwanted volume enters the Gateway in the first place.
If you don't use Imunify Email, the Gateway works as a standalone outbound relay with its own filtering and authentication.
Either way, your email deliverability improves.
Imunify Email Gateway is a cloud-based outbound email relay and filtering service for hosting providers. You redirect your server's outbound email through the Gateway via a lightweight cPanel or Plesk plugin. The Gateway filters, authenticates, and delivers email from its own managed IP pool.
What this means in practice:
That's it. Once the plugin is configured, outbound email flows through the Gateway automatically.
We're opening a limited private beta for Imunify Email Gateway. We're looking for hosting companies who want to test the Gateway with real production traffic and help us refine the product before general availability.
What the beta includes:
Who can participate:
We'll hand-select beta participants to ensure a diverse set of server environments and configurations. Spots are limited.
What we're looking for from you:
Real-world traffic, honest feedback on setup and deliverability, and help identifying edge cases we haven't encountered yet. This is a working beta. We want to get this right before we open it up more broadly.
Apply for the private beta
We'll review applications and follow up individually with selected participants.