MailMum for Telecom & Hosting Providers / ISPs

If you run mail infrastructure at scale, or on behalf of many downstream customers, a single shared blacklist doesn’t fit your model. MailMum is multi-tenant by design.

Built for wholesale and reseller operations

• One MailMum deployment, many isolated accounts and servers, each with independently managed blacklists and whitelists.
• Segmented, not siloed. Abuse handling, IP-reputation policy, and audit reporting are segmented per customer, but centrally operated from a single installation.
• Role-gated access. Each account has its own admins and viewers, so customer teams can manage their own rules without seeing another customer’s data.
• A full audit trail per account, useful when a downstream customer asks “what happened to my traffic and why.”

Scale

The ingestion pipeline (queue → scheduled importer → background processing) is built to absorb bursts of DNS traffic — up to 1000 requests/second in batches — without blocking the DNS response path that your customers’ mail servers depend on.

Setting it up

Each downstream mail server gets its own identifier and points its RBL check at MailMum, the same integration pattern used for any public list. See the MailMum documentation for the technical setup steps, and the MailMum Whitepaper for the reasoning behind the multi-tenant model.