Cold Email Mailbox Setup Checklist After DNS: What to Do Next

Once SPF, DKIM, and DMARC are published and propagated, the checklist is: verify DNS with a live test email, create mailboxes with real-looking names and matching signatures, set up forwarding/profile photos, connect each mailbox to your sending tool, start warmup for 10-14 days before any cold volume, and cap daily sending volume per mailbox from day one.

Why isn't DNS enough on its own?

SPF, DKIM, and DMARC prove to receiving servers that your domain authorizes the mail you send. They say nothing about whether a mailbox is trustworthy, warmed up, or configured to behave like a real human inbox. Gmail and Outlook also weigh sending reputation, mailbox age, engagement patterns, and account-level signals that have nothing to do with DNS records. A domain can pass every authentication check and still land in spam if the mailbox behind it looks brand new and starts blasting 200 emails on day one.

Treat DNS as the foundation, not the finish line. The checklist below covers everything between "DNS is correct" and "mailbox is ready for cold outreach."

How do I confirm DNS actually propagated correctly?

Don't assume. Verify with a real test send before touching mailbox setup:

• Send a test email from the new mailbox to a mail-tester.com address or to a personal Gmail/Outlook account you control.
• Check the raw headers (in Gmail: "Show original") for SPF: PASS, DKIM: PASS, and DMARC: PASS on that specific message.
• Confirm DKIM is signing with the correct selector. A common failure is DNS showing a valid DKIM record while the mail server signs with a different or old selector, so the header check still fails.
• Re-check after 24-48 hours if you just published records; some registrars and resolvers cache longer than advertised TTLs.

Don't create mailboxes in bulk until at least one test mailbox on the domain passes all three checks cleanly.

What should the mailbox itself look like before sending anything?

This is the part most checklists skip, and it's where deliverability is actually won or lost at the mailbox level:

• Display name and email match a real person: "Sarah Chen" at [email protected], not "Sales Team" or "info@."
• Profile photo set: a real headshot, in both the mail client and any linked Gmail/Microsoft account. Blank avatars are a weak spam signal to filters and an obvious one to human recipients.
• Signature with real contact details: full name, title, company, and ideally a phone number or LinkedIn link. No signature or a signature that's just a link looks automated.
• Mailbox fully provisioned, not just "created": log in at least once, send and receive a manual email, and leave it idle for a day or two before connecting it to any tool. A mailbox that goes from zero to API-connected in minutes looks automated to mailbox providers.
• Inbox and sent folder not empty: a handful of real sent and received emails (replies to the test above, a calendar invite, anything) make the mailbox look used rather than freshly minted.
• Correct time zone and locale match where the "person" is supposed to be based.

If you're provisioning mailboxes through a platform, this is the stage where it matters whether the provider gives you actual Google Workspace or Microsoft 365 accounts you fully own and admin, versus shared or resold access you can't configure yourself. Inboxlogy, for example, provisions authorized Google Workspace and Microsoft 365 mailboxes with 100% ownership and admin access, dedicated US/EU IPs, and automated SPF/DKIM/DMARC, so this profile setup happens on infrastructure you actually control, not a black box.

Do I need a separate IP per mailbox or domain?

Not per mailbox, but IP reputation still matters, especially at scale. A few practical rules:

