SpamAssassin Score: What It Means and How to Lower It
What a SpamAssassin score means, why 5.0 marks spam, the current points for 14 common rules, and how to lower your score before a cold email goes out.

The short answer: A SpamAssassin score is the total of points an email collects from hundreds of spam tests. Lower is better. At the default setting, 5.0 or more marks the email as spam. A clean, authenticated cold email usually scores well under 2, and authentication can push it below 0.

What a SpamAssassin score means
SpamAssassin is an open-source spam filter from the Apache Software Foundation; the latest release is 4.0.2, from August 2025. It runs each email through hundreds of tests and adds up the points for every test that matches. Some tests add points, and some, like a valid DKIM signature, take points away.
Score | What it means |
|---|---|
Below 0 | Strong good signals, usually valid authentication |
0 to 2 | Healthy: typical for clean, authenticated email (our guidance) |
2 to 5 | At risk: a stricter server may flag it |
5 or more | Spam at SpamAssassin's default setting |
8 to 10 or more | Spam even on the more relaxed settings SpamAssassin suggests for ISPs |
The 5.0 cutoff is the default for a setting called required_score. SpamAssassin's own docs call 5.0 "quite aggressive" and suggest ISPs use 8.0 or 10.0 instead (SpamAssassin configuration docs). So the same email can pass on one server and be flagged on another.
Is a higher SpamAssassin score better? No. In SpamAssassin's own score, lower is better and there is no maximum. Some testing tools flip the scale: mail-tester, for example, shows a score out of 10 where higher is better (mail-tester FAQ). Check which scale your tool uses before you panic.
How SpamAssassin calculates the score
Every test, called a rule, has a point value. The final score is the sum of the points of every rule that matched. No single rule decides the result; a few small problems add up.

Why the same rule can have 4 scores
A rule can list up to 4 point values, and the one that counts depends on how the server runs SpamAssassin:
Score set | When it's used |
|---|---|
Set 0 | Bayes learning off, network tests off |
Set 1 | Bayes off, network tests on |
Set 2 | Bayes on, network tests off |
Set 3 | Bayes on, network tests on |
Network tests check things like blocklists; Bayes learns from mail the server has already seen. This is why two testers can show different points for the same rule. SpamAssassin's maintainers tune the default scores to produce "roughly 1 false positive in 2500 non-spam messages" at the 5.0 threshold (SpamAssassin rules file).
14 SpamAssassin rules cold emails trigger, with their points
The points below come from SpamAssassin's current rules file. Where a rule has 4 scores, the table shows set 1 (network tests on) and set 3 (Bayes and network tests on), the two most common setups. Rule scores change when SpamAssassin updates its rules, so treat them as a guide.
Rule | Points (set 1 · set 3) | What triggers it | How to fix it |
|---|---|---|---|
URIBL_DBL_SPAM | 2.5 · 2.5 | A link points to a domain on Spamhaus's domain blocklist | Remove the link, or clean up and delist the domain |
URIBL_BLACK | 1.7 · 1.7 | A link points to a domain on the URIBL blocklist | Check every link, including your tracking domain |
DMARC_REJECT | 1.797 · 1.797 | The email fails DMARC and the domain's policy is reject | Fix SPF and DKIM alignment for the From domain |
DMARC_QUAR | 1.198 · 1.198 | The email fails DMARC and the policy is quarantine | Same: align SPF or DKIM with the From domain |
MISSING_DATE | 1.396 · 1.360 | No Date header | Send from a real mail client or tool that sets it |
HTML_IMAGE_ONLY_24 | 1.282 · 1.618 | An HTML email that's mostly images with little text | Use text; drop banners and image-only layouts |
RDNS_NONE | 1.274 · 0.793 | The sending server's IP has no reverse DNS | Send through a provider that sets reverse DNS |
SPF_SOFTFAIL | 0.972 · 0.665 | The sending server isn't fully allowed by your SPF record | Add your sending service to SPF |
SPF_FAIL | 0.919 · 0.001 | The sending server isn't allowed by your SPF record | Add your sending service to SPF |
SUBJ_ALL_CAPS | 0.5 | The subject line is all capitals | Write the subject in sentence case |
MIME_HTML_ONLY | 0.1 | HTML with no plain-text version | Send plain text, or HTML with a plain-text part |
DKIM_INVALID | 0.1 | A DKIM signature is present but broken | Republish the DKIM record your tool gives you |
DKIM_VALID | −0.1 | A valid DKIM signature | Keep DKIM on |
DKIM_VALID_AU | −0.1 | A valid DKIM signature from the From domain | Sign with your own domain, not your tool's |
Notice how small SpamAssassin's SPF_FAIL score is with Bayes and network tests on. That doesn't mean SPF doesn't matter: Gmail and Outlook weigh authentication heavily, and failing SPF also breaks DMARC, which carries more points.
Does Gmail use SpamAssassin?
No. Gmail and Outlook run their own filters and don't use SpamAssassin's score. Many company mail gateways, web hosts and smaller providers do run SpamAssassin, and B2B prospects often sit behind them. The problems SpamAssassin flags, such as broken authentication, blocklisted links and image-only emails, also hurt you at Gmail and Outlook.
How to check your SpamAssassin score
Send a real email to a testing tool. mail-tester runs a default SpamAssassin install and gives 3 free tests per rolling 24 hours (mail-tester FAQ). See our deliverability testing tools for others.
Send from the inbox and tool you'll use for the campaign. A test from your personal Gmail tells you nothing about your sending setup.
Read the matched rules, not just the total. The rule list tells you what to fix.
Change one thing at a time and test again. That way you know which fix moved the score.
How to read the X-Spam-Status header
If a server runs SpamAssassin, it usually adds its result to the email's headers. In Gmail, open the email, click the three dots and choose "Show original". In Outlook, open the message's properties to see the internet headers.

