spam-test
Skill8 starsChanged 6 months agoMITView on GitHub
Run a Smartlead Smart Delivery spam test on a campaign's sender mailboxes. Reports inbox placement %, DKIM/SPF/DMARC auth status, blacklist status, and rDNS/IP reputation. Use before launching a campaign, when a campaign's reply rate suddenly drops, or when the user asks to run a spam test, check inbox placement, or audit deliverability infrastructure.
In this repository11 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- audit-mailbox-configSkill
- check-deliverabilitySkill
- clone-campaignSkill
- compare-campaignsSkill
- create-campaignSkill
- launch-campaignSkill
- smartlead-onboardingSkill
- upload-leadsSkill
- warmup-mailboxesSkill
- weekly-reportSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 104
If the user fixes something (publishes a DKIM record, etc.), wait 1-4 hours for DNS propagation, then re-run the spam test on the same …
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Before running: verify exact flag names with
smartlead <command> --help. Flag shapes shown below are illustrative — confirm against the actual CLI.
/spam-test
You're running a Smart Delivery spam test to check inbox placement and authentication health.
What you need from the user
- What to test — a campaign (test all senders), or specific mailbox IDs?
Step 1 — Kick off the test
For a campaign's senders
smartlead delivery start-test --campaign-id <campaign_id>For specific mailboxes
smartlead delivery start-test --mailbox-ids <id1>,<id2>Save the returned spam_test_id.
The test sends a test email from each sender to a panel of seed inboxes across major ESPs (Gmail, Outlook, Yahoo, etc.). Takes ~15 minutes.
Step 2 — Poll for completion
smartlead delivery test-status <spam_test_id>Status flow: RUNNING → COMPLETED (or FAILED).
Poll every 60 seconds. Don't poll faster — wastes API budget.
Step 3 — Get the full report
smartlead delivery test-details <spam_test_id> --output json > report.jsonOr per-aspect:
smartlead delivery dkim-details <spam_test_id> # DKIM auth status
smartlead delivery spf-details <spam_test_id> # SPF auth status
smartlead delivery rdns-report <spam_test_id> # Reverse DNS
smartlead delivery ip-details <spam_test_id> # IP reputation
smartlead delivery spam-filter-report <spam_test_id> # Per-ESP placementStep 4 — Interpret results
For each sender, report:
| Metric | Healthy | Concerning |
| Inbox % (Gmail) | >85% | <70% |
| Inbox % (Outlook) | >80% | <60% |
| DKIM | PASS | FAIL or NEUTRAL |
| SPF | PASS | SOFTFAIL or FAIL |
| DMARC | PASS | FAIL |
| rDNS | matches sender domain | mismatch or missing |
| IP blacklists | 0 hits | any hit (esp Spamhaus, SORBS) |
Common failure patterns
| Pattern | Cause | Fix |
| DKIM FAIL | Missing or wrong DKIM DNS record | Republish DKIM TXT record at the right selector |
| SPF SOFTFAIL | Missing sending IP from SPF | Add Smartlead's sending IPs to SPF, or use include: |
| DMARC FAIL with SPF/DKIM PASS | Alignment issue — mail.from domain != From: domain | Use same sending domain for both |
| Low inbox % on Gmail despite DKIM/SPF pass | Reputation issue (warmup incomplete, content trigger, IP blocked) | More warmup, change copy, change sending IP |
| Outlook inbox 0% | Recipient on Microsoft 365 + bad sender reputation | Wait for warmup to mature, audit signature for spam triggers |
Step 5 — Recommendations
Group findings by severity:
🔴 BLOCKERS — fix before launching
- DKIM FAIL on any sender
- SPF FAIL on any sender
- Inbox % <50% on majority of senders
🟡 WARNINGS — fix soon, not blocking
- DMARC FAIL but DKIM+SPF pass
- One sender significantly worse than others (consider pausing it)
- Inbox % 50-70%
🟢 NICE-TO-HAVE
- DMARC quarantine vs reject policy
- BIMI not configured
Step 6 — Re-test after fixes
If the user fixes something (publishes a DKIM record, etc.), wait 1-4 hours for DNS propagation, then re-run the spam test on the same senders.
Reference
- Smartlead's Smart Delivery docs: https://api.smartlead.ai/api-reference/smart-delivery (or via
docs/reference/endpoint-index.tsv) docs/learnings/mailbox-warmup-best-practices.md— reputation building
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

