Why Business Email Goes to Spam (and How to Fix It)
If MailShrine webmail sends fine but Gmail/Outlook files you under Spam, start with authentication and DNS, then content and reputation — in that order.
Real-life example: BrightLedger
Tomi’s invoices vanished into spam for two enterprise clients. Root causes: duplicate SPF + no DMARC + subject lines with “URGENT PAYMENT!!!” on a week-old domain.
Common causes → fixes
| Symptom / cause | Fix |
|---|---|
| Missing/failing SPF | SPF guide — one merged TXT |
| DKIM fail / missing | DKIM setup |
| No DMARC | Start p=none (DMARC) |
| Old MX leftovers | Clean MX (MX) |
| Brand-new domain | Warm with real conversations; avoid blasts |
| Spammy content | Plain tests first; fix links/attachments |
| Shared IP learning | Consistent legit volume beats panic sending |
What you need
Access to MailShrine Domains + a Gmail “Show original” view + DNS panel.
Step 1: Confirm MailShrine verification
Domains should show Verified for MX + auth records.
Step 2: Read one message’s headers
Look for spf=pass, dkim=pass, dmarc=pass (or none policy).
Step 3: Fix the first failing layer
Don’t change everything at once. Prefer SPF merge or DKIM paste before content rewrites.
Step 4: Retest with boring content
Subject: Test from BrightLedger. Body: one sentence + your name.
Step 5: Only then tune reputation
Ask contacts to move to inbox / add to contacts. Avoid purchased lists.
Checklist
- Auth verified in MailShrineCompleted
- Headers reviewedCompleted
- Failures fixedCompleted
- Clean retest sentCompleted
Common mistakes
- Blaming “the algorithm” before DNS.
- Buying random “spam fixer” tools first.
- Sending marketing blasts from a cold mailbox (Email Marketing is a different product).
Next steps
Citations & References
- Reference: Google: Email sender guidelines
- Reference: Cloudflare Learning Center: DNS records
- Reference: ICANN: What is DNS?
Written by Ben K., Email Authentication Specialist. Ben diagnoses spam folder issues for SMEs after DNS cutovers.
