Why Are My Emails Going to Spam
in Gmail But Not Outlook?

You test your emails — they arrive fine in Outlook, no problem in Yahoo, but every single Gmail recipient sends them to spam. Sound familiar? This isn't random. Gmail has significantly stricter email authentication requirements than almost every other mail provider, and since February 2024 those requirements got even tighter. Here's exactly what's happening and how to fix it.

📋 In this article

  1. Why Gmail is stricter than Outlook
  2. Google's 2024 sender requirements
  3. The most common causes
  4. Why DMARC alignment matters specifically for Gmail
  5. Are you sending bulk or marketing emails?
  6. How to fix Gmail spam issues step by step
  7. How to test if your fix worked

Why Gmail is stricter than Outlook

Gmail and Outlook use different spam filtering engines with different thresholds and priorities. Gmail has historically been more aggressive about enforcing email authentication standards — partly because Google processes an enormous volume of email globally and invests heavily in anti-spam technology, and partly because Gmail users are trained to trust their inbox and report spam aggressively when something looks off.

Outlook (Microsoft 365 and Outlook.com) tends to be somewhat more lenient, particularly for business-to-business email. It also uses different signals — including sender reputation databases and machine learning models — that may weigh authentication failures differently than Gmail does.

The result is that an email that passes Outlook's filters may still fail Gmail's — and this gap has widened significantly since Google's 2024 policy changes.

⚠️ Important context Gmail processes over 1.5 billion active accounts. In Canada alone, a huge proportion of your customers, clients, and prospects use Gmail for personal email — even if they use Outlook at work. If your emails are failing Gmail, you're missing a massive portion of your audience.

Google's 2024 sender requirements

In February 2024 Google introduced mandatory requirements for anyone sending email to Gmail addresses. These aren't guidelines — they're hard requirements, and failing them means your emails get rejected or sent to spam automatically.

RequirementWhat it meansWho it applies to
Valid SPF or DKIMAt least one must pass for your sending domainAll senders
DMARC recordA DMARC policy must exist — p=none is acceptable to startBulk senders (5,000+ emails/day)
DMARC alignmentThe From domain must align with SPF or DKIMBulk senders
One-click unsubscribeMarketing emails must include a working unsubscribe linkBulk/marketing senders
Spam rate below 0.1%Keep spam complaints under 1 in 1,000 emails sentBulk senders
Valid PTR recordSending IP must have a valid reverse DNS recordAll senders

Even if you're not a bulk sender, Google's spam filters still heavily weight SPF, DKIM, and DMARC when making filtering decisions for all incoming email. Failing these checks makes you significantly more likely to land in spam regardless of your sending volume.

The most common causes of Gmail-specific spam issues

1. Missing or failing DMARC

This is the number one cause of Gmail-specific spam problems. Gmail places enormous weight on DMARC — more so than most other providers. If your domain has no DMARC record, or has one set to p=none without proper SPF/DKIM alignment, Gmail will treat your emails with heightened suspicion.

Outlook may still deliver these emails because it uses different weighting. Gmail often won't.

2. DMARC alignment failure

This is more subtle and often catches people out. DMARC alignment means the domain in your email's "From" address must match the domain that passed SPF or DKIM. If you're sending from [email protected] but your email is being relayed through a third-party service that signs with a different domain, DMARC alignment will fail — even if SPF and DKIM both technically pass.

From: [email protected] DKIM signature: d=mailservice.com ← DMARC alignment FAIL SPF pass: mailservice.com ← DMARC alignment FAIL The From domain (yourcompany.ca) doesn't match either the DKIM or SPF domain — DMARC fails.

3. Sending through a third-party tool without proper setup

If you send marketing emails through Mailchimp, HubSpot, Constant Contact, or any similar platform, that platform needs to be explicitly authorised in your SPF record AND needs DKIM configured for your domain. Many businesses set up their marketing tool but never update their DNS records to authorise it — causing Gmail to flag every marketing email as suspicious.

4. Shared IP reputation

If you're on shared hosting, you may be sharing an IP address with other senders. If any of those senders have been flagged by Gmail for spamming, the shared IP's reputation suffers — which can affect your deliverability even if your own authentication is perfect. Gmail is particularly sensitive to IP reputation.

5. No PTR (reverse DNS) record

Gmail specifically checks that the IP address your email is sent from has a valid reverse DNS record — called a PTR record. This is less common for small businesses using established email providers (Google Workspace, Microsoft 365), but can be an issue if you're using a VPS or custom mail server setup.

