Catch a reputation slip before it costs you the inbox.

The signals that predict deliverability trouble: bounce rate (hard and soft), complaint/spam rate, delivered rate, open and click rates, unsubscribe rate, per-list bounce and spam rates, blacklist status for both domains and IPs, and authentication health — DKIM, SPF, and redirect-domain validation. Each rule scopes to a specific sending domain, a sending node, or the whole account.

Each criterion uses a plain comparison — greater than, less than, equal, not equal — against a value you set. You can put several criteria in one rule and choose whether the rule fires when ALL of them are true or when ANY single one is. That lets you write both broad guardrails ('any one of these means stop') and precise ones ('only when all three line up').

A rule can suspend a sending domain, suspend specific IPs, suspend a contact list, or suspend the account — and notify the account owner by email and in-app. You decide which actions run automatically and which queue for approval, so the guardrail is always on while the high-stakes levers stay under your control.

Beyond any rule you set, Mumara ONE protects the IP automatically: it throttles the sending speed on that IP and eases it back into a warm-up ramp, slowing volume to a pace the IP's current standing can sustain. Sending keeps going — just at a safe, reduced rate — so the IP rebuilds trust with the mailbox providers instead of compounding the damage at full volume. As the signals recover, the throttle lifts and full speed returns.

Mumara ONE does not allow sending from blacklisted domains. If one of your domains lands on a blacklist it's automatically suspended, and a domain that stays blacklisted puts the whole account in danger — up to account-level suspension. It's a zero-tolerance protection: one compromised or abused domain can't be allowed to drag down every other sender on the platform, including your own other domains. Keep your domains clean and authenticated and you'll never see it trigger.

Pending Actions are the moves you've configured to require approval — they queue up with their trigger and wait for you to apply or dismiss them. Recent Actions is the log of everything that already happened, including auto-applied actions, each with its trigger, timestamp, and outcome. Together they give you a guardrail that acts fast on small things and checks with you on big ones.

You choose the cadence per rule — evaluate continuously as data arrives, daily, or weekly. Fast-moving signals like blacklist status or complaint spikes suit continuous or hourly evaluation; slower-moving hygiene checks can run daily or weekly to avoid noise.

Only if you configure it to. Account-level suspension is exactly the kind of high-stakes action most operators route through the approval queue rather than automating. You're in control of which actions execute automatically and which wait for a human — and every action is logged with the rule and data that triggered it.

Yes — it's designed for them. Per-IP and per-pool reputation is exactly what dedicated infrastructure puts in your hands, and Reputation Monitoring is how you keep that infrastructure healthy automatically. Rules can target individual IPs, the domains sending through them, or the lists feeding them.