- Home
- Skills
- APIs & Backend
- mail deliverability doctor
Works with the AI Agents you already use
mail deliverability doctor
Diagnose email bounces, audit SPF/DKIM/DMARC, and fix delivery issues for Gmail, Outlook, and Yahoo.
Free
mail deliverability doctor
Example session with this skill installed
My emails to Gmail are bouncing with error 5.7.26 and I think my SPF record is broken. Can you check my domain example.com and the sending IP 1.2.3.4?
- Read your context and instructions
- Compiled the mail deliverability doctor
I have audited the DNS configuration for example.com and the reputation of IP 1.2.3.4. The SPF record is currently failing because the sending IP is not included in the allowed list, and the record exceeds the 10-lookup limit.
Diagnostic Report
| Test | Result | Details |
|---|---|---|
| SPF Record | FAIL | v=spf1 include:_spf.google.com include:sendgrid.net include:mail.zendesk.com ~all (11 lookups) |
| DKIM (default) | PASS | Valid signature found for selector default |
| DMARC | WARN | Policy is p=none; no alignment issues found but reporting is disabled |
| Reverse DNS | PASS | 1.2.3.4 resolves to mail.example.com |
| Blocklists | CLEAN | IP 1.2.3.4 is not listed on 8 major public lists |
The bounce code
5.7.26 confirms Gmail is rejecting the mail because the SPF check failed and the message is unauthenticated. Your current SPF record has too many include statements, causing recursive lookups to exceed the maximum of 10.
Proposed Fix: Optimized SPF Record
# Replace your current TXT record for example.com with this:
v=spf1 ip4:1.2.3.4 include:_spf.google.com include:sendgrid.net -all
Next steps
- Update the SPF TXT record in your DNS control panel with the optimized version above.
- Wait for the TTL (currently 3600s) to expire before testing again.
- Run
check-server.shon your mail server to verify the HELO string matchesmail.example.com.
Connects securely to your tools. The creator never sees your data.
About this skill
Mail is bouncing or landing in junk folders because of authentication failures, reputation issues, or misconfigured servers. This skill diagnoses the specific technical cause of email delivery failure and provides the exact DNS or server configurations required to fix it.
What it does
- DNS auditing verifies SPF trees, DKIM keys, DMARC alignment, and MTA-STS records to find configuration gaps.
- Server diagnostics analyzes Postfix or Exim logs to group bounces by error code and identify top internal spam sources.
- IP reputation checks queries public blocklists and validates PTR records, HELO names, and forward-confirmed reverse DNS.
- Header analysis parses raw email headers to detect alignment issues between ESPs and sender domains.
- Record generation produces merged SPF records and staged DMARC policies ready for manual deployment.
How it works
- Analyze symptoms by looking up bounce codes (like S3140 or 5.7.26) in the provider reference database.
- Audit technical setup using
check-domain.shandcheck-ip.shto identify authentication or reputation failures. - Inspect server logs with
check-server.shto find the specific volume of deferrals and identify compromised accounts. - Generate fixes using
gen-records.shto create the exact DNS strings or config edits needed for the specific environment.
Frameworks & tools
The skill uses standard Linux networking utilities including dig, openssl, curl, and bash. It supports Postfix and Exim environments on cPanel, Plesk, DirectAdmin, or bare Linux servers.
Why this beats prompting it yourself
Email deliverability involves complex lookup limits, recursive SPF includes, and strict header alignment rules that generic LLMs often hallucinate. This skill uses local diagnostic scripts to pull live data from your server and DNS, ensuring the solution is based on real-world state rather than assumptions.
Use cases
- Fix "unauthenticated mail" warnings or junk placement in Gmail and Outlook.
- Resolve 5.7.1 or 5.7.26 bounce errors caused by SPF/DKIM/DMARC failures.
- Secure a mail server after a spam outbreak by finding the exploited script or account.
- Migrate email to a new provider while maintaining authentication alignment.
Known limitations
Does not support changing DNS records or server configs directly. Blocklist checks may fail if using public DNS resolvers like Google or Cloudflare due to provider rate limits.
Read-only tool; users must manually apply suggested DNS and config changes. Spamhaus queries may be refused if the system uses large public resolvers.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
This skill has been used 1 time.
Trust & safety
Security scan
Security scan passed 16 days ago
- Free with an Agensi account
Permissions
Allowed Hosts