← RetenoCONTENT HISTORY

Update to Reteno

Snapshot Nov 18, 2026 · 06:17 UTC · version 0.4.1

Collection source: downloaded plugin package.

WHAT CHANGED

First saved snapshot

No earlier snapshot is available to establish a change.

Save Reteno and check future changes in Following.

Up to 3 plugins free · no card required.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "description": "Audit Reteno email deliverability technical setup using live MCP configuration, public DNS and TLS. Use for SPF, DKIM/CNAME, DMARC, sender and Reply-To domains, required custom link domains or setup audits. Reports unavailable evidence separately from confirmed failures and applies the current Reteno customer checklist.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 245
    },
    {
      "relative_path": "references/checklist-evidence.md",
      "size_in_bytes": 1744
    },
    {
      "relative_path": "scripts/audit_engine.py",
      "size_in_bytes": 55010
    },
    {
      "relative_path": "scripts/audit_technical_setup.py",
      "size_in_bytes": 5391
    },
    {
      "relative_path": "scripts/checklist.py",
      "size_in_bytes": 8823
    },
    {
      "relative_path": "scripts/spf_policy.py",
      "size_in_bytes": 8888
    }
  ],
  "name": "email-deliverability",
  "skill_md_contents": "---\nname: email-deliverability\ndescription: Audit Reteno email deliverability technical setup using live MCP configuration, public DNS and TLS. Use for SPF, DKIM/CNAME, DMARC, sender and Reply-To domains, required custom link domains or setup audits. Reports unavailable evidence separately from confirmed failures and applies the current Reteno customer checklist.\n---\n\n# Email deliverability\n\nThis is read-only. Call `get_email_deliverability_setup` for the selected account and save the\nfresh response locally. Resolve `<skill-dir>` from the installed plugin, not the working directory.\nThe helper uses Python 3.11+ and `dnspython` from the plugin's pinned requirements.\n\n```sh\npython3 <skill-dir>/scripts/audit_technical_setup.py --input <setup.json> \\\n  --organization-id <authenticated-org-id> --output-dir output/email-deliverability\n```\n\nRead the JSON and Markdown results before answering. Lead with confirmed failures, followed\nby unavailable evidence and its practical effect. Never describe an incomplete audit as passed.\nDNS timeout, SERVFAIL, DNSSEC/network or query-budget failures are unavailable evidence.\nOnly confirmed absence/mismatch against an applicable requirement is a failure.\n\nThe October 6 checklist requires an effective DMARC `quarantine`/`reject` policy; `p=none` and\n`t=y` do not satisfy enforcement. SPF must be evaluated at the exact envelope/Return-Path domain\nwith actual Reteno sending IPs, including mechanism order, qualifiers, includes, redirects and\nlookup limits. It does not inherit from the From domain or a parent. Preserve other authorized\nsenders; `~all` and `-all` are both allowed. Do not recommend flattening solely from a theoretical\nmaximum lookup count. The bounded evaluator reports unsupported macro/PTR evidence as unavailable.\n\nDKIM follows CNAMEs and uses the Reteno `esputnik` selector as discovery fallback. Missing\nfallback evidence alone does not fail the customer. Validate active/in-flight selectors against\naccount-specific expected names, record types and keys/targets; retired selectors are excluded.\nA customer-controlled custom link domain is mandatory for every Reteno organization. Confirm\nits selection, activation, CNAME target and TLS, including retained domains still used in old emails.\n`shortLinks.settings.enabled` controls UTM tagging; `destinationDomains` are redirect destinations,\nnot expected DNS CNAME targets. `oneClickUnsubscribe.enabled` (configuration 371) does not prove\nunsubscribe headers; do not generate a header finding from it. BIMI/MTA-STS/TLS-RPT are optional.\n\nIf MCP exposes insufficient account reference details, report unavailable evidence and explain\nwhat is missing. Where those details are supplied by live settings or the user, prepare the\n[reference evidence file](references/checklist-evidence.md) and pass `--references <file>`.\nDo not guess an envelope hostname, sending IP, DKIM key, custom link CNAME or technical MX target.\nTechnical MX documentation disagreements are not customer failures. Never refresh verification,\nchange DNS/configuration or send test mail as part of an audit.\n"
}

SHA-256 of public snapshot: 284bc90b91954ca33dba9d7079e384a55c15e978d16c0ea6f915205f2a0029ab