Why Are My Emails Going to Spam All of a Sudden? A 15-Minute Diagnostic for Gmail, Outlook and Yahoo

Updated 17 October 2026.

First: which mailbox provider is filtering you?

Spam placement is almost never universal. Before touching anything, split your last campaign's results by recipient domain. Your ESP's reporting usually shows delivered, opened, clicked, bounced and complained by domain; if it doesn't, export the recipient list and pivot on the domain.

Scroll for more → On small screens, choose cards for wide tables.

Knowing the scope tells you which tool to open and saves you from "fixing" something that isn't broken.

The 15-minute triage (in this order)

Work through these seven checks in sequence. Stop at the first one that fails and fix it before moving on; later checks are often symptoms of earlier failures.

1. Does authentication pass and align? (3 minutes)

Send a test message to a personal Gmail address. Open it, choose "Show original," and read the three lines: spf=pass, dkim=pass, dmarc=pass. Then check the domains next to them. The DKIM signing domain or the SPF domain must be your From domain (or a subdomain of it) for DMARC to pass. If any line says fail, softfail, temperror or none, you have found the problem. Common causes: an expired or rotated DKIM key, an ESP migration that left the old DNS records in place, an SPF record that now exceeds 10 DNS lookups (Microsoft flags this one explicitly), or a new sending subdomain that was never authenticated.

2. What is your Gmail spam rate? (2 minutes)

Open Postmaster Tools. The rule is below 0.10% to be safe, never at or above 0.30%. If you are above 0.3%, Google will not offer mitigation until the rate "remains below 0.3% for 7 consecutive days." Look at the trend, not one day: a single spike after one send is a list problem; a slow climb over weeks is a content or frequency problem. Then open the Compliance status dashboard, which shows whether you meet each sender requirement.

3. What changed in the last 14 days? (3 minutes)

List every change: a new segment (especially one that had not been mailed in months), a volume jump, a new sending domain or subdomain, a new template, a new link-tracking domain, a new ESP or IP pool, a DNS change, a domain renewal, a new team member with send access. The answer is usually in this list. A send to a dormant segment is the single most common trigger we see for a "sudden" spam problem on an otherwise compliant program.

4. Did bounces or complaints spike on a specific send? (2 minutes)

In the ESP, sort recent sends by hard-bounce rate and complaint rate. A send with hard bounces above 2% or complaints above 0.1% is your culprit. Note its audience: that segment needs suppression and a different treatment, not another send.

5. Content and links (2 minutes)

Check the links in the suspect email: URL shorteners, a tracking domain that differs from your From domain and has no reputation, links to a domain on a blocklist, or a link to a site that was recently compromised. Check for a sudden shift to image-only content or a template with broken HTML. Content is rarely the sole cause of a sudden drop, but a bad link can be.

6. Blocklists and shared infrastructure (2 minutes)

Look up your sending IPs and domain on Spamhaus and a multi-blocklist checker. If you are on a shared IP pool at your ESP, check the ESP's status page and ask support whether the pool had an incident. Yahoo's permanent rejections explicitly include "IP listed by Spamhaus" as a cause.

7. Unsubscribe mechanics (1 minute)

Confirm the one-click unsubscribe headers (List-Unsubscribe and List-Unsubscribe-Post) are present on marketing mail and that the visible unsubscribe link works without login. A broken unsubscribe turns people who would have left quietly into complaints.

Download the printable 7-check triage (PDF).

The diagnostic tree

Scroll for more → On small screens, choose cards for wide tables.

Gmail specifics

Gmail is where most "going to spam" questions start, because it is the largest consumer mailbox and because Postmaster Tools makes the problem visible.