• Shared infrastructure with unknown neighbors is the biggest risk. If other domains on the same IP range get flagged, it can drag yours down.
• Dedicated IPs (as opposed to shared pools you don't control) give you a reputation that's entirely your own to build or damage.
• Geography matters loosely. US/EU-based IPs sending to US/EU recipients tend to behave more predictably than mismatched geography, though this is a minor signal compared to mailbox behavior.
• Don't over-engineer this at small volume. If you're running 5-10 mailboxes, a reputable provider's shared-but-isolated infrastructure is usually fine. It becomes worth insisting on dedicated IPs once you're running dozens of mailboxes across multiple domains.

When do I start warmup, and how long does it take?

Start warmup immediately after the mailbox passes DNS verification and has its profile fully set up. Plan for 10-14 days minimum before sending any real cold outreach, longer (2-3 weeks) for brand-new domains with no sending history at all.

A few things to know about how warmup actually works:

• Warmup runs inside your sending tool, not your infrastructure provider. Tools like Instantly, Smartlead, and ReachInbox have warmup built in. They send and receive emails between a network of mailboxes to build positive engagement signals (opens, replies, "move to inbox" actions) before you start cold sending. Your DNS and mailbox provider set up the foundation; the sending tool is what actually runs the warmup process.
• Don't skip warmup because DNS passed. Authentication and reputation are separate things. A perfectly authenticated mailbox with zero sending history still looks suspicious to Gmail/Outlook's reputation systems.
• Ramp gradually even after warmup: start cold sends at 10-20/day per mailbox in week one, not your eventual target volume.
• Keep warmup running continuously in the background even after you start cold sending. Most tools support this, and pausing it once live volume starts is a common mistake that lets reputation slide.

How many emails can one mailbox send per day once it's live?

As a general starting range for a warmed-up Google Workspace or Microsoft 365 mailbox: 20-30 emails/day in the first week of live sending, scaling to 40-50/day by week three or four if replies and bounce rates stay healthy. Don't exceed roughly 50/day per mailbox on standard Workspace/365 accounts regardless of how long they've been warmed. This is a platform-level sending limit and reputation ceiling, not just a best practice.

This is also why cold email programs run across many mailboxes rather than pushing volume through one or two: 10 mailboxes at 30/day sustainably outperforms 2 mailboxes pushed to 150/day, both in deliverability and in avoiding account suspensions.

What's the full sequence, start to finish?

• 1. Confirm SPF/DKIM/DMARC pass on a live test email, not just in a DNS checker.
• 2. Create the mailbox with a real name, matching domain, and correct locale/time zone.
• 3. Add a profile photo and a signature with real contact details.
• 4. Log in manually, send/receive a few real emails, let it sit idle 1-2 days.
• 5. Connect the mailbox to your sending tool (Instantly, Smartlead, ReachInbox, etc.) via API or IMAP/SMTP.
• 6. Start warmup inside the sending tool, minimum 10-14 days, longer for new domains.
• 7. Begin cold sending at low volume (10-20/day), scaling gradually while monitoring bounce and spam-complaint rates.
• 8. Keep warmup running continuously alongside live sending, and never exceed the mailbox's safe daily ceiling.

If you'd rather not manage mailbox provisioning, authentication, and ownership details yourself, this is the gap Inboxlogy is built for: authorized Google Workspace and Microsoft 365 mailboxes with automated SPF/DKIM/DMARC, dedicated US/EU IPs, full ownership and admin access, and an API to connect directly into whichever sending tool you run warmup and campaigns from, starting at $2.80/mailbox/month with no setup fee, billed monthly. The platform handles everything up to and including the connection into your sending tool; warmup itself always runs in that connected tool, not on Inboxlogy's side.

FAQ

Can I start cold sending immediately if DNS checks all pass?

No. Passing SPF/DKIM/DMARC confirms authentication, not sending reputation. A mailbox still needs profile setup and 10-14 days of warmup before it has enough positive sending history for inbox providers to trust high-volume outreach.

How many mailboxes do I need per domain?

Most cold email setups use 2-3 mailboxes per domain to keep volume distributed without overloading a single domain's reputation, and run multiple domains in parallel for real scale. Going much higher than 3-4 mailboxes on one domain concentrates risk if that domain gets flagged.

Does warmup happen automatically once DNS is set up?

No. Warmup isn't a DNS function at all. It runs inside your sending tool (Instantly, Smartlead, ReachInbox, etc.), which simulates real engagement across a mailbox network. DNS and mailbox setup just get the mailbox ready to be connected to that tool.

What's the most common mistake in this post-DNS stage?

Connecting a brand-new mailbox straight to a sending tool and starting cold outreach the same day DNS passes, skipping both the manual profile setup and the warmup period. This is the single biggest cause of new domains landing in spam within the first week.