---
title: "MailMum for MSPs Running Mail for Clients"
description: "The account/server hierarchy maps directly onto client and their mail servers, so an MSP can apply a baseline blacklist per client and hand over a clean report of what was blocked and why."
url: "https://mailmum.io/for-msps/"
---

# MailMum for MSPs Running Mail for Clients

Managing mail security for multiple clients usually means juggling separate
tools, separate lists, and separate reporting per client. MailMum's account
and server model maps directly onto how you already work.

## How it fits your model

* **Account = client, servers = their mail servers.** Apply a baseline
  blacklist across a client account, then let individual mail servers add
  their own exceptions.
* **Clean, isolated reporting.** Hand a client a clear picture of what was
  blocked and why — without exposing any other client's data.
* **Role-gated admins and viewers per account**, so client-side staff can be
  given visibility without full control, or vice versa.
* **Analytics per server and per account** — blocked-vs-passed traffic,
  hourly volume, and blacklist match counts — so you can show clients
  real numbers, not just "we're handling it."

## Getting a client onboarded

Create an account for the client, add their mail server(s), and point each
server's RBL check at MailMum — see the
[MailMum documentation](https://docs.mailmum.io/) for the Postfix/Exim/etc.
configuration steps. From there, baseline rules and per-server exceptions are
managed entirely inside MailMum.

Read the [MailMum Whitepaper](https://mailmum.io/whitepaper) for more on how the account/server
hierarchy works.