• The spam rate is user reports, not filter decisions. It is the share of delivered mail that recipients mark as spam, calculated daily, only for personal Gmail accounts. A rate of 0.3% is three reports per thousand. On a cold list that is easy to exceed.
• Compliance status replaces guesswork. Postmaster Tools v2 shows whether you pass each requirement: SPF/DKIM/DMARC with alignment, one-click unsubscribe, spam rate. The old Domain Reputation dashboard is being retired, so stop looking for a "Bad / Low / Medium / High" label and read the compliance and spam-rate views instead.
• Promotions is not spam. A move from Primary to Promotions is a classification change, not a deliverability failure. Your engagement will dip, but the mail is in the inbox.
• Engagement matters more since January 2026. Gmail's AI inbox summaries and the "Manage subscriptions" view with one-tap unsubscribe make it easier for disengaged subscribers to leave or to report. That raises the cost of mailing people who do not read you.
• Temporary codes name the failing requirement. Google's FAQ lists 4.7.27 (SPF), 4.7.30 (DKIM), 4.7.31 (no DMARC policy), 4.7.32 (From alignment), 4.7.23 (PTR) and 4.7.29 (TLS). 5.7.26 is a permanent rejection for unauthenticated mail. Read the raw bounce text.

Outlook, Hotmail and Live specifics

Since 5 May 2025 Microsoft enforces SPF, DKIM and DMARC (at least p=none, aligned with SPF or DKIM) for domains sending more than 5,000 messages a day to its consumer domains. Microsoft's own notice says non-compliant mail is rejected with 550 5.7.515 Access denied, sending domain [SendingDomain] does not meet the required authentication level. There is no gray area to negotiate: fix authentication and the rejections stop.

Two Microsoft-specific checks: SPF records with more than 10 DNS lookups fail, and Microsoft says a Safe Senders entry "won't be honored" as a bypass. For visibility, register your IPs in SNDS (Smart Network Data Services) for complaint and trap data, and in JMRP (Junk Mail Reporting Program) to receive copies of messages users mark as junk.

Yahoo and AOL specifics

Yahoo requires a complaint rate below 0.3%, calculated against mail delivered to the inbox rather than everything sent, and unsubscribes honored within two days. Its temporary deferrals (421, 451) cite complaints, spam-like content, poor IP reputation or unusual traffic patterns; its permanent rejections (553, 554) cite DMARC or DKIM failures, policy content, suspicious behavior or a Spamhaus listing. Enroll each DKIM domain in Yahoo's Complaint Feedback Loop so you see complaints as they happen, and if the same deferral code repeats "over an extended period," submit a Sender Support Request with the exact error and diagnostic codes from your logs.

Google Workspace and Microsoft 365 recipients

If the complaints come from B2B recipients on corporate domains, none of the consumer dashboards will show it. Google's sender guidelines "don't apply to messages sent to Google Workspace accounts," and Postmaster Tools reports only personal Gmail. Corporate filtering is set by each organization's admins. Your levers are the same (authentication, list quality, relevance), but the feedback loop is the recipient telling you. Ask a few customers at affected companies to check their spam folder and, if possible, mark you "not spam" and add you to their allow list.

Why fixes take days to show up

Three lags stack on top of each other. Postmaster Tools data is calculated daily and can be missing on low-volume days. Google's mitigation eligibility requires seven consecutive days below 0.3%. And filtering decisions use rolling reputation windows, so a clean week slowly dilutes a bad day. Practitioners generally report seeing the effect of a fix in Postmaster Tools after 5–10 days. Plan for two weeks before judging whether a change worked, and do not stack new changes on top of each other during that window or you will not know which one mattered.

What NOT to do

1. Don't switch to a new domain. A domain without sending history is treated with suspicion, and Google applies an accelerated enforcement timetable to domains that only became bulk senders after 1 January 2024. You would be starting from zero with your most damaged traffic.
2. Don't send more to "prove" you are legitimate. Volume on a damaged reputation accelerates the damage.
3. Don't switch ESPs mid-recovery. You lose the data that tells you what went wrong, and shared-IP reputation at the new ESP is not yours anyway.
4. Don't remove your DMARC record to "stop failures." It removes your eligibility for mitigation and does nothing for placement.
5. Don't re-import an old export to replace "bad" segments. That is how suppressed addresses and traps come back.

The 14-day recovery plan

