Is "This is not spam" a spam trigger word?
"This is not spam" is a defensive disclaimer that backfires: legitimate senders rarely need to insist they aren't spam, so filters and recipients read the phrase as a tell of exactly the mail it denies being. It's a weighted content signal at the "shady" end of the scale — never an automatic block on its own, but one of the more self-defeating phrases you can put in a cold email.
Also flagged: This isn't spam, Not spam, I promise this isn't spam.
Telling someone "this is not spam" is meant to reassure, but it does the opposite. Real 1:1 email from a person you'd want to hear from never opens by denying it's junk — only mass and scam mail does, which is why the phrase clusters with the lowest-quality messages spam filters are trained on. It also collides with sender guidelines (Google's and the FTC's CAN-SPAM rules alike) that ask your subject and content to honestly represent who you are and what you're sending, rather than pre-empting suspicion.
- Category
- Shady / phishing
- Risk level
- Medium (self-defeating in subject)
- Worst variants
- This is NOT spam, I promise this isn't spam
- Safer phrasing
- Delete it — a clear From name and relevant first line do the work
Key takeaways
- No single phrase sends an email to spam by itself. Deliverability is decided mostly by authentication (SPF/DKIM/DMARC), sender reputation, and your spam-complaint rate, with wording acting as a weighted tiebreaker that matters in combination.
- "This is not spam" backfires by design: genuine senders don't need to defend their legitimacy, so the disclaimer reads as a hallmark of the spam it denies being.
- It runs against Google's guidance and the FTC's CAN-SPAM rules that subject lines and content should honestly represent the sender — defensive or misleading framing hurts, it doesn't help.
- Human recipients react the way filters do: the phrase raises suspicion and lowers replies, and low engagement feeds back into a worse sender reputation.
- The fix is to delete it entirely and earn trust the real way — a relevant subject, a clear sender identity, a personal first line, and a working one-click unsubscribe.
Why does "This is not spam" trigger spam filters?
Modern filters at Gmail, Outlook, and Apple Mail don't run a simple banned-word list — they score messages with models trained on billions of examples of wanted and unwanted mail. The phrase "this is not spam" appears overwhelmingly in the unwanted pile, because legitimate 1:1 email from someone you'd want to hear from simply never opens by denying it's junk. That statistical lopsidedness is what makes it a negative signal.
There's a human layer too. The phrase is a textbook case of "protesting too much": the moment a sender insists they're legitimate, both filters and people lean toward the opposite conclusion. It reads as the behaviour of someone who expects to be distrusted — which is itself a property of low-quality and scam mail.
It also brushes against sender guidelines. Google asks that a message's subject, headers, and content accurately represent the sender and not be misleading, and the FTC's CAN-SPAM rules require honest, non-deceptive subject lines. A defensive disclaimer doesn't represent anything real about you; it just tries to manage perception, which is the opposite of the honest framing those rules reward.
Does "This is not spam" always send an email to spam?
No. No single phrase is a guaranteed one-way ticket to the spam folder, and "this is not spam" is no exception. The heavy lifting in deliverability is done by authentication and reputation: if your domain passes SPF, DKIM, and DMARC, your sender reputation is healthy, and your Postmaster spam-complaint rate stays well under the 0.3% line Google flags (ideally below 0.1%), a single ill-judged sentence won't sink an otherwise trusted message.
What the phrase does is stack the deck against you. It adds content risk on top of whatever else is weak — a cold domain with no sending history, an all-caps subject, multiple links, or low open and reply rates. Filters react to the cluster, and "this is not spam" is a cluster member that brings zero upside.
So treat it as a pure liability rather than a tiebreaker worth keeping. With most spam words there's a legitimate reason to use them occasionally; with "this is not spam" there essentially isn't, because it can never make a real email more trustworthy.
What can you use instead of "This is not spam"?
The honest answer is: nothing — just delete it. There is no rephrasing that preserves the intent, because the intent itself (pre-empting the suspicion that you're spam) is the problem. Anything that gestures at "trust me, I'm legit" carries the same backfire.
Instead, earn the trust the disclaimer was trying to fake. Send from a real, authenticated domain with a recognisable From name; write a specific subject that names a real topic; and open with a personal first line that proves you did your homework — a detail about their company, role, or recent announcement. That combination signals legitimacy far more convincingly than any sentence claiming it.
If you genuinely worry the recipient won't know who you are, say who you are plainly ("I'm a founder at Komo; we work with RevOps teams like yours") and give them an easy out with a one-click unsubscribe. Transparency and a clean exit do what a defensive disclaimer never can.
Before and after
As of June 2026.Sources:Google — Email sender guidelinesGmail — Email sender guidelines (bulk senders FAQ)FTC — CAN-SPAM Act: A Compliance Guide for Business
Is “This is not spam” in your email?
Paste your draft into the free Email Spam Checker. It highlights every trigger word, scores your inbox placement 0–100, and rewrites the email to pass — in seconds, no signup.
Check your email free“This is not spam” — frequently asked questions
