Skip to content
Mumara

Compliance

The do-not-send list, kept current automatically.

Suppress a single address, a whole domain, or an IP range — globally or per list — and let real-time DSN events keep it current. Hard bounces and complaints suppress within seconds, so a known-bad address never gets a second send.

Get started How it stays current →
suppression · global
EmailA single address

[email protected]

DomainA whole domain

example-dead.com

IPA range, CIDR-aware

203.0.113.0/24

checked before every sendauto-fed by DSN

How it works

Multiple types, multiple scopes, zero manual upkeep.

Three suppression types

Suppress a specific email address, an entire domain, or an IP range with CIDR support — the right granularity for everything from one complainer to a whole problematic domain or netblock.

Fed automatically by DSN

Hard bounces and feedback-loop complaints suppress within seconds of the event, in real time — not on the next processing cron. The list stays current with reality without anyone touching it.

Global or per-list scope

Apply suppression account-wide so it touches every send, or scope it to a single list when an exclusion only applies to one audience. Seed it by CSV or API on day one.

Why automatic matters

A suppression list is only as good as how fresh it is.

A manually-maintained do-not-send list is always behind: an address hard-bounces on Monday's campaign, but doesn't get added until someone runs the cleanup — so it gets battered again on Wednesday's. Each repeat send to a dead mailbox or a complainer chips at your reputation.

Because ONE classifies bounces and complaints at the gateway and feeds them into suppression in real time, the gap closes to seconds. The address that failed on this send is suppressed before the next one — no cleanup job, no window where you keep mailing the unmailable.

What it prevents

The reputation drain of stale lists.

  • Re-mailing hard bounces

    Sending again to a dead mailbox signals carelessness to mailbox providers. Real-time auto-suppression removes the address before the next send.

  • Mailing past complaints

    Continuing to email someone who hit "spam" is the fastest way to tank reputation. FBL complaints feed suppression automatically.

  • Losing your suppression list in a migration

    Switching platforms and leaving the do-not-send list behind re-mails people you'd already lost. CSV and API import bring it across on day one.

  • Over-broad or under-broad blocking

    Email-only suppression can't stop a whole abusive domain or netblock. Domain and CIDR-aware IP suppression give you the right blast radius.

What it covers

The right blast radius for every exclusion.

  • One complainer

    The problem
    A recipient hits "spam" or asks to be removed.
    What you suppress
    Suppress the single address — globally so it's honoured everywhere, or per-list when it only applies to one audience.

  • A dead domain

    The problem
    A whole company's domain has gone dark or hostile.
    What you suppress
    Suppress the entire domain in one entry, instead of chasing individual addresses one bounce at a time.

  • A bad netblock

    The problem
    Abuse or spam-trap activity from a known IP range.
    What you suppress
    Suppress a CIDR-aware IP range, so a whole problematic netblock is excluded at once.

  • A platform migration

    The problem
    You're moving in with a historical do-not-send list.
    What you suppress
    Seed suppression by CSV or API on day one, so you never re-mail the people you already lost elsewhere.
“The real-time part is what matters. On our old setup a hard bounce wouldn't leave the list until someone ran a cleanup, so we'd hammer dead mailboxes for days. Here the address that fails on this send is gone before the next one — our bounce rate dropped and our reputation stopped taking the hit.”

Verified review

Mumara ONE customer

G2

Common questions

What buyers usually ask.

What can I suppress?

A single email address, an entire domain, or an IP range (CIDR-aware) — covering everything from one complainer to a whole dead domain or a problematic netblock.

Does it update on its own?

Yes. Hard bounces and feedback-loop complaints feed suppression in real time, within seconds of the event — because ONE classifies them at the gateway rather than polling a mailbox. No manual cleanup job.

Global or per-list?

Both. Apply a suppression entry account-wide so every send respects it, or scope it to a single list when the exclusion only applies to one audience.

Can I bring my existing list?

Yes. Seed suppression by CSV upload or via the API, so a migration or a historical do-not-send list is in place before your first send — and you never re-mail people you already lost.

Related

Pages that pair with this one.

Mumara ONE · Suppression Management

Never send to a known-bad address again.

Email, domain, and IP suppression at global or per-list scope — seeded by CSV or API and kept current in real time by every bounce and complaint.

Get started See pricing