Scroll for more → On small screens, choose cards for wide tables.

When it's actually a dormant-list problem

The pattern is unmistakable: authentication passes, the engaged program was healthy, and the drop began the day you sent to subscribers who had not heard from you in months. Hard bounces on that send were 1–3% or more, complaints 0.2% or more. That segment contains the invalid addresses, recycled spam traps and forgotten signups that every old list accumulates (vendor scans report 15–30% invalid or risky), and it will produce the same result every time you mail it as a block.

The fix is not a better subject line. It is eligibility checks, a scan, a 1/30 daily stream and written stop conditions, which is what the dormant list reactivation playbook describes step by step.

Did the drop start after mailing an old segment? The free List Health Audit scans that segment for bounces, traps and dead domains, maps dormancy by tier and scores your domain risk, within 72 hours. Get the free audit →

FAQ

Can a single send ruin my sender reputation? Yes, if it pushes the complaint rate to 0.3% or produces a bounce spike. Three reports per thousand delivered is the Gmail limit, and a cold segment can produce that in one send. The damage spreads to your engaged recipients because reputation is tracked per domain.

How long does it take to recover from spam placement? Authentication fixes work as soon as DNS propagates and the mailbox providers see clean mail, typically days. Reputation recovery from a complaint spike takes weeks of clean sending; expect to see the effect in Postmaster Tools after 5–10 days and plan two weeks before judging.

Should I pause sending completely? Pause marketing and promotional sends while you fix the cause. Keep transactional mail (receipts, password resets) flowing. Then resume to your most engaged recipients only.

Do shared IPs cause sudden spam placement? Sometimes, and your ESP's status page or support will tell you if the pool had an incident. More often the cause is on your side, because Gmail and Microsoft weight domain reputation heavily and that is yours alone.

Does Google Postmaster Tools show Outlook or Yahoo data? No. It covers personal Gmail only. Use Microsoft SNDS and JMRP for Outlook.com domains and Yahoo's Complaint Feedback Loop for Yahoo and AOL.

What does error 5.7.26 mean? Gmail rejected the message because it was not authenticated: SPF or DKIM is missing or failing, or, for bulk senders, DMARC and alignment are not in place. Fix authentication and the rejections stop.

Want a second pair of eyes on authentication, spam-rate exposure and list risk? The Data & Deliverability Audit covers all three across your sending domains. Request the audit →

Continue with these guides

• List revival
• Email sender requirements
• Google postmaster tools v2
• List revival playbook
• Email sunset policy

Sources

• Google, Email sender guidelines and FAQ: thresholds, 7-day mitigation rule, November 2025 enforcement, Workspace exclusion, 4.7.x and 5.7.26 codes. https://support.google.com/a/answer/81126 and https://support.google.com/a/answer/14229414
• Google, Get started with Postmaster Tools and Deprecation of the old Postmaster Tools interface: personal-Gmail scope, missing data on low volume, reputation dashboards retired, Compliance status. https://support.google.com/mail/answer/9981691 and https://support.google.com/mail/answer/16594218
• Microsoft, Strengthening Email Ecosystem: Outlook's New Requirements for High-Volume Senders (April 2025, v4.0): 5,000/day, 550 5.7.515, 10-lookup SPF note, Safe Senders not honored. https://techcommunity.microsoft.com/blog/microsoftdefenderforoffice365blog/strengthening-email-ecosystem-outlook’s-new-requirements-for-high‐volume-senders/4399730
• Yahoo, Sender Best Practices and SMTP Error Codes. https://senders.yahooinc.com/best-practices/ and https://senders.yahooinc.com/smtp-error-codes/
• Gmail January 2026 inbox features (AI summaries, Manage subscriptions), as reported by Google and covered by Klaviyo, Attentive and Tom's Guide.
• Practitioner estimates of Postmaster Tools lag (5–10 days): Suped, Bento documentation. Vendor sources.
• EmailListValidation (2026): 15–30% invalid or risky addresses in dormant lists. Vendor figure.