X-Spam-Flag: NO
X-Spam-Level: *
X-Spam-Status: No, score=1.2 required=5.0 tests=DKIM_SIGNED,
DKIM_VALID,DKIM_VALID_AU,RDNS_NONE,SPF_PASS,SUBJ_ALL_CAPS
autolearn=ham version=4.0.2Part | What it tells you |
|---|---|
X-Spam-Flag: NO | The email wasn't marked as spam |
X-Spam-Level: * | One star per whole point; 1.2 rounds down to 1 star |
No, score=1.2 | Not spam, with a total of 1.2 points |
required=5.0 | This server's spam cutoff |
tests=... | Every rule that matched; look these up to see what to fix |
autolearn=ham | The server's Bayes filter learned from it as good mail |
version=4.0.2 | The SpamAssassin version that scored it |
In this example, using set 3 scores, the three DKIM rules net −0.1, SPF_PASS is −0.001, RDNS_NONE adds 0.793 and SUBJ_ALL_CAPS adds 0.5, for 1.192, shown as 1.2. Fixing the all-caps subject alone takes it to 0.7. The header is an example built from the rules file, not a real email.
How to lower your SpamAssassin score
Fix the rules with the most points first. In order:
Clean every link. A link to a blocklisted domain adds up to 2.5 points on its own. Check your tracking domain too, and avoid URL shorteners.
Fix authentication. Make SPF, DKIM and DMARC pass and align with your From domain. A DMARC failure adds 1.2 to 1.8 points, and a valid DKIM signature from your own domain takes points off. See SPF, DKIM and DMARC explained.
Send text, not images. Image-heavy HTML adds up to about 1.6 points. A plain-text cold email avoids the whole group of HTML rules.
Send through a provider with reverse DNS. Google Workspace and Microsoft 365 handle this for you; a self-hosted server may not.
Drop shouty formatting. An all-caps subject adds 0.5. Rows of exclamation marks and "100% free" style claims trip other content rules.
Get off blocklists. If your domain or IP is listed, no copy change will fix it. See our blacklist removal guide.

Before and after: one email, two scores
Here's what fixing the big rules does, using set 3 points from the rules file. It's an example, not a real test.

Rule | Before | After |
|---|---|---|
URIBL_BLACK (blocklisted tracking link) | +1.7 | removed |
HTML_IMAGE_ONLY_24 (image-heavy HTML) | +1.618 | removed |
DMARC_QUAR (DMARC failed) | +1.198 | removed |
RDNS_NONE (no reverse DNS) | +0.793 | removed |
SUBJ_ALL_CAPS | +0.5 | removed |
DKIM_SIGNED and DKIM_INVALID | +0.2 | DKIM_SIGNED +0.1 |
DKIM_VALID and DKIM_VALID_AU | none | −0.2 |
SPF_PASS | none | −0.001 |
Total | 6.0, spam | −0.1, clean |
A low score isn't the whole story
A low SpamAssassin score means your email passes one filter's content and setup checks. It doesn't guarantee the inbox. A clean email from a domain with high bounce or complaint rates can still land in spam at Gmail or Outlook, which judge your sending history too. Track real inbox placement alongside the score.
A five-minute pre-send check
Send your first email, exactly as written, from the real inbox to a testing tool.
Confirm SPF, DKIM and DMARC all pass.
Read the matched rules and fix anything worth more than about 0.5 points.
Click every link and check each domain, including the tracking domain.
Read the plain-text version to make sure it makes sense on its own.
How Alien Mail helps
Alien Mail sets up SPF, DKIM and DMARC on the mailboxes you buy, warms every inbox for free and verifies your list before every send, so most of the setup rules in this post are handled before your first campaign. You pay only for emails sent, starting with 100 free credits and no card.
Start free → · See free email warmup
Frequently asked questions
What is a good SpamAssassin score? Below 2 is healthy and below 0 is excellent. The default spam cutoff is 5.0, but some servers flag email at lower scores, and SpamAssassin suggests 8.0 to 10.0 for ISPs.
Is a higher SpamAssassin score better? No. In SpamAssassin's own score, lower is better and there is no maximum. Some tools, such as mail-tester, flip it into a score out of 10 where higher is better.
What does required=5.0 mean in an email header? It's the server's spam cutoff, set by required_score. An email that scores 5.0 or more on that server is marked as spam. 5.0 is SpamAssassin's default.
Why do two testers give different SpamAssassin scores? A rule can have 4 point values, and the one used depends on whether the server runs Bayes learning and network tests. Rule updates also change scores over time.
Can a negative SpamAssassin score happen? Yes. Rules for good signals subtract points. A valid DKIM signature from your own domain takes off 0.2 across two rules (0.1 net, since DKIM_SIGNED adds 0.1), so a clean email can score below 0.
Do Gmail and Outlook use SpamAssassin? No. They use their own filters. Many company gateways and web hosts do use SpamAssassin, so it matters for B2B cold email.
Can a good email still get a high SpamAssassin score? Yes. A blocklisted link, a failed DMARC check or an image-heavy layout can add several points to an email whose copy is fine.
Key terms
SpamAssassin: an open-source spam filter from the Apache Software Foundation, used by many mail servers and gateways.
Rule (test): one check SpamAssassin runs, with a point value that's added when it matches.
required_score: the server's spam cutoff, 5.0 by default.
Score set: which of a rule's 4 point values is used, depending on Bayes and network tests.
X-Spam-Status: the email header where SpamAssassin writes its verdict, score and matched rules.


