Are your campaigns landing in spam while your sending tool reports successful deliveries? Open Postmaster Tools first: sender reputation shows up in the spam rate. A spam rate below 0.10% is the target, and 0.30% is the limit you should never reach. Google’s guidelines give no timeframe for rebuilding a reputation, so this guide lays out the order of checks, then a 3-phase correction plan with dates.
What Gmail, Outlook and Yahoo measure
Sender reputation is not a single score. Each mailbox provider keeps its own, based on the messages its users receive from you. Gmail exposes it in Postmaster Tools (spam rate, domain and IP reputation, authentication). That older interface is due to give way to a v2 and its compliance dashboard. Microsoft shows it in SNDS and Yahoo in its Sender Hub. The Sender Score is a different measure: a 0 to 100 grade that Validity, a third party, assigns to an IP address, and that no mailbox provider uses. On a dedicated IP, IP address reputation is tracked separately from domain reputation.
5 factors feed these signals:
- the spam complaint rate;
- where sign-ups come from (single or double opt-in);
- your bounce rates;
- how steady your sending volumes are;
- recipient engagement.
Diagnose: Postmaster Tools, SNDS and blocklists
Start by measuring. Each check below rules a cause in or out.
Read the spam rate in Postmaster Tools
Add the DKIM domain (d=) or the SPF domain (Return-Path) of your messages to Postmaster Tools, then verify it with the TXT or CNAME record provided. Google says verification can take up to 10 minutes (Postmaster Tools help). Until it is verified, no data appears. The guide to setting up Google Postmaster walks through the procedure.
The dashboard only covers messages received by @gmail.com or @googlemail.com accounts. Google Workspace recipients are outside its scope. Google’s guidance fits in one sentence:
Keep spam rates reported in Postmaster Tools below 0.10% and avoid ever reaching a spam rate of 0.30% or higher.
That sentence comes from Gmail’s email sender guidelines. Google adds that a low rate makes a sender more resilient to occasional spikes in complaints.
| Provider | Complaint threshold | Authentication requirements |
|---|---|---|
| Gmail | target below 0.10%, limit 0.30% | SPF, DKIM and DMARC above 5,000 messages per day |
| Yahoo | 0.3% (on mail delivered to the inbox) | SPF and DKIM, DMARC at p=none minimum |
| Outlook.com | not specified in the announcement | SPF, DKIM and DMARC above 5,000 messages per day, rejection with 550 5.7.515 since May 5, 2025 |
Query SNDS and Yahoo’s Sender Hub
Sign in to SNDS with a Microsoft account, then request access to the IP addresses you are responsible for. The service provides per-IP data and a Junk Mail Reporting Program (JMRP) that sends back complaints from Outlook.com users. Our page on Microsoft SNDS explains the columns of the report.
Yahoo sets the same 0.3% complaint limit. Its calculation starts from mail delivered to the inbox, according to the Sender Requirements page, so the rate you compute on raw sends will be lower than the one Yahoo applies. Yahoo’s Sender Hub is where you enroll your domains in the Complaint Feedback Loop, which sends complaints back.
Look up your IP and domain on blocklists
Spamhaus runs several lists: SBL, PBL and XBL for IP addresses, DBL for domains. Query them with your sending IP, then with the sender domain. If the IP or domain is listed, fix the cause first (purchased list, authentication, complaints): each list publishes its own removal procedure and generally refuses a request while the problem persists.
In your SMTP logs, Gmail’s 550 5.7.1 code can mean the IP sits on a list of suspended addresses, a case Google links to shared IPs with a bad reputation. The code also has other possible causes, including a domain with a very low reputation. A message refused with 5.7.26 points instead to an authentication failure.
The causes that sink reputation
The readings almost always point to one of the following causes.
Purchased lists come first. Yahoo advises against buying lists or pre-ticking the sign-up box. Spamhaus notes that spam traps, addresses with no human owner, are used to spot senders who scrape, buy or fail to maintain their contacts (Spamhaus guide on spamtraps, 2022). List verification reduces bounces and removes dead addresses. It cannot detect a trap address that accepts mail: only the origin of the list settles that risk.
A missing one-click unsubscribe comes next. Gmail and Yahoo expect a List-Unsubscribe header allowing one-click unsubscribe (RFC 8058) on marketing messages. Requests must be processed within 48 hours (Google’s recommendation) or 2 days (Yahoo). A recipient who cannot find the exit clicks “spam”.
Incomplete authentication weighs too. Above 5,000 messages per day to Gmail, Google requires SPF, DKIM and DMARC, with a From header domain aligned with the SPF or DKIM domain. Since November 2025, Gmail has been enforcing these rules more strictly: non-compliant messages risk temporary or permanent rejections, on top of being filed as spam. Microsoft announced the same requirements for Outlook.com on April 2, 2025 (domains sending more than 5,000 messages per day). The initial announcement first provided for Junk placement from May 5, 2025, then rejection at an unspecified date. Its April 29 update strikes that passage: non-compliant messages are rejected with error 550 5.7.515, effective May 5, 2025 as announced (Microsoft announcement). Go back to the authentication setup if one of the three protocols fails: SPF and DKIM prove where the message came from, while DMARC sets the policy applied when they fail.
Volume plays a role of its own. According to Google, suddenly doubling your sends can trigger rate limiting or a drop in reputation. On a shared IP, the reputation of every customer in the same pool also weighs on your deliveries. A dedicated IP removes that dependency and leaves you solely responsible for its reputation.
A 3-phase correction plan
No provider promises a timeline. The phases below form a working schedule whose measurable milestones come from Postmaster Tools.
Days 1 to 7: stop the damage
Pause sending to recently imported contacts and to anyone who has opened nothing in 6 months. Keep transactional mail running. Add the one-click List-Unsubscribe header and fix the SPF, DKIM or alignment failures found above. Aim for 7 consecutive days below 0.3%: above 0.3%, a bulk sender loses access to Google’s mitigation measures and only becomes eligible again after 7 consecutive days under that threshold.
Weeks 2 to 4: clean the list and resume volume
Run the list through a verification tool before the next send, for example on a sample of 1,000 contacts, then compare the hard bounce rate before and after cleaning. Email cleaning removes invalid addresses. It says nothing about whether recipients care. Next, send a re-engagement campaign to inactive contacts and delete those who do not respond.
Resume volume with a stepwise warm-up, following Google’s recommendations: start small with interested users, check the spam rate and SMTP errors at each step, and reduce volume if deferrals persist. Finally, switch to double opt-in for new sign-ups.
After week 4: lock it down and monitor
Google, Yahoo and Microsoft accept DMARC at p=none, which protects nothing but produces reports. Read the aggregate reports (rua tag) until all your legitimate sources pass alignment. Then move up to p=quarantine and finally p=reject. Sign up for the providers’ feedback loops, JMRP at Microsoft and the Complaint Feedback Loop at Yahoo, so you can remove each complainer from the list. Last, set your sending frequency to match the promise made at sign-up, with email subject lines that match the content: a faster pace or a misleading subject line pushes complaints up.
Common mistakes
Verifying the wrong domain in Postmaster Tools. Google asks for the DKIM domain or the SPF domain of your messages. A brand domain that does not appear in the headers returns no chart.
Relying on an “unsubscribe” link in the message body. Google specifies that a mailto link in the text does not meet the one-click unsubscribe requirement, which runs through the headers.
Assuming bulk sender status disappears when volume drops. It does not expire: per Google’s FAQ, a domain that has reached 5,000 messages per day to Gmail stays subject to the bulk sender rules, with no exit date.
Judging reputation on a single indicator. A good Sender Score does not prevent a block at Gmail, which only Postmaster Tools documents.
Frequently asked questions
Can you ask Google to lift a block?
Only bulk senders that meet every requirement can file a request through Google’s contact form. Since June 2024, a spam rate above 0.3% rules a sender out of these mitigation measures.
Do the rules apply below 5,000 messages per day?
Yes, for the basics. Since February 1, 2024, every sender to Gmail must authenticate with SPF or DKIM, use TLS, have valid reverse DNS and stay under 0.3% spam. DMARC and one-click unsubscribe only become mandatory above 5,000 daily messages.
Does a new domain escape the old one’s reputation?
Google applies its measures faster to new domains, defined as those that have not exceeded 5,000 messages per day to Gmail since January 1, 2024. Switching domains to escape a bad reputation therefore exposes you to quicker scrutiny.
