# SpamAssassin Score: Check, Interpret, and Lower Email Spam Risk

Understand the SpamAssassin score threshold, negative scores and rule hits. Fix the cause of a high score, then check real inbox and spam placement.

A **SpamAssassin score** adds up the results of rules applied to an email. Higher scores indicate more spam-like signals under that scanner's configuration. The default spam threshold is **5.0**, but the receiving system can change it.

A result below the threshold is useful, but it does not guarantee inbox placement. Start with the rule report to understand the score, then test where your campaign actually lands.

## Quick answer: what is a good SpamAssassin score?

For a particular scan, you generally want a score below its configured threshold and no unresolved findings that indicate a real sender or message problem. Check the report's `required` value rather than assuming every scanner uses 5.0.

[Apache's SpamAssassin configuration reference](https://spamassassin.apache.org/full/4.0.x/doc/Mail_SpamAssassin_Conf.html) documents the default threshold and allows positive or negative rule weights. A negative result is therefore possible. The score is not a percentage or a grade out of ten.

There is no universal "0 to 2.9 is safe" band or "8 means block the campaign" rule. Your team may set its own review policy, but that policy should be clearly distinguished from the scanner's threshold.

## How SpamAssassin scoring works

The scanner runs the enabled tests and combines their weights. Its rules and configuration determine which findings contribute to the result. Two scanners can therefore produce different scores for the same message.

Read the report before editing. A high total caused by a sender authentication failure needs a different repair from one caused by malformed message content. Changing a subject line at random can leave the actual problem untouched.

## How to read SpamAssassin headers

If the receiving server adds SpamAssassin headers, look for `X-Spam-Status` and the accompanying report. The fields you need are:

| Field | What to look for |
| --- | --- |
| `score` | The total assigned to this message |
| `required` | The threshold used by this scanner |
| `tests` | Names of triggered rules; consult the detailed report for their weights and descriptions |
| Checker version | Context when comparing scans made at different times or on different systems |

For example, a reported score of `6.2` with `required=5.0` exceeds that scan's threshold by `1.2` points. It does not mean 62% of recipients will put the message in spam. This is an illustration of how to read the fields, not a measured campaign result.

Save the received message and its report before making changes. If a service displays only a summary grade, look for its explanation of the scale before comparing it with a raw SpamAssassin result.

## What raises a SpamAssassin score?

Use the actual triggered rules to decide what to investigate. Depending on the scanner's enabled tests, the report may point to authentication, headers, links, message formatting or reputation checks.

| Report finding | Useful next check |
| --- | --- |
| SPF or DKIM failure | Confirm that the email service provider (ESP) is authorized to send and that the received message passes the relevant authentication check |
| A domain mismatch | Identify which domains the rule compares; review the ESP's sending-domain configuration |
| A suspicious URL or domain | Inspect the final tracked link and destination, including redirects |
| Malformed HTML or MIME | Review the message produced by the sending system, including its plain-text and HTML parts |
| A blocklist result | Check the named list and affected domain or IP before choosing a repair |

Avoid assuming that a particular word, image count or text-to-image ratio always produces the same score. The named rule and its explanation are much more useful than a generic list of "spam words."

## Why do the sender domains differ?

If your report describes `HEADER_FROM_DIFFERENT_DOMAINS` as a difference between the From and EnvelopeFrom domains, compare the visible sender with the envelope sender used for delivery. An ESP may use its own return-path domain, so a mismatch alone is not enough to tell you that the message is fraudulent or broken.

Inspect the received message's From, Return-Path and authentication results. Check your provider's custom sending-domain instructions before changing DNS. As [Google explains](https://support.google.com/mail/answer/81126), DMARC can pass through aligned SPF or DKIM. Passing, aligned DKIM can therefore satisfy DMARC even when the envelope sender uses another domain. The [DMARC guide](/guides/dmarc-explained/) explains the relationship.

If a report flags this rule, read its assigned weight and description in that report. Correct an unintended setup problem, then send again through the same ESP. Do not rewrite the campaign just to remove a domain-related finding.

## How to lower a high SpamAssassin score

Start with the largest relevant rule contributions and confirm their cause. Repair authentication in the ESP or DNS configuration when that is the issue. Repair broken markup, misleading links or missing content in the message when the report points there.

Keep the final campaign recognizable and useful. Removing the offer, footer or necessary customer information to chase a number can make the email worse for the reader.

After each focused change, send the revised message through the same provider and inspect the new report. Keep the sender, scanner and test conditions comparable. A lower number from a different scanner is not a reliable before-and-after comparison.



### Put that spam score next to real placement

Run your message through MailSlurp and compare spam checks with provider inbox results. Find out whether the email reaches the inbox, lands in spam or goes missing.

[Test spam and inbox placement](/product/inbox-placement-deliverability-tests/)



## Spam score vs deliverability test

A rule-based score explains what one scanner found. An inbox placement test observes the folders used by the provider mailboxes in that test. Those are different measurements, and using both helps you investigate a campaign more effectively.

MailSlurp's [free spam test](/tools/free-spam-test/) provides placement results and a separate score displayed out of ten. Read that tool's labels and provider results on their own terms: its score is not the raw SpamAssassin total described above. In the MailSlurp result, a higher score represents healthier placement signals; in a raw SpamAssassin scan, a higher score adds spam suspicion.

For a campaign check:

1. Start the MailSlurp test and copy its current recipient addresses and tracking marker.
2. Send the finished campaign through the ESP and sender you normally use.
3. Confirm the send and wait for the completed observations.
4. Review the provider results individually, including spam and unresolved outcomes.
5. Investigate the affected sender or message, then repeat the test after a repair.

The [Mailchimp inbox placement guide](/guides/mailchimp-inbox-placement-testing/) walks through those steps in the provider. Use [inbox placement testing](/product/inbox-placement-deliverability-tests/) for repeatable campaign checks and compare equivalent provider samples over time.

## FAQ

### Is a SpamAssassin score under 5 always safe?

It is below the default threshold, but your scanner may use another threshold. Gmail, Outlook and other recipients also apply their own filtering systems. Check the rule findings and observed placement rather than using the number as a delivery guarantee.

### Is a negative score an error?

No. Rules can subtract as well as add points. Read the report to see which findings contributed to that total.

### Should I aim for zero?

A useful goal is to resolve genuine findings and confirm that the campaign reaches the intended mailbox folders. Changing correct content just to reach an arbitrary number can waste time without improving delivery.

### Why did the score change when I barely edited the email?

The received message may include changed tracking links, headers or formatting. The scanner's rules and configuration can also change. Compare both messages and their detailed reports before attributing the difference to the visible copy.

Once you have repaired the findings, [test the campaign's inbox placement](/tools/free-spam-test/) and review the email your recipients will actually receive.
