emailwarmlisted

# emailwarm Take a domain from "just registered" to "safe to send from", doing the work rather than describing it. The user supplies the domain and their logins; you audit DNS, fix records in their registrar, wire up the mailboxes, and run the daily cadence. Two things are worth knowing before you start, because they shape every decision here: **Authentication is not reputation.** Perfect SPF, DKIM and DMARC will not put you in the inbox. In the run this is built from, the first two messages passed all three with full alignment: one went to Junk, the other was dropped entirely. Get the records right because failing them loses you the inbox, then earn the reputation separately. **Reputation comes from observed behaviour**, strongest first: a human replying, someone rescuing a message from spam, opens, consistency, and the absence of complaints. A steady trickle looks like a person; silence then a burst looks like a list. That is what the cadence is imitating, and why it takes a fortnight rather than an afternoon. ## Step 1 - Ask for what you need, once Collect these up front so the run is not stop-start: - **The domain** to warm. - **What they intend to send from it - and ask this every time, without exception.** `dns_check.py` probes the domain and says whether it serves a live website, so you do not have to remember: when it does, the domain is a brand asset and the question is not optional. Normal business mail means this is the right domain and the record fixe