Junk and spam consequences

Every email your app sends gets a spam score (see the health report). With the junk consequences feature of your plan, that score has a cost: each person’s mail provider has a spam filter, and mail that scores too high goes to their Junk folder.

A person never sees mail in Junk, so they never answer it. Just as in real life.

Filters

Each person’s filter is set by style.filter:

Filter	Junks mail scoring at least
strict	5
normal	6
lenient	9
none	never junks

When style.filter is not set, it follows the person’s address. Big providers are strict: gmail.com, googlemail.com, outlook.com, hotmail.com, live.com, msn.com, yahoo.com, aol.com, icloud.com and me.com. Every other domain is normal.

So the same email can reach [email protected] (normal, junks at 6) and land in Junk for [email protected] (strict, junks at 5) when it scores 5.5.

What you see

• The message is in the person’s Junk folder, not INBOX.
• A persona.junked event with the score, the threshold and why.
• Insights counts it as junked for that campaign.

Tip

If a test waits for mail to a person and times out, check their Junk folder: GET /api/[email protected]&folder=Junk&existing=true.

Lowering your score

The health report lists each finding that moved the score, with how to fix it. Common ones are a missing plain-text part, a subject in capitals, URL shorteners, and mail that is mostly images. See the health report.