What Is a Good SpamAssassin Score?
Translates the raw score into concrete fixes instead of just explaining the number.
SpamAssassin scores run from 0 upward, with most mail servers treating 5.0 as the default line into spam-folder territory. A score of 0 to 2 is clean and passes almost every mail server; 2 to 5 is borderline; above 5 gets filtered on most servers. Content, sender authentication, and list quality all add to the score, so a high score is rarely caused by one single issue. It's also just one signal among several, since Gmail and Outlook run their own separate, non-public filtering on top of it.
How SpamAssassin Scoring Works
SpamAssassin is an open-source spam filter that many mail servers and hosting providers run, either on its own or as one input into a larger filtering system. It scans an email against a long list of rules, each one worth a certain number of points, and adds them up into a single score. There's no cap on how high a score can go in theory, but in practice most legitimate email lands under 5, and most spam runs well above it.
The default threshold most SpamAssassin installs use is 5.0: cross that and the message gets tagged or filtered as spam. A score of 0 to 2 is clean and passes nearly every server. 2 to 5 is borderline, still likely to be delivered but not comfortably clear. Some providers set a stricter threshold than the 5.0 default, which is why the safer practical target for cold email is under 2 to 3, not just under 5.
What Raises a SpamAssassin Score
The score is a sum of many small rule hits rather than one big penalty, which is why fixing it usually means fixing several small things rather than one obvious mistake.
Content and formatting. Classic spam-trigger phrases ("100% free," "act now," "risk-free," "guaranteed"), excessive capitalization, multiple exclamation marks, and a subject-to-body mismatch all add points. So does an email that's mostly a link or an image with very little actual text, and an unusually high ratio of links to words.
Authentication. Missing or misconfigured SPF, DKIM, and DMARC records add points independently of content, since one of SpamAssassin's jobs is checking whether a message is actually authorized to come from the domain it claims to be from. A perfectly written email with broken authentication can still score high.
Sender and list reputation. Sending from a domain or IP with a history of complaints, a blacklist listing, or a high bounce rate adds points that have nothing to do with the specific email's content. This is one of the reasons a technically clean email can still score poorly if it's coming from a domain with existing reputation problems.
Want every check on this page run automatically?
EmailQo runs SPF, DKIM, DMARC, blacklist, and content checks before every campaign, on your own Gmail, Outlook, or AWS SES sending account. Start the 7-day free trial, no card.
Start free trial →How to Lower It
Fix authentication first: verify SPF, DKIM, and DMARC are all set up correctly and passing, since this affects every email you send, not just one campaign. Then address content: write like a person emailing a colleague, avoid the classic trigger-word list, keep exclamation marks to at most one if any, and keep a healthy ratio of text to links and images. Finally, protect list and sender reputation by verifying addresses before sending and warming up any new sending account gradually rather than sending full volume from day one.
A SpamAssassin score is a useful proxy for content and setup quality, but it isn't the only thing deciding inbox placement. Gmail and Microsoft run their own separate, non-public filtering systems on top of whatever a server-side tool like SpamAssassin reports, so a clean score is a good sign, not a guarantee.
How EmailQo Helps
EmailQo's pre-send scanner checks the same categories of risk SpamAssassin scores on: trigger words, excessive capitals, exclamation marks, and DNS authentication, catching them while you write rather than after a send. It doesn't report a literal SpamAssassin number, since that score depends on the receiving server's own installed ruleset, but it flags the same underlying issues before they can add up into one.
Related Resources
Keep the guide close, get deliverability tips monthly
One short, useful email per month covering SPF/DKIM/DMARC pitfalls, warmup, and cold-email content. No spam. Unsubscribe anytime.
By subscribing you agree to receive occasional tips at this address. See our Privacy Policy. Unsubscribe anytime from any email or at /unsubscribe.
Your emails deserve the inbox.
Start free trialKeep reading
SPF Setup Guide for Cold Email Senders
Step by step SPF record setup for cold email. Includes DNS examples, common mistakes, and how to validate your record is working.
GuideDKIM Setup for Amazon SES | Step by Step
Complete DKIM setup guide for Amazon SES. Generate keys, add DNS records, verify in AWS console, and start sending authenticated email.
GuideDMARC Setup Guide for Cold Email Senders
Step by step DMARC setup for cold email. Choose the right policy, set up reporting, and protect your domain from spoofing.
AlternativeInstantly Alternative: Own Your Infrastructure
Instantly uses shared sending pools. EmailQo routes through your own AWS SES. Own your reputation instead of sharing it with thousands of senders.
AlternativeSmartlead Alternative: Dedicated Infrastructure
Smartlead shares your sending reputation with other users. EmailQo gives you your own AWS SES infrastructure. Dedicated sending from $19/mo.