email-infra-warmup-golivelisted

# Warmup & Go-Live · [Sales Ops → GTM] > **Reads:** `{SKILL_BASE}/resources/reference.md` §1, §2, §5 · gt-list-building (list verification) · **Runs:** `{SKILL_BASE}/playbooks/dns-auth-audit` · **Related:** domain-research, provisioning, campaign-building. > **Launch gate, first step.** Before anything else on this page, run the DNS audit across every > sending domain and require a clean exit: > ```bash > cd {SKILL_BASE}/playbooks/dns-auth-audit/scripts > uv run execute.py --file domains.txt --csv <client>_launch.csv # exit 0 = clear, 2 = blocked > ``` > All four auth records — MX, SPF, DKIM, DMARC — must be PASS. A WARN on any of them (a > `p=quarantine` DMARC, a missing DKIM key) blocks too. The exit code is designed as a gate, > so this can sit in front of go-live rather than beside it. Take provisioned domains (the provisioning sub-skill) from cold to live. Warm long enough, age before you link, and clear the gate before the first send. Numbers in `{SKILL_BASE}/resources/reference.md` §1, §5. --- ## Part 1, Warmup - **Minimum 21 days / 3 weeks** before any cold send (hard floor). **4 weeks on a cautious build.** - **Never disable warmup** once campaigns are running. - Warmup runs on every mailbox from day one of provisioning. **Warmup volume = cold limit × the warm-to-cold ratio** (`reference.md` §1): Google **1.5:1**, Outlook **3:1**. During the first 21 days cold is effectively 0–1, so warmup carries the load. > **Auto-warmup platforms.** Instantly and Smartle