email-best-practices

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Guidance for building deliverable, compliant, user-friendly emails that reach inboxes, respect user consent, and reduce spam risk across transactional and marketing flows.

Core Features & Use Cases

  • Email authentication guidance: SPF, DKIM, and DMARC setup with practical DNS records and rollout strategies.
  • Compliance & consent coverage: CAN-SPAM, GDPR, CASL, unsubscribe handling, consent recording, and data retention considerations.
  • Operational reliability: Webhooks integration, idempotent sends, retry strategies, suppression/list hygiene, and cross-region considerations.
  • Decision guidance: Clear criteria for distinguishing transactional vs marketing emails to optimize deliverability and legal compliance.

Quick Start

Configure DNS authentication for a new domain, enable double opt-in, add List-Unsubscribe headers, and implement a basic retry path for failed sends.

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?

Email deliverability improves by configuring SPF, DKIM, and DMARC DNS records to authenticate sending domains, adding practical TXT records, and applying a phased DMARC rollout strategy from monitoring to enforcement to protect against spoofing.

What is the difference between transactional and marketing emails for compliance?

Transactional emails convey account or service information, while marketing emails promote products and require explicit consent. Distinguishing them optimizes deliverability and ensures compliance with CAN-SPAM, GDPR, and CASL consent and unsubscribe regulations.

How do I implement List-Unsubscribe headers and consent management for GDPR and CASL?

GDPR and CASL compliance requires implementing double opt-in consent recording, adding List-Unsubscribe headers to marketing emails, and managing data retention. You must track user consent states and provide accessible unsubscribe mechanisms across marketing flows.

Why do I need idempotent retry logic and webhooks for transactional email sending?

Idempotent retry logic and webhooks ensure operational reliability for transactional email sending by preventing duplicate messages during network failures and processing delivery status updates. This maintains list hygiene through suppression management and handles failed sends gracefully.

Does this email compliance guidance apply to SaaS apps sending cross-region marketing emails?

Yes, the guidance applies to SaaS apps and marketing platforms sending cross-region emails, covering CAN-SPAM, GDPR, and CASL compliance. It handles domain authentication, consent recording, and cross-region considerations for transactional and marketing flows.