email-best-practices

Configure SPF, DKIM, and DMARC authentication with compliance guidance.

1|Updated Oct 27, 2025
One-click install
npx skills add https://github.com/sandrasocial/sselfie-9g --skill email-best-practices-sandrasocial
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: email-best-practices
Source: https://github.com/sandrasocial/sselfie-9g/tree/main/.agents/skills/email-best-practices
Command: npx skills add https://github.com/sandrasocial/sselfie-9g --skill email-best-practices-sandrasocial

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the challenges of sending reliable, compliant, and user‑friendly emails by providing comprehensive guidance on authentication, deliverability, consent capture, webhook handling, and distinguishing transactional from marketing communications.

Core Features & Use Cases

  • Authentication Setup: Detailed steps for SPF, DKIM, and DMARC configuration to prevent spam folder placement.
  • Compliance Guidance: Covers CAN‑SPAM, GDPR, and CASL requirements for consent and unsubscribe handling.
  • Reliability Engineering: Implements idempotent sending, retry logic, and webhook processing for delivery events.
  • Strategic Planning: Helps decide when to use transactional versus marketing emails and outlines a catalog of essential transactional messages.
  • Use Case Example: A SaaS product can follow this Skill to configure its email service, ensure legal compliance, and maintain high sender reputation across both onboarding and promotional campaigns.

Quick Start

Ask the email-best-practices skill for a step‑by‑step guide to set up SPF/DKIM/DMARC and ensure CAN‑SPAM compliance.

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 email authentication?

Email authentication requires configuring SPF, DKIM, and DMARC DNS records to verify your sending domain and prevent spam folder placement. This ensures receiving servers trust your messages and maintain your sender reputation.

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

Transactional emails convey essential account or service updates requiring no consent, while marketing emails require explicit opt-in consent and unsubscribe options. Distinguishing them is critical for meeting CAN-SPAM, GDPR, and CASL regulations.

How do I ensure GDPR and CASL compliance for email consent capture?

GDPR and CASL compliance requires capturing explicit user consent before sending marketing emails and providing clear unsubscribe mechanisms. You must document consent records and immediately process opt-out requests to meet legal standards.

Why are my transactional emails going to the spam folder?

Transactional emails go to the spam folder when SPF, DKIM, or DMARC authentication records are missing or misconfigured. Proper DNS setup and maintaining a strong sender reputation are required to ensure reliable inbox placement.