Update to MisarMail

{
  "description": "Add and verify a custom sending domain in MisarMail, including SPF, DKIM, DMARC, and inbound routing. Use for \"send from my own domain\", DNS setup, domain verification, or inbound email.",
  "included_files": [],
  "name": "setup-sending-domain",
  "skill_md_contents": "---\nname: setup-sending-domain\ndescription: Add and verify a custom sending domain in MisarMail, including SPF, DKIM, DMARC, and inbound routing. Use for \"send from my own domain\", DNS setup, domain verification, or inbound email.\n---\n\n# Set up a sending domain\n\n## 1. Add it\n\n`add_domain` returns the DNS records to publish. Give the user the exact record\ntype, host, and value — a paraphrase produces a broken record.\n\n## 2. Wait, then verify\n\n`verify_domain` re-checks DNS. Propagation takes minutes to 48 hours, so a\nfailure right after publishing is expected rather than an error. Say that\ninstead of letting the user think something is wrong.\n\n`check_dmarc` shows what is actually resolving publicly, which is the fastest\nway to spot a record pasted into the wrong host (a very common mistake:\n`_dmarc.example.com` published as `_dmarc.example.com.example.com`).\n\n## 3. Warm up before volume\n\n`get_warmup_status` — a new domain has no reputation. Ramping gradually is what\nseparates a domain that lands in the inbox from one that lands in spam\npermanently. Do not let a user send a large first campaign from a brand-new\ndomain without flagging the risk.\n\n## DMARC policy\n\nStart at `p=none` (monitor only), then move to `quarantine` and finally\n`reject` once `check_dmarc` shows SPF and DKIM aligned and passing. Jumping\nstraight to `p=reject` before alignment is confirmed silently blackholes\nlegitimate mail.\n\n## Inbound\n\n`configure_inbound_domain` routes replies into the unified inbox and returns\nthe MX record to publish. Use a subdomain (`reply.example.com`) so it cannot\ninterfere with the organisation's primary mail.\n"
}