Is Gmail specifically blocking your emails?

I'll audit your domain, identify the exact cause, and give you clear instructions to fix it — usually within 24–48 hours.

Get my Gmail issue fixed →

Flat fee $200–$500 · No login credentials required · 23 years IT experience

Why DMARC alignment matters specifically for Gmail

DMARC alignment is worth understanding in more detail because it's the most commonly misunderstood cause of Gmail-specific failures.

DMARC has two alignment modes — relaxed and strict. In relaxed mode (the default), the organizational domain just needs to match. In strict mode, the domains must be identical.

From addressDKIM domainRelaxed alignmentStrict alignment
[email protected]yourcompany.ca✓ Pass✓ Pass
[email protected]yourcompany.ca✓ Pass✗ Fail
[email protected]mailchimp.com✗ Fail✗ Fail
[email protected]mcsv.net✗ Fail✗ Fail

The third and fourth rows are the most common problem. When you send through Mailchimp, by default the DKIM signature uses Mailchimp's domain — not yours. Gmail sees the From address claiming to be yourcompany.ca but the DKIM signature from mcsv.net and DMARC alignment fails.

The fix is to set up custom domain authentication in Mailchimp (or whichever tool you use) — this adds a DKIM record to your own DNS so Mailchimp signs emails with your domain, not theirs.

Are you sending bulk or marketing emails?

If you send newsletters, promotions, or any kind of bulk email to Gmail addresses, Google's 2024 requirements are mandatory for you. Here's a quick checklist:

💡 Google Postmaster Tools If you send significant volume to Gmail, register your domain at postmaster.google.com — it's free and shows you your domain reputation, spam rate, and authentication status directly from Google's perspective. It's one of the most useful diagnostic tools available.

How to fix Gmail spam issues step by step

Step 1 — Check your current authentication status

Go to mxtoolbox.com and run SPF, DKIM, and DMARC checks for your domain. Note any failures or warnings.

Also go to mail-tester.com, copy the test address, send a normal email to it, then check your score. Pay attention to any Gmail-specific warnings.

Step 2 — Fix SPF

Make sure your SPF record includes every service that sends email on your behalf. If you use Google Workspace, Mailchimp, and your hosting provider's email, all three need to be in your SPF record.

v=spf1 include:_spf.google.com include:servers.mcsv.net include:_spf.hostinger.com ~all

Step 3 — Set up DKIM for every sending service

Each email platform you use (Google Workspace, Mailchimp, HubSpot etc.) has its own DKIM setup process. You need to generate DKIM keys in each platform and add the corresponding TXT records to your DNS. Don't just do it for your main email — do it for every service you send from.

Step 4 — Add or fix DMARC

If you don't have a DMARC record, add one. Start with p=none to monitor without affecting delivery, then escalate to p=quarantine after reviewing reports for a couple of weeks.

v=DMARC1; p=quarantine; rua=mailto:[email protected]; pct=100

Step 5 — Set up custom domain authentication in your marketing tool

If you use Mailchimp, HubSpot, or any other email marketing platform, find the "Domain Authentication" or "Custom DKIM" setting and follow their setup instructions. This is the step most people miss — and it's exactly why their marketing emails fail Gmail specifically.

Step 6 — Wait and verify

DNS changes take 24–48 hours to propagate. After that, re-run your MXToolbox checks and send another mail-tester.com test. Send a real test email to a Gmail address and check where it lands.

How to test if your fix worked

✅ How to view email headers in Gmail Open any email you sent to a Gmail address, click the three dots (⋮) in the top right of the email, and select "Show original." You'll see a summary at the top showing SPF, DKIM, and DMARC pass or fail results — this is the most direct way to see what Gmail thinks of your emails.

Still landing in Gmail spam after trying these fixes?

Gmail deliverability issues can be tricky to diagnose on your own — especially DMARC alignment failures with third-party senders. I'll audit your full setup and tell you exactly what's wrong.

Get my email fixed →

From $200 flat fee · 24–48hr turnaround · Guided walkthrough included

👩‍💻

Written by Lina K — Inlet Digital

Lina has 23 years of IT experience and has personally configured email authentication records for 200+ domains. She has managed Proofpoint's enterprise email security platform — including Email Fraud Defense, TAP, and TRAP — giving her a unique perspective on both why emails get blocked and exactly how to fix it. She now helps small businesses across Canada resolve email deliverability issues for a flat fee.