Quick answer
Your spam complaint rate is the share of delivered mail that recipients mark as spam, and both Gmail and Yahoo now hold bulk senders to a hard ceiling. Google's sender guidelines say to keep the spam rate reported in Postmaster Tools below 0.3%, and Google's additional guidance is to keep it below 0.10% and avoid ever reaching 0.30%. Yahoo's sender requirements say the same: keep your spam rate below 0.3%. Crossing that threshold is a list-quality and relevance problem — authentication will not fix it.
What the spam complaint rate is
The spam complaint rate (also called the user-reported spam rate) is the proportion of your delivered messages that recipients mark as spam by clicking "Report spam" or its equivalent. It is not a DNS record and not something you publish. It is a behavioral signal that mailbox providers calculate from what their own users do with your mail.
Gmail surfaces this number for you in Google Postmaster Tools as the Spam rate (or User-reported spam rate) chart, plotted day by day for your authenticated domain. Yahoo computes an equivalent rate on its side and, through its Complaint Feedback Loop, sends you copies of the individual complaints once your mail is DKIM-signed.
One detail changes how you should read the number. The rate is measured against mail that actually reached users. Gmail counts mail delivered to the inbox, and Yahoo states explicitly that its spam rate is calculated based on mail delivered to the inbox, not mail that was already routed to the spam folder. Mail that a provider sends straight to spam is generally not counted in the reported rate. That is why a low reported rate is not, by itself, proof of good placement — if a large share of your mail is being filtered to spam before it ever reaches an inbox, those messages cannot generate "Report spam" clicks, and your reported rate can look healthy while your real inbox placement is poor.
The threshold: below 0.3%, and really below 0.1%
The headline number is 0.3%. Google's guideline is to "keep spam rates reported in Postmaster Tools below 0.3%," and Yahoo's parallel requirement is to "keep your spam rate below 0.3%." But 0.3% is the ceiling you must never hit, not the target you should aim for.
Google's additional guidance makes the distinction concrete: keep your spam rate below 0.10%, and avoid ever reaching 0.30%. In practical terms, 0.3% is roughly 3 complaints for every 1,000 messages delivered. That is a small number. A single poorly targeted send to a stale segment can push a campaign over it. The 0.1% target gives you headroom so that one bad day does not breach the 0.3% line.
These requirements apply to all senders, and they are enforced for bulk senders — broadly, anyone sending around 5,000 or more messages per day to Gmail users. When your reported rate climbs toward or past the threshold, the consequences are immediate and graduated: throttling, spam-foldering, and ultimately rejection of your mail.
Why authentication does not lower your complaint rate
SPF, DKIM, and DMARC are necessary. Yahoo will not even send you Complaint Feedback Loop data until your mail is DKIM-signed, and both providers require valid authentication from bulk senders. But authentication answers a different question than the complaint rate does.
Authentication proves that a message genuinely came from your domain and was not tampered with in transit. The complaint rate measures whether the people receiving that genuinely-authenticated mail actually want it. You can pass SPF, DKIM, and DMARC on every message and still have recipients reporting you as spam in large numbers, because they never asked for the mail, forgot they signed up, or cannot find the unsubscribe link. Fixing authentication does nothing for any of those. A high complaint rate is a list-quality and relevance problem, and the levers that move it are about who you mail and how you let them leave.
How to lower a high complaint rate
It comes down to who you mail and how easily they can leave. These are the levers that actually move the number.
-
Mail only engaged, explicitly opted-in recipients. Send to people who asked to hear from you and who have opened or clicked recently. Cold lists, purchased lists, and addresses scraped from elsewhere generate complaints almost immediately.
-
Make unsubscribing trivial. Add a working one-click unsubscribe header so recipients can leave in a single action without hunting through the message. RFC 8058 one-click unsubscribe is itself a Gmail and Yahoo bulk-sender requirement, and it is the single most effective way to convert a would-be "Report spam" click into a clean removal. See the one-click unsubscribe guide.
-
Prefer confirmed (double) opt-in. Require a confirmation step before adding an address to your list. It costs you some signups but guarantees that everyone on the list genuinely wanted to be there, which is the strongest possible defense against complaints.
-
Segment and sunset inactive recipients. Identify recipients who have not opened or clicked in a defined window and stop mailing them, or move them to a low-frequency re-engagement track. Inactive recipients are far more likely to report mail as spam than to unsubscribe politely.
-
Keep volume and cadence consistent. Sudden spikes in volume or frequency look like a compromised account or a list dump to filtering systems and to recipients alike. Ramp gradually and hold a steady, predictable sending pattern.
-
Use a recognizable, aligned From identity. Send from a From name and domain recipients recognize, aligned with your authenticated domain. Mail that looks unfamiliar in the inbox is mail that gets reported.
-
Process bounces and remove invalid recipients promptly. Suppress hard bounces and invalid addresses immediately. A list full of dead addresses signals poor hygiene and concentrates your sending on the recipients most likely to complain.
-
Monitor and react to spikes. Watch the Postmaster Tools spam rate chart for Gmail and the Complaint Feedback Loop for Yahoo. When you see a rise, pause and investigate the responsible send before it climbs toward 0.3% rather than after.
What this does not measure
A low reported spam complaint rate tells you that the recipients who received your mail in their inbox mostly did not press "Report spam." It does not tell you how much of your mail was filtered to the spam folder before it could be reported, what your domain or IP reputation looks like at any specific provider, or whether a particular message reached a particular inbox.
Relaymetry checks the public DNS and authentication baseline for your domain. It cannot see your Postmaster Tools spam rate, your Yahoo Complaint Feedback Loop data, or inbox-placement outcomes — those live inside the mailbox providers' own dashboards and feedback loops, tied to mail you actually sent. Use the full domain report as the entry point to confirm the authentication foundation, then read the complaint rate where the providers publish it.