email-infrastructure
Email delivery infrastructure - DNS authentication (SPF/DKIM/DMARC), subdomain isolation, provider abstraction, template systems, bounce handling, warmup strategy, and deliverability monitoring.
npx skills add vibeeval/vibecosystem --skill email-infrastructure --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Email Infrastructure Production email delivery requires DNS authentication, domain isolation, and provider-agnostic architecture. A single misconfiguration can land your entire domain in spam. ## GOOD vs BAD: Domain Strategy ``` BAD: Send bulk marketing from example.com → Spam complaints tank your main domain reputation → Transactional emails (password reset, receipts) start landing in spam → Recovery takes weeks of warmup GOOD: Subdomain isolation with separate reputations → mail.example.com for transactional (password reset, receipts, 2FA) → notify.example.com for product notifications (comments, mentions) → marketing.example.com for bulk campaigns (newsletters, promotions) → Each subdomain has independent reputation — one bad campaign does not poison the rest ``` ## DNS Authentication: SPF + DKIM + DMARC ``` # SPF — declare which servers can send from your domain mail.example.com TXT "v=spf1 include:_spf.provider.com ~all" # DKIM — cryptographic signature on every email selector._domainkey.mail.example.com TXT "v=DKIM1; k=rsa; p=MIGf..." # DMARC — policy for failed authentication (progressive rollout) # Week 1-2: monitor only _dmarc.mail.example.com TXT "v=DMARC1; p=none; rua=
- GOOD vs BAD: Domain Strategy
- DNS Authentication: SPF + DKIM + DMARC
- Email Provider Abstraction
- Transactional vs Marketing Separation
- Template System (MJML)
- Bounce and Complaint Handling
- Domain Warmup Strategy
- Deliverability Monitoring
- Pre-Send Checklist
What does the email-infrastructure skill do?
Email delivery infrastructure - DNS authentication (SPF/DKIM/DMARC), subdomain isolation, provider abstraction, template systems, bounce handling, warmup strategy, and deliverability monitoring.
How do I install it?
Run `npx skills add vibeeval/vibecosystem --skill email-infrastructure --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From vibeeval/vibecosystem, a repository with 521 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.