Email Specifications
A platform-agnostic technical specification for transactional and lifecycle email.30 topics total.
Foundations
3 topicsMessage format, headers, MIME, identity, and the envelope.
Internet Message Format (RFC 5322)
RequiredConstruct structurally valid email messages adhering to RFC 5322 grammar, strict CRLF line endings, 998-character line limits, and standard header folding rules.
Essential Email Header Fields
RequiredEmit mandatory RFC 5322 header fields (From, Date, Message-ID), structured recipient fields, and machine-readable metadata while preventing header duplication.
MIME Multipart Message Structure
RequiredStructure rich email payloads using standardized MIME multipart trees (alternative, related, mixed), paired plain-text fallbacks, and collision-resistant boundary delimiters.
Authentication
3 topicsSPF, DKIM, DMARC, transport security, and domain trust.
Sender Policy Framework (SPF)
RequiredPublish a single, bounded SPF policy that authorizes legitimate envelope senders without exceeding the 10-DNS-lookup limit or using overly permissive qualifiers.
DomainKeys Identified Mail (DKIM) Signatures
RequiredCryptographically sign outgoing email messages with DKIM using aligned domains, minimum 2048-bit keys, canonicalization, and regular selector rotation.
Domain-based Message Authentication, Reporting, and Conformance (DMARC)
RequiredEnforce domain-aligned email authentication with a DMARC policy that instructs receivers how to handle unauthenticated mail and generates aggregate feedback reports.
Deliverability
3 topicsReputation, list quality, bounces, and inbox placement.
Reverse DNS (PTR) & Forward-Confirmed Reverse DNS (FCrDNS)
RequiredConfigure Forward-Confirmed Reverse DNS (FCrDNS) on every sending IP address, ensuring the PTR record matches the forward A/AAAA record and the SMTP EHLO greeting.
Mailing List Hygiene & Recipient Validation
RequiredMaintain pristine sender reputation through automated bounce management, double opt-in confirmation, inactive subscriber sunsetting, and spam trap avoidance.
Spam Complaint Handling & Feedback Loops (FBL)
RequiredProcess user spam complaints in real-time through ISP Feedback Loops (FBL) and RFC 5965 Abuse Reporting Format (ARF) to maintain spam complaint rates below 0.10%.
Accessibility
3 topicsReadable, operable messages for people of all abilities.
Semantic HTML Structure & Screen Reader Accessibility
RecommendedStructure email markup with true semantic HTML elements (h1-h3, p, ul, ol), document language declarations, and clear hierarchical reading order.
Color Contrast & Dark Mode Adaptation in Email
RecommendedMeet WCAG 2.2 AA contrast standards (minimum 4.5:1) while architecting email designs for dark mode color inversions across Outlook, Apple Mail, and Gmail.
Accessible Image Alt Text & Image-Off Fallbacks
RequiredProvide meaningful alternative text for informative images, null alt attributes for decorative graphics, and styled fallbacks when remote images are blocked.
Rendering
3 topicsHTML and CSS that survive real-world email clients.
Cross-Client HTML Table Layout Architecture
RecommendedConstruct bulletproof HTML email scaffolds using presentation tables, role="presentation" ARIA semantics, 600px max-width containers, and Microsoft Outlook ghost tables.
CSS Inlining & Cross-Client Style Compatibility
RecommendedInline critical CSS rules directly onto HTML elements to survive webmail style-stripping while leveraging embedded style blocks for media queries and dark mode.
Responsive Email Layout & Fluid-Hybrid Design
RecommendedDesign responsive email templates using fluid-hybrid layouts, mobile-first breakpoints, single-column column stacking, and 44x44px touch targets.
Privacy
3 topicsConsent, tracking, data minimisation, and respectful measurement.
Tracking Pixels, Remote Image Privacy & Apple MPP
RecommendedUnderstand remote tracking pixel mechanics, Apple Mail Privacy Protection (MPP) proxy caching, GDPR/ePrivacy compliance, and pseudonymized analytics.
Consent Provenance & Audit Trails
RequiredMaintain immutable cryptographic records of subscriber consent, capturing timestamps, IP addresses, signup URLs, form identifiers, and policy versions for regulatory compliance.
PII Protection & Data Minimisation in Email
RequiredMinimize Personally Identifiable Information (PII) transmitted across email bodies and URL parameters, enforcing masking, TLS transport, and ephemeral log retention.
Internationalisation
3 topicsUnicode, language, direction, and international addresses.
UTF-8 Encoding & Multilingual Message Bodies
RequiredStandardize on end-to-end UTF-8 encoding across email headers and MIME bodies using Quoted-Printable or Base64 transfer encodings to prevent character corruption.
Language Direction & Right-to-Left (RTL) Layouts
RecommendedArchitect bidirectional and Right-to-Left (RTL) email layouts with document-level dir="rtl" declarations, mirrored table alignments, and isolated BiDi spans.
Internationalized Email Addresses (EAI) & Punycode
RecommendedSupport Internationalized Domain Names (IDN) via Punycode and handle non-ASCII local-parts using RFC 6530 Email Address Internationalization (EAI) and SMTPUTF8.
Lifecycle
3 topicsSubscription, unsubscribe, complaints, retries, and expiry.
One-Click List-Unsubscribe (RFC 8058)
RequiredImplement RFC 8058 one-click list unsubscribe headers with HTTP POST endpoints, mailto fallbacks, DKIM signature protection, and zero login barriers.
Automated Bounce Handling & Delivery Status Notifications (DSN)
RequiredClassify and process hard and soft delivery failures using RFC 3463 enhanced status codes, Variable Envelope Return Path (VERP), and instant suppression automation.
SMTP Retry Scheduling & Queue Expiry
RequiredConfigure outbound SMTP queue management with exponential backoff, randomized jitter, greylisting survival delays, and strict 72-to-120-hour queue retention limits.
Security
3 topicsInjection, dangerous content, phishing resistance, and secrets.
Email Header Injection & CRLF Neutralization
RequiredPrevent SMTP and RFC 5322 header injection vulnerabilities by neutralizing CRLF control characters and using typed mail serialization libraries.
Secure Hyperlinks & Click-Tracking Integrity
RequiredEnforce HTTPS-only hyperlinks, eliminate phishing link text mismatches, and protect email click-tracking redirects against open redirect vulnerabilities using HMAC signatures.
Dangerous Content & Prohibited Email Elements
RequiredEliminate prohibited active content (JavaScript, iframes, embedded objects, raw forms) and restrict high-risk file attachment extensions to prevent malware classification.
Automation
3 topicsMachine-readable actions, calendars, receipts, and agent use.
Schema.org Email Markup & Gmail Actions
OptionalEmbed structured Schema.org JSON-LD markup in transactional emails to render interactive One-Click Actions, order summaries, and flight/event cards in Gmail and Apple Mail.
iCalendar (iMIP) Automated Calendar Invitations
RecommendedPublish standards-compliant calendar meeting invites, updates, and cancellations using iCalendar (RFC 5545) and iMIP (RFC 6047) multipart attachments.
MIME File Attachments & Binary Data Transport
RecommendedAttach documents and assets using RFC 2183 Content-Disposition, RFC 2231 international filename encoding, Base64 transfer encoding, and 10MB size ceilings.