Email deliverability testing

Severity: Recommended

Email deliverability testing ensures your emails reach the inbox, not spam. This includes spam scoring tools and periodic placement tests with fresh accounts.

Check automatically:

1. Check for automated email testing in CI/CD:

grep -riE "mail-tester|spamassassin|glockapps|litmus|email.*score|deliverability" .github/workflows/*.yml scripts/ 2>/dev/null

2. Check for deliverability monitoring in codebase:

grep -riE "spam.*score|deliverability|placement.*test" --include="*.md" --include="*.yml" . 2>/dev/null | grep -v node_modules

Ask user:

• "What tool do you use to test spam score?" (mail-tester.com, GlockApps, Litmus, etc.)
• "Do you periodically test placement with fresh accounts?"
• "What providers do you test against?" (Gmail, Outlook, Yahoo, etc.)
• "How often do you run these tests?" (monthly, quarterly, after major changes)
• "Where do your emails typically land?" (Inbox, Promotions, Spam)

Pass criteria:

• Spam scoring tool identified and used periodically
• Placement tests with fresh accounts performed (at minimum: Gmail, Outlook)
• Testing cadence defined (monthly or quarterly minimum)

Recommended (bonus):

• Automated spam scoring in CI/CD or scheduled job

Fail criteria:

• No spam scoring tool
• Never tested placement with fresh accounts
• Only tested once at initial setup, never since

Evidence to capture:

• Spam scoring tool used
• Placement testing cadence
• Providers tested (Gmail, Outlook, Yahoo, etc.)
• Typical results (inbox vs promotions vs spam)
• Manual vs automated
• Recent score/results if available

---