Cold Emailing
CEO and co-founder
Email infrastructure glossary: SPF, DKIM, DMARC, warmup & deliverability terms
TL;DR: Manual DNS configuration and per-inbox pricing are the two costs quietly compressing agency margins. SPF, DKIM, and DMARC play a critical role in whether your campaigns reach the inbox. Dedicated IPs isolate your sender reputation from other senders' behavior. And per-inbox pricing costs $350/month for 50 inboxes on Google Workspace versus flat-rate alternatives. This glossary defines every term you need to evaluate vendors, protect your margins, and keep campaigns out of spam.
Deliverability is not magic. It is a strict mathematical output of your DNS records, IP reputation, and warmup strategy. For 200 inboxes, Google Workspace Business Starter costs $1,400 per month at $7.00 per seat. Flat-rate infrastructure costs $129/month for 50 inboxes. On Google Workspace, that same count costs $350-420/month. The gap is your profit margin.
When client campaigns scale, manual DNS setup and per-inbox pricing become growth bottlenecks. What most agency founders lack is the vocabulary to evaluate alternative vendors, spot deliverability risks before they become client fires, and buy infrastructure that protects net margins at scale. This glossary defines the exact technical terms, deliverability metrics, and cost variables you need.
Outbound email infrastructure setup
Building a functional outbound email system starts with understanding the components involved and how they connect. The sections below cover the core building blocks, the financial terms that affect your margins, and the cost breakdown across inbox tiers.
Core components of email infrastructure
Cold email infrastructure is the combination of domains, inboxes, IP addresses, DNS records, and sending protocols that determines whether your outbound email reaches a prospect's inbox or gets blocked entirely. The core technical components you'll encounter include:
Mailbox (inbox): A single email account tied to a domain, used to send outbound campaigns. Industry practitioners commonly recommend daily sending limits of 30-50 cold emails per inbox to avoid triggering spam filters.
SMTP (Simple Mail Transfer Protocol): The protocol used for sending outgoing email. Every platform like Instantly or Smartlead uses SMTP credentials (server address, port, username, password) to route your campaigns.
IMAP (Internet Message Access Protocol): The protocol commonly used for receiving and syncing email across devices. IMAP credentials let cold email platforms pull replies back into your campaign dashboard.
Email verification: The process of checking whether an email address is valid before sending to it. Tools like ZeroBounce and NeverBounce help identify invalid addresses that can cause hard bounces and impact sender reputation.
Watch this Inframail setup tutorial for a walkthrough of how each component connects in a real cold email infrastructure stack.
Deliverability's impact on agency margins
Understanding infrastructure costs means understanding your full P&L (profit and loss statement), the document that tracks total revenue minus all costs to show your net profit. Key financial terms to track:
Gross margin: Revenue minus direct costs (infrastructure, domains, tools).
Net profit margin: What remains after all costs including labor, software, and infrastructure. High infrastructure costs relative to billings compress this significantly.
Unit economics: The revenue and cost structure tied to a single client. For example, if one client generates $3,000/month and their infrastructure costs $600/month, that's 20% consumed before counting any labor.
CAC (Customer Acquisition Cost): The total cost to win one new client. When infrastructure setup takes hours per onboarding, you spend labor budget before the client pays their first invoice.
Client LTV (Lifetime Value): Average monthly retainer multiplied by average client tenure in months.
The TCO (Total Cost of Ownership) table below breaks down exactly how infrastructure costs scale across three inbox tiers. Domain costs reflect industry-standard pricing of $5-16/year per domain, amortized monthly, and vary with your domain-to-inbox ratio.
Cost component | 50 inboxes | 100 inboxes | 200 inboxes |
|---|---|---|---|
Inframail flat rate | $129/mo | $129/mo | $129/mo |
Domains (amortized) | ~$18-35/mo | ~$25-45/mo | ~$35-65/mo |
Inframail total (estimated) | ~$147-164/mo | ~$154-174/mo | ~$164-194/mo |
Google Workspace ($7.00/seat) | $350/mo | $700/mo | $1,400/mo |
Google Workspace total (estimated) | ~$368-385/mo | ~$725-745/mo | ~$1,435-1,465/mo |
Estimated monthly savings | ~$204-238/mo | ~$551-591/mo | ~$1,241-1,301/mo |
Annual savings with Inframail | ~$2,448-2,856/yr | ~$6,612-7,092/yr | ~$14,892-15,612/yr |
Warmup tools ($15-50/month per inbox) and sending platforms ($37-147/month) apply equally to both infrastructure options and are excluded from the savings calculation.
Inframail's DFY Email Campaign Setup at $499/month includes email account warmup for teams that want it bundled.
Mastering SPF, DKIM, DMARC protocols
Each authentication protocol plays a distinct role in how receiving mail servers evaluate your email. The subsections below cover how SPF, DKIM, and DMARC work individually, how DNS records support them, and what each one controls in the verification process.
Configuring SPF for high inbox
SPF (Sender Policy Framework) is an email authentication method stored as a DNS TXT record that lists every IP address authorized to send email on behalf of your domain. Receiving mail servers check every inbound email's sending IP against your domain's SPF record. If the IP is not on the list, the email fails SPF and gets flagged or rejected.
Think of an SPF record like a door attendant's guest list: if the sending IP is not on it, the server will not let it through. A typical Microsoft-hosted SPF record looks like: v=spf1 include:spf.protection.outlook.com ~all.
The DNS setup bottleneck occurs when agencies manually log into registrars like Namecheap or GoDaddy to create this record for each domain, wait for propagation, test it, and repeat for every client. Inframail's platform configures SPF automatically, with no DNS panel access required.
DKIM setup for high deliverability
DKIM (DomainKeys Identified Mail) is an email authentication method that attaches a cryptographic digital signature to every outgoing email. Receiving servers use a public key stored in your domain's DNS to verify the signature and confirm the message was not altered in transit.
Think of DKIM like a tamper-proof seal on medicine: if email headers or body were changed after sending, the signature fails verification. This signals to ESPs (Email Service Providers) that your domain is legitimate and that the message content arrived intact.
Watch this video on setting up SPF, DKIM, and DMARC in under 2 minutes using Inframail's automated setup.
DMARC: reduce spoofing & phishing risk
DMARC (Domain-based Message Authentication, Reporting and Conformance) is the policy layer that sits on top of SPF and DKIM. It tells receiving mail servers how to handle emails that fail authentication, and where to send aggregate reports so you can monitor your domain's reputation.
DMARC policy options include:
p=none (monitor): According to DMARC standards, failed emails typically still reach the inbox while you collect reports without blocking anything. Use this initially to audit your authentication setup.
p=quarantine: Failed emails are typically routed to spam or junk folders. Stronger protection against spoofing attempts.
p=reject: Failed emails are typically blocked entirely. Maximum protection, used once authentication is fully confirmed.
Email spoofing occurs when someone sends email that appears to come from your domain without authorization. DMARC provides instructions to receiving servers on how to handle emails that fail SPF and DKIM checks, which helps reduce the impact of spoofing attempts on your domain reputation and your clients' brands.
DNS records for inbox placement
DNS (Domain Name System) records are the publicly accessible database entries that control how email and web traffic routes to and from your domain. For email infrastructure, the critical record types include TXT (storing SPF and DMARC policies), CNAME (publishing DKIM public keys), and MX (directing inbound email to the correct mail server).
DNS panels are the management interfaces (Namecheap, GoDaddy, Cloudflare) where you manually create these records. When not automated, each record requires logging in, entering exact values, saving, and waiting for propagation before testing. Our automated DNS configuration handles critical record types automatically, so you never touch a DNS panel for cold email infrastructure setup.
Dedicated vs. shared IP explained
IP architecture is one of the more consequential infrastructure decisions you will make when setting up outbound email. The subsections below cover how each model works, the trade-offs involved, and how warmup and sender reputation fit into the broader picture.
Dedicated IP: cost, control, & reputation
A dedicated IP is an IP address assigned exclusively to your sending account. No other sender shares it. Your sending behavior determines the IP's reputation history with mail providers like Google and Microsoft, and a blacklist event caused by another sender cannot affect your campaigns.
Watch our dedicated vs. shared IP breakdown for a full comparison of how each architecture affects cold email deliverability. Inframail's Unlimited Plan ($129/month) includes 1 dedicated US-based IP and the Agency Pack ($327/month) includes 3 dedicated US-based IPs. This architecture means a deliverability issue on one client's campaign is isolated from other clients' IP reputation.
The trade-off: a fresh dedicated IP typically starts with no reputation history and requires a warmup period before sending at full volume.
Risks of shared IP pools
A shared IP pool is a range of IP addresses used simultaneously by multiple senders across a platform. Several cold email infrastructure providers use shared pools rather than dedicated IPs.
The core risk: since the IP is shared, the sending reputation is also shared. Your deliverability rate can be affected by everyone else sending from that IP, not just your behavior. One bad actor generating high complaint rates from the same pool can potentially flag the entire IP range, affecting deliverability for every sender on it. Our comparison of Maildoso and Inframail covers exactly this risk.
Setting up your sending IP warmup
Email warmup is the process of gradually increasing sending volume from a new inbox or IP to build a positive sending history with ISPs (Internet Service Providers). ISPs track how recipients interact with email from new senders, and starting at full volume on a cold inbox immediately triggers spam filters.
Many practitioners run 2-3 inboxes per domain to distribute sending load and reduce risk per inbox. Each inbox requires its own warmup period. For step-by-step guidance on warming up inboxes after migration, our help center covers the recommended daily volume targets.
Assessing sender reputation metrics
Sender reputation is a composite score assigned by ISPs and ESPs to your sending domain and IP based on historical sending behavior. It incorporates multiple signals:
IP reputation: The score tied specifically to your IP address, typically built through consistent sending volume and low complaint rates.
Domain reputation: The score tied to your sending domain. Major providers like Google and Microsoft track domain reputation, often independently from IP reputation.
Email reputation: The overall sending reputation combining IP and domain signals. Mail-Tester evaluates sending configuration and returns a score out of 10. We report 9.5/10 on Mail-Tester across tested domains.
Watch Nick Abraham's 2026 cold email deliverability breakdown for a practitioner's perspective on how reputation factors interact.
Evaluating inbox rates & vendor ROI
Comparing vendors and measuring campaign performance requires a clear set of metrics and an understanding of what each one actually measures. The subsections below cover inbox placement, bounce signals, spam scoring tools, and the cost variables that affect vendor selection decisions.
Avoiding inbox placement drops
The distinction between delivery rate and deliverability is one of the most misunderstood concepts in cold email infrastructure.
Delivery rate (acceptance rate): The percentage of emails the recipient's mail server accepts without bouncing or blocking at the server level. A high delivery rate means the server accepted your email, not that prospects saw it.
Deliverability (inbox placement rate): The percentage of accepted emails that land in the inbox rather than spam or junk. You can have a high delivery rate but low inbox placement if accepted emails route to the spam folder.
The distinction matters operationally. Delivery rate is a server metric. Inbox placement rate determines whether prospects actually see your campaigns. Always ask vendors for inbox placement data alongside delivery rate, and require methodology transparency: sample size, sending domains tested, test duration, and sending platforms used.
A deliverability collapse refers to a sharp drop in inbox placement, often caused by factors like blacklist additions, authentication failures, or spikes in spam complaints. An early warning system monitors domain and IP health continuously so you catch drops before clients do. Inframail's domain health monitoring checks blacklist additions and authentication failures in real time.
Monitor your email bounce rate
Bounce rate measures the percentage of sent emails that cannot be delivered. Hard bounces are permanent delivery failures (the address does not exist, or the server blocked your IP). Soft bounces are temporary failures (full mailbox or temporarily unavailable server). Industry guidance suggests hard bounce rates above 2-3% can damage sender reputation quickly.
Spam complaint rate is the percentage of recipients who mark your email as spam. Major providers like Gmail and Yahoo monitor complaint rates closely: industry best practices suggest keeping spam complaint rates well below 0.3%. Monitor complaint rates through your sending platform and remove complainers immediately.
Inframail's help center covers healthy campaign metric thresholds across bounce rate, reply rate, and spam signals.
Decoding your email spam score
Mail-Tester is a tool at mail-tester.com that evaluates your domain's sending configuration and returns a score out of 10. It checks SPF, DKIM, DMARC, blacklists, and content signals. Practitioners commonly target scores of 9+/10 for cold email sending. We report 9.5/10 across tested domains.
GMass inbox rate testing is a testing methodology that sends emails to test accounts across Gmail and other providers to measure actual inbox placement. GMass inbox rate testing measures actual inbox placement across Gmail and other providers, giving you a placement baseline before campaigns launch.
Sample size and test parameters matter. A test run on 10 domains is not comparable to a test run on 500 domains at production sending volume. When evaluating vendor deliverability claims, require methodology details: number of domains tested, volume per domain, test duration, and sending platforms used.
Evaluating deliverability vendors
Per-inbox costs are the fees charged per email account per month. Google Workspace Business Starter charges $8.40 per user per month. At 50 inboxes, that's $420/month in infrastructure before domains, warmup, or sending platform costs.
The sunk cost fallacy applies heavily to infrastructure vendor evaluation. Agencies commit $200-300 to domains and $129 to a first month on a platform before getting 30 days of real performance data. Once that money is spent, the tendency is to stay with a mediocre vendor rather than absorb switching costs.
Our cold email infrastructure cost comparison across 7 platforms covers per-inbox pricing versus flat-rate models with full cost breakdowns.
Essential domain records & blacklist defense
Domain-level decisions affect both deliverability and legal compliance in ways that IP and authentication configuration alone do not cover. The subsections below address rotation strategy, warmup scheduling, propagation timelines, blacklist defense, and list management requirements.
Managing domain rotation for deliverability
Domain strategy (primary vs. secondary) separates your main business domain from sending domains. A common best practice is to reserve your primary domain (your company's brand domain) for business correspondence only, not cold outreach. Secondary domains are purpose-bought for campaigns, often as variations related to your primary brand.
Domain rotation is the practice of cycling through multiple sending domains so no single domain carries the full sending load. Practitioners commonly run 2-3 inboxes per domain and cap daily sends at 30-50 emails per inbox. Our Mailreef vs Inframail comparison covers how infrastructure choices affect domain rotation capacity at agency scale.
Managing domain warmup effectively
A domain warmup schedule is the structured sending plan for a new domain. A practical warmup schedule follows this progression:
Week 1: Start with 5-10 emails per day to contacts who will engage
Week 2: Increase to 25-50 emails per day
Weeks 3-4: Ramp to 50-100 emails per day
Beyond week 4: Gradually approach your full target daily volume
New addresses on existing domains typically need 2-3 weeks of warmup. New addresses on brand-new domains often need 4-6 weeks because you're building domain reputation simultaneously with IP reputation. These timelines assume SPF, DKIM, and DMARC are already verified before warmup begins.
Cut DNS propagation delays by hours
DNS propagation is the time it takes for a new or updated DNS record to spread across the global network of DNS servers. Propagation commonly takes 24-48 hours for full global distribution after adding or updating records.
Automated platforms reduce configuration errors significantly. Once records are added correctly the first time (automatically), propagation completes on the standard schedule without the troubleshooting cycles caused by manual entry mistakes. An agency managing 50 domains can complete the entire configuration phase in minutes rather than days of back-and-forth error correction.
Email blacklists: deliverability impact
A blacklist (also called a blocklist or DNSBL) is a database of IP addresses or domains flagged for sending spam. When a receiving mail server checks an inbound email, it queries multiple blacklists. If your IP or domain appears on any major list, the email is blocked or routed to spam automatically.
Common blacklist providers include Spamhaus, SURBL, and Barracuda. Inframail's deliverability monitoring dashboard flags blacklist additions in real time and auto-submits delisting requests.
Spam traps are email addresses maintained by blacklist operators and ISPs to identify problematic sending practices. Hitting a spam trap often indicates sending to old, unverified, or purchased lists. Email verification tools like ZeroBounce and NeverBounce help identify and remove invalid addresses including potential spam traps before they cause deliverability issues.
Watch this tutorial on fixing emails going to spam for practical blacklist diagnostic and delisting workflows.
Allowlist for outbound email setup
Email list management is the practice of maintaining a clean, verified, and compliant contact database. Run every list through an email verification tool before your first send. Bounce rates above 3-5% can damage sender reputation across every domain you use. Maintain a suppression list of contacts who have opted out, bounced, or complained, and import it to your sending platform to prevent re-mailing them.
The CAN-SPAM Act is the US law governing commercial email. Key CAN-SPAM requirements include honest subject lines, a physical postal address in every email, an opt-out mechanism, and honoring opt-out requests within 10 business days. Violations carry penalties up to $53,088 per email. Our guide to cold email legal compliance covers CAN-SPAM requirements in full.
"I can set-up inboxes in 5mins while saving money on Google Workspace subscriptions and benefit from great deliverability." - Verified user review of Inframail
Don't make these outbound setup errors
A handful of setup mistakes account for most deliverability problems agencies run into after infrastructure is live. The subsections below answer the most common practical questions around propagation timing, protocol roles, IP selection, and warmup planning.
How long does DNS propagation take?
DNS propagation commonly takes 24-48 hours for records to fully spread across global DNS servers. The propagation timeline is the same whether you configure records manually or through an automated platform. The time saved by automation is in configuration accuracy, not propagation speed. Manual entry errors (wrong TXT record format, missing ~all qualifier on SPF, incorrect CNAME for DKIM) require identifying the mistake, correcting it, and waiting another full propagation cycle. Automated platforms eliminate this loop entirely.
SPF vs. DKIM: core roles explained
SPF and DKIM serve distinct functions that work together. SPF verifies that the sending server's IP is authorized to send email for your domain. DKIM verifies that the email content was not altered after it was sent. DMARC then tells receiving servers how to act when either check fails. Major mail providers strongly recommend implementing all three protocols for optimal inbox placement.
Do I need a dedicated IP for cold email?
Yes, if you want full control over your sender reputation. With a dedicated IP, your sending behavior determines how ISPs treat your email. The alternative, a shared IP pool, means other senders on the same pool can potentially affect your deliverability even when your campaigns are clean.
Setting optimal domain warmup duration
For a new email address on an existing domain, plan for 2-3 weeks of warmup before sending campaigns at full volume. For a new address on a brand-new domain, plan for 4-6 weeks because you're building domain reputation alongside IP reputation simultaneously. The Inframail inbox warmup guide covers recommended daily volume targets across each warmup week. Starting warmup with broken authentication wastes the entire warmup period.
Sign up to Inframail and get started today. Automated DNS configuration, unlimited inboxes, and 1-3 dedicated US-based IPs at $129/month with no per-seat charges and no manual DNS panel work required.
FAQs
What is the cost difference between Inframail and Google Workspace for 50 inboxes?
Google Workspace Business Starter costs $350/month for 50 inboxes at $7.00 per seat, plus amortized domain costs of $18-35/month, totaling roughly $368-385/month. Inframail's Unlimited Plan costs $129/month flat for unlimited inboxes plus the same amortized domain costs, totaling roughly $147-164/month. That's an estimated saving of approximately $204-238/month per our infrastructure cost comparison.
How does Inframail's automated DNS setup compare to manual configuration in time?
Manual DNS configuration for 50 domains requires logging into Namecheap, GoDaddy, or Cloudflare for each domain, entering SPF, DKIM, and DMARC records individually, and waiting for propagation, a process that can involve hours of active work. Inframail's automated platform configures SPF, DKIM, and DMARC rapidly per domain, with customers reporting 10 inboxes live in under 2 minutes.
How does Inframail handle blacklist issues?
Our platform auto-submits delisting requests when domains or IPs are flagged on blacklists. Manual delisting requires identifying the correct blacklist operator, submitting removal forms, and monitoring for confirmation independently.
Does Inframail include a warmup tool?
No, Inframail does not include a built-in warmup tool and requires an external service like Warmbox or Lemwarm, typically $15-50/month per inbox. The exception is the Done-for-You Email Campaign Setup package at $499/month, which bundles free email account warmup alongside automated DNS setup and sending platform access.
Key terms glossary
Cloudflare: A CDN and DNS management platform commonly used to manage domain DNS records for web and email infrastructure.
HubSpot: A CRM and marketing automation platform that includes email marketing capabilities.
MailerSend: An email delivery service provider offering transactional email capabilities.
Postmark: An email delivery service focused on transactional email infrastructure.
Inframail.io: The flat-rate Microsoft email infrastructure platform for cold email agencies, provisioning unlimited inboxes with automated SPF/DKIM/DMARC setup on dedicated US-based IPs at $129/month.
Mailforge.ai: A cold email infrastructure provider associated with email warmup capabilities via its companion Warmforge tool, a separate product within their Forge Stack ecosystem.
Supersend.io: A sales engagement platform supporting multichannel outreach capabilities.
Salesforge.ai: A sales engagement platform that reportedly combines email infrastructure with AI-powered personalization features.
Validity: An email deliverability and data quality platform provider offering monitoring and analytics tools for email programs.
MXToolbox: A diagnostic platform for checking domain DNS configuration, blacklist status, and mail server health across multiple parameters.
