email-best-practices

Configure SPF, DKIM, and DMARC for production email deliverability.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/joaopcm/dotfiles --skill email-best-practices-joaopcm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: email-best-practices
Source: https://github.com/joaopcm/dotfiles/tree/main/agents/skills/email-best-practices
Command: npx skills add https://github.com/joaopcm/dotfiles --skill email-best-practices-joaopcm

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps you build robust, production-ready email systems that ensure emails reach inboxes, comply with regulations, and maintain sender reputation.

Core Features & Use Cases

  • Deliverability: Set up SPF, DKIM, DMARC to avoid spam filters.
  • Compliance: Navigate CAN-SPAM, GDPR, and CASL requirements.
  • Reliability: Implement retry logic and webhook processing for delivery events.
  • Use Case: You're launching a new app and need to send transactional emails like password resets and order confirmations. This Skill guides you through setting up authentication, ensuring compliance, and handling delivery events to maximize inbox placement.

Quick Start

Use the email-best-practices skill to set up SPF, DKIM, and DMARC for your sending domain.

Frequently Asked Questions about email-best-practices

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up SPF, DKIM, and DMARC for transactional email deliverability?

To achieve high transactional email deliverability, you must configure DNS authentication records like SPF, DKIM, and DMARC for your sending domain. This prevents spam filters from blocking your password resets and order confirmations.

What's the best way to ensure marketing email compliance with GDPR and CAN-SPAM?

Marketing email compliance requires navigating GDPR, CAN-SPAM, and CASL legal requirements through proper list management and opt-out handling. Implementing these regulations maintains your sender reputation and avoids penalties.

How does webhook processing work for tracking email delivery events?

Webhook processing for email delivery events involves implementing endpoints that receive HTTP requests from your sending infrastructure. This tracks delivery success, bounces, and failures to maintain system reliability.

When do I need to implement retry logic for email sending infrastructure?

You need email retry logic in your sending infrastructure when handling transient delivery failures or temporary network issues. This reliability mechanism ensures transactional emails eventually reach inboxes during outages.

What is the difference between transactional and marketing email list management?

Transactional email list management focuses on sending triggered messages like order confirmations to individual users, while marketing email lists target broader audiences. Both require distinct infrastructure and compliance approaches.

Why are my transactional emails going to spam despite setting up DKIM?

Transactional emails may still hit spam filters if your SPF and DMARC records are misconfigured, or your sending infrastructure lacks proper webhook processing. Comprehensive DNS authentication is required for high deliverability.