email-best-practices

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Email programs often fail to reach the inbox or comply with global regulations, causing deliverability issues and legal risk.

Core Features & Use Cases

  • SPF/DKIM/DMARC setup guidance with DNS records and rollout strategy
  • Unsubscribe management, List-Unsubscribe header configuration, and suppression workflows
  • Webhook processing, delivery event handling, and region-aware compliance planning
  • Idempotent sending, retry logic, and rigorous data retention policies for marketing and transactional emails

Quick Start

Configure SPF/DKIM/DMARC for your domain and implement unsubscribe, webhooks, and retry logic according to regional rules.

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 records for email deliverability?

To set up SPF, DKIM, and DMARC for email deliverability, configure the appropriate DNS TXT records for your domain and follow a phased DMARC rollout strategy starting with a none policy to monitor authentication results before enforcement.

What's the best way to manage email unsubscribes and opt-out compliance?

The best way to manage email unsubscribes and opt-out compliance is by implementing List-Unsubscribe headers, maintaining suppression workflows, and enforcing per-region unsubscribe timing rules to ensure regulatory adherence across different jurisdictions.

How do email webhooks work for processing delivery events?

Email webhooks work by receiving real-time HTTP POST requests from your email provider containing delivery event data, which you process to handle bounces, complaints, and suppressions while maintaining idempotent receiving logic to prevent duplicate actions.

Do I need different email compliance rules for transactional versus marketing emails?

Yes, you need different compliance rules for transactional versus marketing emails. Transactional emails require robust retry logic and error handling, while marketing emails demand strict opt-in management, unsubscribe processing, and rigorous data retention policies.

Why are my emails not reaching the inbox despite passing SPF and DKIM checks?

Emails may fail to reach the inbox despite passing SPF and DKIM checks if DMARC alignment is incorrect, suppression workflows are not filtering bounced addresses, or retry logic lacks idempotent sending capabilities causing duplicate message delivery.