Deliverability · pre-send · client-side
The Spam Score Analyzer runs a client-side check inside the broadcast editor before you schedule. Scans the subject line, content structure, compliance elements, and spam-trigger words. Returns a score and actionable recommendations — fix it now, save the reputation hit later. One button: Analyze Spam Score.
Pre-send score
82/100
Findings · 3 minor
Subject line contains "free"
Consider rewording or pair with high-trust context.
Image-to-text ratio 68%
Add more body text to balance the visual emphasis.
Unsubscribe link present · physical address detected
CAN-SPAM compliance markers found.
What the analyzer checks
The analyzer runs three passes against your broadcast before you schedule. Each pass catches a different family of issues — subject-line patterns, content-structure heuristics, compliance markers. The combined score with per-finding recommendations lets you fix issues in seconds.
ALL CAPS, excessive punctuation, multiple exclamation marks, dollar signs, classic spam-trigger words (FREE, MAKE MONEY, ACT NOW, LIMITED TIME), excessive length, multiple emoji — every subject-line antipattern that correlates with spam. The score reflects how many flags fire across these dimensions.
Link-to-text ratio (too many links vs body text = link-farm pattern), image-to-text ratio (image-heavy emails can't be content-analysed by filters), HTML/text version pairing (multipart emails score better), body length distribution, and overall structural sanity. Helps catch the 'image-only Black Friday banner' antipattern.
Unsubscribe link presence, physical address in footer (CAN-SPAM requirement), sender-name clarity, reply-to validity. Mumara auto-injects the unsubscribe link via the %%unsubscribelink%% variable; the analyzer catches the case where you accidentally removed it. The compliance pass is mostly green-pass detection rather than catching mistakes.
The honest scope
The Spam Score Analyzer is an honest pre-flight check, not a deliverability oracle. It catches the obvious content-level mistakes that get a message flagged before ISPs even evaluate sender reputation. It does NOT predict ISP-specific filter behaviour, your sender-reputation score, or whether a particular recipient's mailbox will route the message to inbox vs spam.
What it does well: catches the 80% of avoidable content-level mistakes. ALL CAPS subjects, spam-trigger words clustered in close proximity, image-only emails, missing unsubscribe link, missing physical address — these are the issues where a quick edit before send saves you from a measurable inbox-placement drop. Run it on every broadcast before you schedule; the cost is one click.
What it doesn't do: simulate Gmail's actual content filter, predict reputation-based routing, account for the recipient's prior engagement history with your sender, or guarantee inbox placement. Those signals live at the ISP layer and depend on factors beyond any pre-send analyzer — sender domain reputation, IP reputation, recipient engagement patterns, complaint history. Mumara's broader deliverability stack — DKIM authentication on Sending Domains, FBL ingestion in Bounces & Spam, IP allowlists, suppression management — addresses those structural layers separately.
The mental model: Spam Analyzer catches the content-level mistakes a human reviewer would catch on a careful read. The deliverability stack handles the infrastructure-level signals that determine ISP-level reputation. Both matter; they cover different dimensions. Run the analyzer before every schedule; configure the deliverability stack once and trust it.
What it catches in the wild
These are the issues senders most commonly trip over — sometimes by accident, sometimes because the marketing copy demanded it. The analyzer surfaces each one with a recommendation. Fix or accept; the score updates either way.
"FREE", "Click here", "Make money fast", "Act now", "Limited time only" — the classic spam-trigger word list. Flagged in subject and body. Doesn't mean you can't use them; means you should use them sparingly and pair with high-trust signals.
SUBJECT LINES IN ALL CAPS!!! get flagged because that pattern correlates strongly with spam. Multiple exclamation marks, $$$ signs, and ALL-CAPS body sections all score against you.
Emails that are mostly links with little text get flagged — spammers cram link farms into short bodies. The analyzer catches when your link density exceeds typical-broadcast norms.
Emails that are 95%+ images with almost no text trigger spam filters because the text content can't be analysed. Image-to-text ratio gets flagged; the fix is adding meaningful text alongside the images.
CAN-SPAM and GDPR require an unsubscribe link in every commercial email. Mumara's %%unsubscribelink%% variable injects one automatically; the analyzer catches the case where you accidentally removed it.
Re: or Fwd: in subject lines that aren't actually replies, ALL CAPS, multiple emoji, excessive length, urgency words ("URGENT", "IMMEDIATE") — every classic subject-line antipattern gets surfaced.
The deliverability stack
Pre-send content checking is one of several deliverability signals Mumara manages. Each layer addresses a different failure mode; together they keep messages out of spam folders across every send.
What pre-send checks save you from
A single bad broadcast can ding sender reputation for weeks. Pre-send checks turn the 'oh no we should have caught that' moment into a 30-second fix instead.
A subject like "URGENT!!! BLACK FRIDAY DEAL INSIDE!!!" reads great in the meeting but lands in spam folders. The analyzer catches it; you change to "Black Friday savings inside" before send; open rates double.
Marketing designs a beautiful image-based broadcast with three lines of text. Most spam filters can't analyse images and flag the body as anomalous. The analyzer catches the image-to-text imbalance pre-send.
Removing the unsubscribe link by accident (template restructure, content drag-and-drop slip) means every send is non-compliant. The analyzer's compliance pass turns this into a green-pass check at every send.
"FREE GIFT with every order. ACT NOW! LIMITED TIME ONLY!" packs four trigger words into one sentence. The analyzer flags the cluster; you rewrite to "Order today and get a complimentary gift — offer ends Friday" and the score improves dramatically.
“The spam analyzer has become part of our pre-flight checklist for every broadcast. The first time it caught a missing unsubscribe link on a regulatory email, it paid for itself ten times over — that would have been a real CAN-SPAM headache. Now we run it before scheduling, every time.”
Verified review
Mumara customer
Common questions
Client-side. The analysis runs in your browser when you click Analyze Spam Score in the broadcast editor. No round-trip to Mumara's servers, no waiting on a queue, no rate-limited API call. Instant feedback. The trade-off: client-side means no access to live ISP feeds or sender-reputation databases — the analyzer can only check what's in the message itself.
No — and any analyzer claiming this is lying. Inbox placement depends on sender reputation, recipient engagement history, IP reputation, domain reputation, and ISP-specific filter behaviour. The Spam Analyzer catches content-level mistakes that get a message filtered BEFORE these reputation signals even matter. A perfect score means your content isn't shooting itself in the foot; it doesn't override the structural signals managed by the deliverability stack.
0-100, higher is better. The score reflects how many flags fired across the subject, content, and compliance passes, weighted by severity. A score of 80+ generally indicates ready-to-send content. Below 70 suggests significant content-level issues that warrant fixing before schedule. Below 50 is a clear stop-and-rewrite signal. The specific cutoffs aren't ISP-aware — they're heuristic guidance based on common spam-filter patterns.
No — spam filters use proprietary, frequently-changing rule sets. The analyzer covers the well-documented heuristics that the major filters share (trigger words, structural patterns, compliance markers). It will not catch ISP-specific quirks (e.g., Gmail's promotional-tab logic, Outlook's sender-network-graph signals). For comprehensive deliverability monitoring, supplement with seed-list testing from a dedicated deliverability tool.
No — the analyzer is informational. You can schedule and send a broadcast with any score (or without running the analyzer at all). The platform trusts you to make the call. Some senders deliberately use trigger words in regulated industries where the marketing copy demands it; blocking would be paternalistic. The platform's auto-stop discipline (Commercial-ESP feature on Packages) is reputation-based via bounce rate, not content-score-based.
Yes. The analyzer evaluates both HTML and Plain-Text variants of the broadcast. Spam filters typically score multipart emails better than HTML-only, but the text content of both versions is analysed for trigger words, missing compliance markers, and structural issues. Make sure both versions are clean.
Not built-in. For deeper testing, use a dedicated seed-list tool (Glock Apps, Mailtrap Inbox-Placement, GMass) that sends a test broadcast to a controlled set of mailboxes across providers and reports actual inbox-vs-spam placement. The Spam Analyzer is the lightweight pre-flight check; seed-list tools are the heavyweight diagnostic when you suspect a reputation issue.
Inside the broadcast editor — Broadcasts → edit any broadcast → Preview & Test section → Analyze Spam Score button. The score and findings render in the same panel, so the loop is tight: click, read, fix, click again. Spend 30 seconds on the analyzer for every broadcast you schedule and you'll catch the issues that matter.
Related
The broadcast editor is where the Spam Analyzer lives. Preview & Test section, Analyze Spam Score button, real-time feedback inside the same panel as Send Test Email.
Read moreThe structural deliverability layer — POP/IMAP bounce processing, FBL complaint ingestion, soft/hard classification. Spam Analyzer complements; doesn't replace.
Read moreDKIM + SPF authentication on your Sending Domains is the most important structural deliverability signal. Get this right and the spam-score game becomes much easier.
Read moreSuppression keeps you from re-sending to bounced / unsubscribed / complaint-flagged addresses. The hygiene layer that protects sender reputation over time.
Read moreCAN-SPAM, GDPR, CASL compliance markers. The analyzer's compliance pass dovetails with the platform's compliance features for end-to-end coverage.
Read more%%first_name%% personalization counts as a positive signal in some filters — pre-fill the recipient name and the email reads more legitimate than "Dear Customer". Pair Spam Analyzer with personalization.
Read morePer-recipient content variation via Spintax reduces content-fingerprint repetition — one of the structural patterns that contributes to ISP scoring across high-volume sends.
Read moreAI-rewritten content variation goes one step further than Spintax — fresh per-send variants. Combined with pre-send scoring, generates content that scores well by default.
Read moreMumara Campaigns · Spam Analyzer
The Spam Score Analyzer ships with every Mumara Campaigns plan — Self-Hosted and Mumara Machine. Client-side, one-click, in-editor. Catch the obvious content-level mistakes before a single recipient sees them. Pair with DKIM, SPF, and the broader deliverability stack.
