KoltrixThe 0.3% spam rate line: how it is measured and avoided
Gmail and Yahoo both draw a line at a 0.3% spam complaint rate and recommend staying under 0.1%. How the rate is calculated and how to keep it low.
On this page(8 sections)
- What the rate measures
- How few complaints it takes
- What happens at the threshold
- Why people complain
- Keeping the rate low
- Make unsubscribing easier than complaining
- Send to people who want the mail
- Set expectations at signup
- Keep the sender recognizable
- Watch new segments carefully
- Measuring your own rate
- An alerting setup
- Key takeaways
Gmail and Yahoo both draw the same line: keep your spam complaint rate below 0.3%. Google also recommends staying below 0.1%.
Those numbers sound generous until you work out how few complaints it takes to cross them, and how the rate is actually calculated.
What the rate measures
The spam rate is the share of your messages that recipients mark as spam. In Google Postmaster Tools, the user-reported spam rate is calculated as the number of messages marked as spam divided by the number of messages delivered to the inbox, for mail from your domain to active Gmail users on a given day.
Two implications follow from that definition:
- Only inbox-delivered mail counts in the denominator. Messages that Gmail already filtered into spam are not part of it, because users cannot report a message as spam if it is already there. If a growing share of your mail goes to spam, your measured spam rate can look better while your actual situation is getting worse.
- It is per day and per domain. One bad campaign can push a single day over the line even if your monthly average looks fine.
Postmaster Tools also only shows data when your daily volume to Gmail is large enough, so low-volume senders may see gaps.
How few complaints it takes
At 0.3%, three complaints per thousand inbox-delivered messages crosses the threshold. At 0.1%, one per thousand.
| Messages delivered to inbox | Complaints at 0.1% | Complaints at 0.3% |
|---|---|---|
| 10,000 | 10 | 30 |
| 50,000 | 50 | 150 |
| 200,000 | 200 | 600 |
A newsletter sent to a list that includes people who signed up years ago and forgot can easily generate those numbers. Transactional mail usually has far lower complaint rates, which is one reason mixing streams on one domain is risky: marketing complaints drag down the reputation that receipts and password resets depend on.
What happens at the threshold
Both providers list a spam rate below 0.3% among their requirements. Gmail has been specific about one consequence: since June 2024, bulk senders with a user-reported spam rate above 0.3% are ineligible for mitigation. If you have a delivery problem and ask Google for help, it will not act until your rate has stayed below 0.3% for seven consecutive days.
Beyond that, spam complaints are among the strongest negative signals filters use. A sustained high rate pushes more of your mail into spam, which, as noted above, can hide the problem in your metrics while engagement collapses.
Why people complain
Complaints rarely mean recipients think you are a criminal. More often:
- They do not remember signing up. The signup was long ago, or happened as a side effect of creating an account.
- The frequency changed. A list that received monthly mail starts getting weekly messages.
- The content is not what they expected. They signed up for product updates and received promotions.
- Unsubscribing looks harder than reporting spam. If the unsubscribe link is tiny or requires logging in, the spam button is right there.
- The sender name is unfamiliar. A From name that does not match the brand they know reads as spam.
Keeping the rate low
Make unsubscribing easier than complaining
This is the single biggest lever. Gmail and Yahoo require bulk senders to support one-click unsubscribe (RFC 8058) on marketing and subscribed mail, which lets mailbox providers show an unsubscribe button near the sender name. Every person who uses it instead of the spam button is a complaint you did not receive. Add a clear unsubscribe link at the top or bottom of the message as well, and process requests within two days at most.
Send to people who want the mail
- Use confirmed opt-in for marketing lists where practical.
- Stop mailing addresses that have not opened or clicked in a long period; the exact cutoff depends on your sending frequency.
- Never import purchased or scraped lists.
- Separate consent for product updates and promotions.
Set expectations at signup
Tell people what they will receive and how often. Then send that. A welcome message that restates the cadence and offers preferences reduces later surprise.
Keep the sender recognizable
Use a consistent From name that matches your brand, and avoid rotating addresses or subdomains for the same audience.
Watch new segments carefully
When you mail a segment for the first time, especially a reactivation campaign, send to a small portion first and check complaint data before sending to the rest.
Measuring your own rate
Postmaster Tools covers Gmail. For other providers, feedback loops are your main source:
- Yahoo offers a complaint feedback loop for senders using DKIM, delivering reports for messages that Yahoo users mark as spam.
- Microsoft offers the Junk Mail Reporting Program for Outlook.com.
- Many other providers offer feedback loops through their postmaster pages.
Feedback loop reports arrive in ARF format. Process them automatically: suppress the complaining address immediately and record the complaint against the campaign and stream, so you can calculate your own complaint rate per send.
complaint rate = complaints received / messages delivered (per stream, per provider, per day)Gmail does not offer a traditional per-message feedback loop to senders; it offers aggregate data through Postmaster Tools and a Feedback-ID header mechanism that lets large senders see complaint rates by campaign identifier.
An alerting setup
- Daily: pull the user-reported spam rate from Postmaster Tools for each sending domain.
- Per campaign: compute complaints divided by delivered from feedback loop data.
- Alert at 0.1% for any stream, and treat 0.3% as an incident.
- On alert: pause the stream or segment responsible, review the list source and recent changes, then resume gradually.
Key takeaways
- Gmail and Yahoo both require a spam rate below 0.3%; Google recommends staying below 0.1%.
- Gmail's rate divides complaints by inbox-delivered messages, so heavy spam-folder placement can make the number look deceptively good.
- Above 0.3%, Gmail bulk senders are ineligible for mitigation until they have stayed below it for seven consecutive days.
- One-click unsubscribe, permission-based lists and clear expectations are what keep complaints low.
- Track complaints per stream and per campaign, and alert well before 0.3%.
Start with Koltrix
Your domain, one inbox, and an API that sends.
A team inbox where AI sorts and drafts (nothing is sent without your click), plus the transactional API and SMTP relay your product sends with. 7 days free, no card.
