Email filtering for MSPs that manage many client domains

The MSP problem with email security

You support clients on a mix of platforms. Some are on Microsoft 365, some on Google Workspace, a few on a cPanel host they won't leave. Per-seat security products make every new hire a billing change. And DNS you configured carefully gets changed by someone else six months later.

iBlockSpam is built for that reality: a single inbound filtering layer, priced per domain, with checks that tell you when a client's setup has drifted.

What partners get

Program details are confirmed per partner. We'd rather agree terms that fit how you work than publish a scheme that doesn't. See how partnering works, and use our MSP spam filter pricing guide to model your own cost to serve per client domain.

One console for every client

The partner console lists every client account that has given you access. For each domain it shows filtering status, Domain Watch changes from the last 30 days, open lookalike domains, the DMARC pass rate from receivers' reports, subscription status and, once the daily sync has run, delivered and held mail. Filter to the clients that need attention, search by client or domain, or export the lot as CSV. You can try the console demo with sample clients.

• Consent first. A client gives you access by accepting your invitation or entering your partner code, and can switch you to read-only or remove you at any time.
• Work in the client's account. With full access you add and verify domains, run setup checks, manage DMARC monitoring and lookalike reviews, and open the filtering panel. Every action shows in the client's activity log under your name.
• New clients. Create an account for a new client; their owner takes ownership by setting a password, then chooses a plan and pays.
• Clear limits. Partners can't change a client's billing or security settings, and can't delete the account. There's no partner API, bulk import or consolidated partner invoice yet.

How it fits into your stack

One filtering layer across platforms

Every client domain's MX records point to our filtering servers. Spam, viruses, malware, phishing and spoofing are filtered before clean mail is delivered to the client's mail platform. Platform-specific steps differ:

• Microsoft 365: an inbound Partner connector with Enhanced Filtering for Connectors. See Microsoft 365 setup.
• Google Workspace: an inbound gateway configuration. See Google Workspace setup.
• cPanel/WHM: the correct mail exchanger setting for remote filtering. See cPanel/WHM setup.

Fewer tickets about "missing" email

Each user gets a personal quarantine and digest emails on a schedule (hourly, daily, a chosen weekday or custom), so users can release their own false positives. Admins have a domain-wide shared quarantine. Message history covers 30 days, which helps answer "did it arrive?" tickets quickly.

Advanced controls when a client needs them

Geographic filters, attachment-type filters, a Microsoft Office macro filter and custom domain rules are available in advanced settings. Approved and blocked sender lists can require sender verification to stop spoofed allow-listed senders.

Outage cover

If a client's mail server is unreachable, mail is spooled for up to 5 days and delivered when the server returns.

Use the free tools in your workflow

The Check tools work without an account and are useful on day one:

• Email Health Check for a quick domain review before a proposal.
• MX Lookup, SPF Checker, DMARC Checker and DKIM Checker for specific records.
• Email Header Analyzer, which runs in the browser, so client headers aren't uploaded.

A note on limits: an MX lookup shows where mail is routed, not proof that it's filtered. A DKIM selector we can't find is unknown, not broken.

Limits to plan around

• 100,000 inbound messages per domain per month.
• 400 MB maximum inbound message size.
• 500 outbound relay messages per domain per month, with DKIM signing and outbound filtering.
• Mail is processed in the United States. Check this against your clients' requirements; see security and data handling.

Switching clients from another filter

Moving a client from another gateway is a routing change, and routing changes need care. Our migration guide covers TTLs, staging, cutover and rollback.

Next step

Apply to become a partner with the number of clients you manage, the platforms involved and how you support your clients, or contact us first. We'll agree partner terms with you directly.