{
  "@context": "https://schema.org",
  "@graph": [
    {
      "@type": "TechArticle",
      "@id": "https://specification.email/spec/accessibility/color-and-contrast/#article",
      "url": "https://specification.email/spec/accessibility/color-and-contrast/",
      "headline": "Email color contrast and cues",
      "description": "Text, controls, and meaningful graphics need sufficient contrast, and color must never be the only way the message communicates state.",
      "articleSection": "accessibility",
      "keywords": [
        "required",
        "accessibility",
        "email"
      ],
      "citation": [
        "https://www.w3.org/WAI/WCAG22/Understanding/contrast-minimum.html",
        "https://www.w3.org/WAI/WCAG22/Understanding/use-of-color.html"
      ],
      "isPartOf": {
        "@id": "https://specification.email/#website"
      }
    },
    {
      "@type": "TechArticle",
      "@id": "https://specification.email/spec/accessibility/image-alt-text/#article",
      "url": "https://specification.email/spec/accessibility/image-alt-text/",
      "headline": "Alternative text for email images",
      "description": "Every informative image needs concise equivalent alt text, while decorative images need an empty alt attribute and no repeated meaning.",
      "articleSection": "accessibility",
      "keywords": [
        "required",
        "accessibility",
        "email"
      ],
      "citation": [
        "https://www.w3.org/WAI/WCAG22/Understanding/non-text-content.html"
      ],
      "isPartOf": {
        "@id": "https://specification.email/#website"
      }
    },
    {
      "@type": "TechArticle",
      "@id": "https://specification.email/spec/accessibility/semantic-structure/#article",
      "url": "https://specification.email/spec/accessibility/semantic-structure/",
      "headline": "Semantic email structure",
      "description": "Use headings, paragraphs, lists, tables, and landmarks according to meaning so assistive technology can navigate the message.",
      "articleSection": "accessibility",
      "keywords": [
        "required",
        "accessibility",
        "email"
      ],
      "citation": [
        "https://www.w3.org/WAI/WCAG22/Understanding/info-and-relationships.html"
      ],
      "isPartOf": {
        "@id": "https://specification.email/#website"
      }
    },
    {
      "@type": "TechArticle",
      "@id": "https://specification.email/spec/authentication/dane-for-smtp/#article",
      "url": "https://specification.email/spec/authentication/dane-for-smtp/",
      "headline": "DANE for SMTP",
      "description": "Publish DNSSEC-signed TLSA records for your MX hosts so sending servers can verify their certificates without trusting the CA system alone.",
      "articleSection": "authentication",
      "keywords": [
        "recommended",
        "authentication",
        "email"
      ],
      "citation": [
        "https://www.rfc-editor.org/rfc/rfc7672",
        "https://www.rfc-editor.org/rfc/rfc6698",
        "https://www.rfc-editor.org/rfc/rfc7671"
      ],
      "isPartOf": {
        "@id": "https://specification.email/#website"
      }
    },
    {
      "@type": "TechArticle",
      "@id": "https://specification.email/spec/authentication/dkim-signatures/#article",
      "url": "https://specification.email/spec/authentication/dkim-signatures/",
      "headline": "DomainKeys Identified Mail signatures",
      "description": "Sign outgoing mail with DKIM using aligned domains, protected private keys, rotating selectors, and canonicalization that survives normal transit.",
      "articleSection": "authentication",
      "keywords": [
        "required",
        "authentication",
        "email"
      ],
      "citation": [
        "https://www.rfc-editor.org/rfc/rfc6376"
      ],
      "isPartOf": {
        "@id": "https://specification.email/#website"
      }
    },
    {
      "@type": "TechArticle",
      "@id": "https://specification.email/spec/authentication/dmarc-policy/#article",
      "url": "https://specification.email/spec/authentication/dmarc-policy/",
      "headline": "DMARC alignment and policy",
      "description": "Publish DMARC, collect reports, align SPF or DKIM with the visible From domain, and move to enforcement only after legitimate flows pass.",
      "articleSection": "authentication",
      "keywords": [
        "required",
        "authentication",
        "email"
      ],
      "citation": [
        "https://www.rfc-editor.org/rfc/rfc7489"
      ],
      "isPartOf": {
        "@id": "https://specification.email/#website"
      }
    },
    {
      "@type": "TechArticle",
      "@id": "https://specification.email/spec/authentication/mta-sts/#article",
      "url": "https://specification.email/spec/authentication/mta-sts/",
      "headline": "SMTP MTA Strict Transport Security (MTA-STS)",
      "description": "Publish an MTA-STS policy so sending servers require valid TLS to your MX hosts instead of silently falling back to plaintext.",
      "articleSection": "authentication",
      "keywords": [
        "recommended",
        "authentication",
        "email"
      ],
      "citation": [
        "https://www.rfc-editor.org/rfc/rfc8461",
        "https://www.rfc-editor.org/rfc/rfc3207"
      ],
      "isPartOf": {
        "@id": "https://specification.email/#website"
      }
    },
    {
      "@type": "TechArticle",
      "@id": "https://specification.email/spec/authentication/sender-policy-framework/#article",
      "url": "https://specification.email/spec/authentication/sender-policy-framework/",
      "headline": "Sender Policy Framework (SPF)",
      "description": "Publish one bounded SPF policy that authorizes legitimate envelope senders without exceeding DNS lookup limits or permitting the world.",
      "articleSection": "authentication",
      "keywords": [
        "required",
        "authentication",
        "email"
      ],
      "citation": [
        "https://www.rfc-editor.org/rfc/rfc7208"
      ],
      "isPartOf": {
        "@id": "https://specification.email/#website"
      }
    },
    {
      "@type": "TechArticle",
      "@id": "https://specification.email/spec/authentication/starttls/#article",
      "url": "https://specification.email/spec/authentication/starttls/",
      "headline": "STARTTLS on MX hosts",
      "description": "Offer STARTTLS on every MX host with a certificate that matches its hostname and a current TLS configuration, so incoming mail can be encrypted.",
      "articleSection": "authentication",
      "keywords": [
        "required",
        "authentication",
        "email"
      ],
      "citation": [
        "https://www.rfc-editor.org/rfc/rfc3207",
        "https://www.rfc-editor.org/rfc/rfc8996",
        "https://www.rfc-editor.org/rfc/rfc9325",
        "https://www.rfc-editor.org/rfc/rfc8659"
      ],
      "isPartOf": {
        "@id": "https://specification.email/#website"
      }
    },
    {
      "@type": "TechArticle",
      "@id": "https://specification.email/spec/authentication/tls-reporting/#article",
      "url": "https://specification.email/spec/authentication/tls-reporting/",
      "headline": "SMTP TLS Reporting (TLS-RPT)",
      "description": "Publish a TLS-RPT record so sending servers report failed TLS connections to your mail servers, and read the reports.",
      "articleSection": "authentication",
      "keywords": [
        "recommended",
        "authentication",
        "email"
      ],
      "citation": [
        "https://www.rfc-editor.org/rfc/rfc8460"
      ],
      "isPartOf": {
        "@id": "https://specification.email/#website"
      }
    },
    {
      "@type": "TechArticle",
      "@id": "https://specification.email/spec/automation/attachments/#article",
      "url": "https://specification.email/spec/automation/attachments/",
      "headline": "Safe and usable email attachments",
      "description": "Attach only necessary files with accurate media types, safe names, bounded size, malware controls, and an accessible alternative where possible.",
      "articleSection": "automation",
      "keywords": [
        "recommended",
        "automation",
        "email"
      ],
      "citation": [
        "https://www.rfc-editor.org/rfc/rfc2183",
        "https://www.rfc-editor.org/rfc/rfc2231"
      ],
      "isPartOf": {
        "@id": "https://specification.email/#website"
      }
    },
    {
      "@type": "TechArticle",
      "@id": "https://specification.email/spec/automation/calendar-invitations/#article",
      "url": "https://specification.email/spec/automation/calendar-invitations/",
      "headline": "Calendar invitation interoperability",
      "description": "Calendar mail must include valid iCalendar data, stable event identifiers, correct methods, time zones, and updates that replace prior versions.",
      "articleSection": "automation",
      "keywords": [
        "recommended",
        "automation",
        "email"
      ],
      "citation": [
        "https://www.rfc-editor.org/rfc/rfc5545",
        "https://www.rfc-editor.org/rfc/rfc5546"
      ],
      "isPartOf": {
        "@id": "https://specification.email/#website"
      }
    },
    {
      "@type": "TechArticle",
      "@id": "https://specification.email/spec/automation/machine-readable-actions/#article",
      "url": "https://specification.email/spec/automation/machine-readable-actions/",
      "headline": "Machine-readable email actions",
      "description": "Add structured actions only as progressive enhancement, bind them to visible content, and keep the ordinary website workflow complete.",
      "articleSection": "automation",
      "keywords": [
        "optional",
        "automation",
        "email"
      ],
      "citation": [
        "https://schema.org/EmailMessage",
        "https://developers.google.com/gmail/markup/overview"
      ],
      "isPartOf": {
        "@id": "https://specification.email/#website"
      }
    },
    {
      "@type": "TechArticle",
      "@id": "https://specification.email/spec/deliverability/complaint-handling/#article",
      "url": "https://specification.email/spec/deliverability/complaint-handling/",
      "headline": "Spam complaint handling",
      "description": "Subscribe to available feedback loops, connect complaints to recipients safely, suppress them promptly, and monitor complaint rates by message stream.",
      "articleSection": "deliverability",
      "keywords": [
        "required",
        "deliverability",
        "email"
      ],
      "citation": [
        "https://www.rfc-editor.org/rfc/rfc6449"
      ],
      "isPartOf": {
        "@id": "https://specification.email/#website"
      }
    },
    {
      "@type": "TechArticle",
      "@id": "https://specification.email/spec/deliverability/list-hygiene/#article",
      "url": "https://specification.email/spec/deliverability/list-hygiene/",
      "headline": "Recipient list hygiene",
      "description": "Send only to expected recipients, remove permanent failures, suppress complainers, and stop mailing addresses that never engage or consent.",
      "articleSection": "deliverability",
      "keywords": [
        "required",
        "deliverability",
        "email"
      ],
      "citation": [
        "https://support.google.com/a/answer/81126"
      ],
      "isPartOf": {
        "@id": "https://specification.email/#website"
      }
    },
    {
      "@type": "TechArticle",
      "@id": "https://specification.email/spec/deliverability/reverse-dns/#article",
      "url": "https://specification.email/spec/deliverability/reverse-dns/",
      "headline": "Reverse DNS and sending identity",
      "description": "Every sending IP needs stable forward-confirmed reverse DNS, an SMTP greeting that matches it, and an operational domain identity.",
      "articleSection": "deliverability",
      "keywords": [
        "required",
        "deliverability",
        "email"
      ],
      "citation": [
        "https://www.rfc-editor.org/rfc/rfc5321#section-4.1.4",
        "https://support.google.com/a/answer/81126",
        "https://www.rfc-editor.org/rfc/rfc3596"
      ],
      "isPartOf": {
        "@id": "https://specification.email/#website"
      }
    },
    {
      "@type": "TechArticle",
      "@id": "https://specification.email/spec/foundations/header-fields/#article",
      "url": "https://specification.email/spec/foundations/header-fields/",
      "headline": "Required message header fields",
      "description": "Each message needs a valid Date, From, and globally unique Message-ID, with recipient and subject fields that match its purpose.",
      "articleSection": "foundations",
      "keywords": [
        "required",
        "foundations",
        "email"
      ],
      "citation": [
        "https://www.rfc-editor.org/rfc/rfc5322#section-3.6"
      ],
      "isPartOf": {
        "@id": "https://specification.email/#website"
      }
    },
    {
      "@type": "TechArticle",
      "@id": "https://specification.email/spec/foundations/message-format/#article",
      "url": "https://specification.email/spec/foundations/message-format/",
      "headline": "Internet message format",
      "description": "Every message must use the standard header and body structure, valid line endings, and legal field syntax before it enters SMTP.",
      "articleSection": "foundations",
      "keywords": [
        "required",
        "foundations",
        "email"
      ],
      "citation": [
        "https://www.rfc-editor.org/rfc/rfc5322"
      ],
      "isPartOf": {
        "@id": "https://specification.email/#website"
      }
    },
    {
      "@type": "TechArticle",
      "@id": "https://specification.email/spec/foundations/mime-multipart/#article",
      "url": "https://specification.email/spec/foundations/mime-multipart/",
      "headline": "MIME multipart structure",
      "description": "Use valid MIME types, boundaries, transfer encodings, and multipart nesting so every client can select a safe representation.",
      "articleSection": "foundations",
      "keywords": [
        "required",
        "foundations",
        "email"
      ],
      "citation": [
        "https://www.rfc-editor.org/rfc/rfc2045",
        "https://www.rfc-editor.org/rfc/rfc2046"
      ],
      "isPartOf": {
        "@id": "https://specification.email/#website"
      }
    },
    {
      "@type": "TechArticle",
      "@id": "https://specification.email/spec/internationalisation/international-addresses/#article",
      "url": "https://specification.email/spec/internationalisation/international-addresses/",
      "headline": "Internationalized email addresses",
      "description": "Accept and preserve Unicode mailbox addresses only when every validation, storage, SMTP, and support path handles SMTPUTF8 safely.",
      "articleSection": "internationalisation",
      "keywords": [
        "recommended",
        "internationalisation",
        "email"
      ],
      "citation": [
        "https://www.rfc-editor.org/rfc/rfc6531"
      ],
      "isPartOf": {
        "@id": "https://specification.email/#website"
      }
    },
    {
      "@type": "TechArticle",
      "@id": "https://specification.email/spec/internationalisation/language-direction/#article",
      "url": "https://specification.email/spec/internationalisation/language-direction/",
      "headline": "Message language and text direction",
      "description": "Declare the message language and mark bidirectional runs so pronunciation, punctuation, numerals, and reading order remain correct.",
      "articleSection": "internationalisation",
      "keywords": [
        "required",
        "internationalisation",
        "email"
      ],
      "citation": [
        "https://www.w3.org/WAI/WCAG22/Understanding/language-of-page.html",
        "https://www.w3.org/International/questions/qa-html-dir"
      ],
      "isPartOf": {
        "@id": "https://specification.email/#website"
      }
    },
    {
      "@type": "TechArticle",
      "@id": "https://specification.email/spec/internationalisation/utf-8-content/#article",
      "url": "https://specification.email/spec/internationalisation/utf-8-content/",
      "headline": "UTF-8 message content",
      "description": "Encode international text consistently as UTF-8 across headers and bodies, with MIME declarations and transfer encodings that preserve every character.",
      "articleSection": "internationalisation",
      "keywords": [
        "required",
        "internationalisation",
        "email"
      ],
      "citation": [
        "https://www.rfc-editor.org/rfc/rfc6532"
      ],
      "isPartOf": {
        "@id": "https://specification.email/#website"
      }
    },
    {
      "@type": "TechArticle",
      "@id": "https://specification.email/spec/lifecycle/bounce-handling/#article",
      "url": "https://specification.email/spec/lifecycle/bounce-handling/",
      "headline": "Delivery status and bounce handling",
      "description": "Classify SMTP and delivery-status failures, stop permanent retries, back off temporary failures, and connect outcomes to the correct recipient.",
      "articleSection": "lifecycle",
      "keywords": [
        "required",
        "lifecycle",
        "email"
      ],
      "citation": [
        "https://www.rfc-editor.org/rfc/rfc3463",
        "https://www.rfc-editor.org/rfc/rfc3464"
      ],
      "isPartOf": {
        "@id": "https://specification.email/#website"
      }
    },
    {
      "@type": "TechArticle",
      "@id": "https://specification.email/spec/lifecycle/one-click-unsubscribe/#article",
      "url": "https://specification.email/spec/lifecycle/one-click-unsubscribe/",
      "headline": "One-click list unsubscribe",
      "description": "Bulk subscription mail needs authenticated one-click unsubscribe headers that complete without login, redirects, confirmation pages, or extra choices.",
      "articleSection": "lifecycle",
      "keywords": [
        "required",
        "lifecycle",
        "email"
      ],
      "citation": [
        "https://www.rfc-editor.org/rfc/rfc8058"
      ],
      "isPartOf": {
        "@id": "https://specification.email/#website"
      }
    },
    {
      "@type": "TechArticle",
      "@id": "https://specification.email/spec/lifecycle/retry-expiry/#article",
      "url": "https://specification.email/spec/lifecycle/retry-expiry/",
      "headline": "Retry strategy and message expiry",
      "description": "Retry transient SMTP failures with backoff, cap queue lifetime, and expire time-sensitive messages before delayed delivery becomes harmful.",
      "articleSection": "lifecycle",
      "keywords": [
        "required",
        "lifecycle",
        "email"
      ],
      "citation": [
        "https://www.rfc-editor.org/rfc/rfc5321#section-4.5.4.1"
      ],
      "isPartOf": {
        "@id": "https://specification.email/#website"
      }
    },
    {
      "@type": "TechArticle",
      "@id": "https://specification.email/spec/privacy/consent-provenance/#article",
      "url": "https://specification.email/spec/privacy/consent-provenance/",
      "headline": "Consent and subscription provenance",
      "description": "Keep verifiable evidence of how and when each recipient subscribed, what they expected, and which message purposes that choice covered.",
      "articleSection": "privacy",
      "keywords": [
        "required",
        "privacy",
        "email"
      ],
      "citation": [
        "https://eur-lex.europa.eu/eli/reg/2016/679/art_7/oj"
      ],
      "isPartOf": {
        "@id": "https://specification.email/#website"
      }
    },
    {
      "@type": "TechArticle",
      "@id": "https://specification.email/spec/privacy/data-minimisation/#article",
      "url": "https://specification.email/spec/privacy/data-minimisation/",
      "headline": "Recipient data minimisation",
      "description": "Put only necessary personal data in message bodies, headers, links, logs, and provider metadata, with explicit retention for each copy.",
      "articleSection": "privacy",
      "keywords": [
        "required",
        "privacy",
        "email"
      ],
      "citation": [
        "https://eur-lex.europa.eu/eli/reg/2016/679/art_5/oj"
      ],
      "isPartOf": {
        "@id": "https://specification.email/#website"
      }
    },
    {
      "@type": "TechArticle",
      "@id": "https://specification.email/spec/privacy/tracking-pixels/#article",
      "url": "https://specification.email/spec/privacy/tracking-pixels/",
      "headline": "Tracking pixels and remote images",
      "description": "Treat open tracking as unreliable personal data collection, disclose it, minimise retention, and never make essential behavior depend on it.",
      "articleSection": "privacy",
      "keywords": [
        "recommended",
        "privacy",
        "email"
      ],
      "citation": [
        "https://ico.org.uk/for-organisations/uk-gdpr-guidance-and-resources/lawful-basis/legitimate-interests/"
      ],
      "isPartOf": {
        "@id": "https://specification.email/#website"
      }
    },
    {
      "@type": "TechArticle",
      "@id": "https://specification.email/spec/rendering/inline-css/#article",
      "url": "https://specification.email/spec/rendering/inline-css/",
      "headline": "Inline CSS and safe fallbacks",
      "description": "Inline critical presentation, keep selectors simple, and design fallbacks for clients that remove style blocks or ignore unsupported properties.",
      "articleSection": "rendering",
      "keywords": [
        "recommended",
        "rendering",
        "email"
      ],
      "citation": [
        "https://www.caniemail.com/features/"
      ],
      "isPartOf": {
        "@id": "https://specification.email/#website"
      }
    },
    {
      "@type": "TechArticle",
      "@id": "https://specification.email/spec/rendering/responsive-layout/#article",
      "url": "https://specification.email/spec/rendering/responsive-layout/",
      "headline": "Responsive email layout",
      "description": "Messages must fit narrow screens, preserve readable type, and keep controls usable even when media queries or viewport hints are ignored.",
      "articleSection": "rendering",
      "keywords": [
        "required",
        "rendering",
        "email"
      ],
      "citation": [
        "https://www.w3.org/WAI/WCAG22/Understanding/reflow.html"
      ],
      "isPartOf": {
        "@id": "https://specification.email/#website"
      }
    },
    {
      "@type": "TechArticle",
      "@id": "https://specification.email/spec/rendering/table-layout/#article",
      "url": "https://specification.email/spec/rendering/table-layout/",
      "headline": "Robust email layout tables",
      "description": "Use a simple presentation-table scaffold where client support requires it, without leaking table semantics into the reading experience.",
      "articleSection": "rendering",
      "keywords": [
        "recommended",
        "rendering",
        "email"
      ],
      "citation": [
        "https://www.caniemail.com/features/html-table/"
      ],
      "isPartOf": {
        "@id": "https://specification.email/#website"
      }
    },
    {
      "@type": "TechArticle",
      "@id": "https://specification.email/spec/security/dangerous-content/#article",
      "url": "https://specification.email/spec/security/dangerous-content/",
      "headline": "Dangerous active email content",
      "description": "Do not depend on scripts, forms, embedded credentials, or untrusted active content; sanitise generated HTML and provide safe web fallbacks.",
      "articleSection": "security",
      "keywords": [
        "avoid",
        "security",
        "email"
      ],
      "citation": [
        "https://html.spec.whatwg.org/multipage/scripting.html#the-script-element"
      ],
      "isPartOf": {
        "@id": "https://specification.email/#website"
      }
    },
    {
      "@type": "TechArticle",
      "@id": "https://specification.email/spec/security/header-injection/#article",
      "url": "https://specification.email/spec/security/header-injection/",
      "headline": "Email header injection prevention",
      "description": "Treat every header value as structured data, reject line breaks from untrusted input, and let a mail library serialize addresses and fields.",
      "articleSection": "security",
      "keywords": [
        "required",
        "security",
        "email"
      ],
      "citation": [
        "https://cwe.mitre.org/data/definitions/93.html"
      ],
      "isPartOf": {
        "@id": "https://specification.email/#website"
      }
    },
    {
      "@type": "TechArticle",
      "@id": "https://specification.email/spec/security/safe-links/#article",
      "url": "https://specification.email/spec/security/safe-links/",
      "headline": "Safe and trustworthy email links",
      "description": "Link text, visible domains, redirects, and destination context must agree, while sensitive actions require fresh server-side authorization.",
      "articleSection": "security",
      "keywords": [
        "required",
        "security",
        "email"
      ],
      "citation": [
        "https://pages.nist.gov/800-63-4/sp800-63b.html"
      ],
      "isPartOf": {
        "@id": "https://specification.email/#website"
      }
    }
  ]
}