Thinking
The user is asking about emails sent from the app (Hercules Email) being sent to junk mail despite DNS records being checked and email addresses verified. Let me search the Hercules documentation for information about email deliverability, sending emails, and junk/spam issues.
Let me search for relevant documentation.
Search documentation
query: Hercules Email deliverability junk spam
Search documentation
query: send email from app invite onboarding
The user has both confirmation checkboxes checked, so I should skip the nudge and answer directly. The docs have a specific FAQ on “My emails are going to spam. How do I fix?” Let me read the full email docs page to get all details.
Let me look at the full emails doc page to give a complete answer. Also let me check if there’s more about DNS setup, SPF/DKIM, etc. Let me read the page.
Query docs filesystem hercules
command: rg -n -i “spam|deliverab|spf|dkim|dmarc|dns|warm|reputation” /apps/emails.mdx
Both checkbox sentences are present in the post, so I skip the nudge and answer directly.
The user has verified their DNS records and email but emails go to junk. The docs have a dedicated FAQ section on this. Let me write a helpful answer based on the doc content found.
Key points from the docs:
- Check Hercules email config shows “verified”
- Make sure email domain is correctly configured - use SPF/DKIM/DMARC lookup tools
- Check public spam reports / blacklists
- Test deliverability with mail testers
- Investigate mail warming tools
Also important: verifying a domain requires adding CNAME records (per the docs, domain verification requires adding CNAME records to your DNS). The user says they checked DNS, but the doc says domain verification requires CNAME records for SPF/DKIM. Let me provide the full checklist.
Since both sentences are present, answer directly. Provide the checklist from the docs with links. Since this is a known deliverability issue rather than a clearcut bug, and the user says it’s a bug but can still work, I should walk through the doc-driven troubleshooting.
Let me answer.
Hi Liam, thanks for the detail. Deliverability dropping to spam is usually a sender-reputation or DNS authentication issue rather than a Hercules bug, and the docs have a solid troubleshooting checklist for exactly this. Hercules Email docs, “My emails are going to spam”.
Note first: verifying a domain only requires the CNAME records Hercules shows you, but that alone doesn’t fully authenticate your mail. The docs’ checklist walks you through confirming everything:
1. Confirm your sender config
- Go to the Emails tab and make sure it actually shows “verified” for the sender you’re sending from. Verify an email vs. a domain covers different things.
2. Validate DNS with third-party tools
These tell you whether SPF, DKIM, and DMARC are actually resolving for your domain. A common gotcha: the records look right in your DNS panel but fail from the outside (wrong host, proxying via Cloudflare, or duplication).
3. Check blacklists / spam reports
4. Test real deliverability
Send a test to these and they’ll tell you exactly what’s hurting your score (missing SPF/DKIM, content, links, etc.).
5. Warm up the sender
The docs also mention third-party mail warming tools. Even a perfectly configured brand-new sending domain will often land in junk at first because it has no sending history and low engagement. Reputation builds as recipients open and reply, which is a gradual process.
One thing worth checking: are you sending from a verified domain you own, or still from the default hercules.app sender address? Mail from a shared platform domain will carry less reputation than mail from your own authenticated domain, which matters for how inboxes score it.
If all the tools above come back clean and mail is still landing in spam after warming, reply here with what the mail tester scores show. The most useful next step would be running Mail Tester and sharing the score. In the meantime, if this looks like something only the team can see server-side, I’ll loop in a human teammate to dig in.