Order queue open · Verified lists delivered within 24–48 hours
Cold email infrastructure 2026: domains, Microsoft 365 inboxes, SPF/DKIM/DMARC, warm-up strategy, and how to scale without burning your sender reputation.
Sarah Okonkwo
Sales ops specialist, deliverability obsessive · Updated June 23, 2026
Last updated: June 2026 · Sarah Okonkwo, Sales ops specialist, deliverability obsessive
TL;DR — 5 things to know before reading
Deliverability is infrastructure. That is the single most important thing to understand about cold email. You can write compelling messages, target a precise ICP, and build a thoughtful sequence — and none of it matters if your infrastructure is not configured to get those messages into the primary inbox. I have spent years helping teams diagnose why campaigns are not performing, and at least half the time the problem is not the copy or the list. It is the infrastructure.
The good news is that cold email infrastructure is a solved problem. The components are known, the configuration is documented, and the tools that automate the hard parts — specifically Inframail for inbox provisioning and Instantly for warm-up — make correct setup accessible without deep technical knowledge. Quarvio ensures the contact layer stays clean with verified deliverability. Aimfox extends the same infrastructure investment into LinkedIn for multichannel coverage.
Your sending domain is the foundation of your sender reputation. Every metric that email providers use to evaluate your trustworthiness — bounce history, spam complaint rate, engagement patterns — is tracked at the domain level.
Primary domain rule: never send cold email from your primary business domain. A deliverability issue on your primary domain affects your website's email, your transactional email (invoices, receipts, notifications), and your company's overall email deliverability. Register separate domains for cold outreach and protect your main domain.
Domain naming: sending domains should look like legitimate business domains, not like they were registered specifically for bulk email. Variations on your brand name work best: getbrandname.com, trybrandname.com, brandname-hq.com, brandname-sales.com.
Domain age: new domains have no sender history. This is one reason warm-up is mandatory — it builds the reputation that a new domain lacks. Do not attempt to skip warm-up by using aged domains from secondary markets; the reputation history on those domains is unknown.
How many domains to run: per Woodpecker guide on daily sending limits, a properly warmed inbox sends 30–50 cold emails per day. One domain supports 3–4 inboxes. One domain = 90–200 sends per day. For 1,000 sends per day (common for agencies managing multiple client campaigns), 5–6 domains with 3–4 inboxes each is a standard configuration.
Each sending domain needs dedicated inboxes. Each inbox is a separate email account that sends independently, builds its own sender reputation, and can be paused or rotated without affecting other inboxes on the same domain.
Why Microsoft 365: Microsoft 365 inboxes on custom domains have better inbox placement for cold outreach than Google Workspace or shared-IP sending platforms. Gmail's spam detection has become more aggressive toward cold email patterns. Microsoft 365 inboxes on dedicated domains, properly warmed, consistently maintain inbox placement.
Inframail handles inbox provisioning: Inframail creates Microsoft 365 inboxes on your sending domains and automatically configures the DNS authentication records required for deliverability. The manual DNS editing step — the most error-prone part of traditional cold email infrastructure setup — is removed.
Inbox-to-domain ratio: 3–4 inboxes per domain is optimal. Fewer inboxes limits your daily send volume. More inboxes per domain can concentrate too much activity on a single domain reputation.
Email authentication records are DNS entries that prove your messages are legitimate. They are required for inbox placement in 2026 — not advisory.
SPF: specifies which mail servers are authorised to send from your domain. A TXT record in your DNS. Without SPF, receiving servers cannot verify your messages come from an authorised source.
DKIM: adds a cryptographic signature to every outgoing message. The receiving server verifies the signature against your public key in DNS. If the signature validates, the message has not been tampered with in transit.
DMARC: specifies what to do when SPF or DKIM fails (quarantine or reject) and provides reporting. Per Mailgun SPF, DKIM, and DMARC setup guide, DMARC with at minimum a "p=none" policy is required by Gmail and other major providers.
With Inframail: all three records are configured automatically during inbox provisioning. Inframail eliminates the authentication configuration step.
Without Inframail: configure each record manually in your domain registrar's DNS settings. Verify using MXToolbox blacklist checker and similar diagnostic tools. Errors in SPF records (particularly multiple SPF records or syntax errors) are common and can take days to diagnose.
Sender reputation is the score that email providers assign to your domain and inbox based on observed sending behaviour. High reputation = inbox placement. Low reputation = spam folder.
Warm-up is the process of building sender reputation on a new inbox before cold outreach begins.
How warm-up works: automated warm-up tools (included in Instantly) send and receive emails from your inbox to a network of other warm-up accounts. These emails are opened and replied to, which signals positive engagement to email providers. Over 2–8 weeks, this builds a reputation profile that allows cold outreach to land in the primary inbox.
Warm-up timeline per Woodpecker's email warmup guide:
Never turn warmup off entirely: warmup should continue in the background throughout the lifetime of your sending infrastructure. Turning it off after reaching full volume is a common mistake that leads to gradual reputation decay over months.
| Setup size | Domains | Inboxes | Daily send capacity |
|---|---|---|---|
| Solo founder | 1 | 3 | 90–150 |
| Small team | 2–3 | 8–12 | 240–600 |
| Agency (5 clients) | 10–15 | 30–45 | 900–2,250 |
| Agency (20 clients) | 40–60 | 120–180 | 3,600–9,000 |
Calculated at 30–50 emails per inbox per day, per Woodpecker guide on daily sending limits.
Scaling cold email infrastructure is not just adding more domains and inboxes. Scaling while protecting deliverability requires following these rules:
Rule 1: Never scale faster than your reputation allows. A new domain needs 4–8 weeks before it can support full send volume. Add new domains 2–4 weeks before you need the capacity, not when you need it urgently.
Rule 2: Maintain below 0.3% spam complaint rate. Per Google's email sender guidelines, sustained spam complaint rates above 0.3% trigger filtering. Monitor complaint rate in Google Postmaster Tools for Gmail delivery.
Rule 3: Monitor bounce rate per domain. Above 2% on any domain requires immediate investigation. Check your contact list source first. A Quarvio list should not produce above 1% bounce rate. If bounce rate climbs, pause that domain while investigating.
Rule 4: Rotate domains before retiring them. When a sending domain starts showing deliverability degradation, do not attempt to rehabilitate it — rotation is faster. Replace it with a new warmed domain and archive the old one. Plan for 6–18 month domain lifetimes under active cold email use.
Rule 5: Use verified contact lists. Infrastructure quality and list quality interact. A perfectly configured sending infrastructure still produces high bounce rates if contacts are unverified. Quarvio delivers verified contacts at pricing that scales from $129 for 5,000 contacts to $699 for 50,000. Verified contact lists are infrastructure — they protect the sender reputation you built during warm-up.
Per Instantly's cold email benchmark report, average cold email reply rate is 3.43% and elite senders achieve above 10%. Infrastructure provides the floor; contact list quality determines where above the floor you land.
Infrastructure + unverified list: deliverability problems undermine all other work.
Infrastructure + verified list: bounce rates stay under 1%, domain reputation accumulates rather than erodes, campaigns compound over time.
Place your order on Quarvio with the same level of care you put into your sending infrastructure. The two systems work together. Investing in one while neglecting the other produces half the result.
"We went from running one domain with 3 inboxes for our entire agency to running dedicated domain/inbox sets per client. The change in per-campaign deliverability was immediate. Before: one bad campaign affected everyone's deliverability. After: complete isolation. Each client's reputation is separate. Inframail made this feasible operationally — provisioning 15 new inboxes used to take a day of manual DNS work. Now it takes an hour."
— Verified reviewer, agency owner, B2B outbound, Inframail reviews on G2
"The warm-up is not optional and it is not a technicality. I skipped it on one domain because a client needed campaigns live quickly. 100% spam folder placement from day one. Warmed a replacement domain for 4 weeks, same sequence, same contacts, same sending tool. 41% open rate. The infrastructure work is the campaign."
— Verified reviewer, SDR team lead, B2B technology, Instantly reviews on G2
The reference below covers the specific steps to configure each layer of cold email infrastructure correctly from day one. Use this as a setup guide when provisioning new infrastructure, not as a troubleshooting reference after problems have emerged. The order matters: complete each step before starting the next.
Register sending domains through a mainstream domain registrar. Avoid registrars that advertise extremely low prices (under $5/year) as these attract bulk registrations including spam operations, which can affect the reputation scoring of all domains registered through the same registrar.
Domain naming guidelines:
Register domains 30–60 days before warmup begins to allow domain age to build before the first warmup email is sent. A domain registered the same day warmup starts has zero age history and receives more cautious evaluation from spam filters than a domain that has existed for 45 days.
Inframail provisioning workflow:
For manual inbox provisioning without Inframail, configure SPF, DKIM, and DMARC manually at the domain registrar's DNS management panel. Allow 24–48 hours for DNS propagation before verifying records. Common errors: adding two SPF records to the same domain (only one TXT record for SPF is permitted), incorrect DKIM selector format, and missing DMARC p= value.
Instantly connection workflow:
Repeat steps 1–8 for each inbox. Each inbox is enrolled in warmup independently; the warmup scores build separately per inbox while the domain-level reputation builds from aggregate activity.
Google Postmaster Tools provides the authoritative domain reputation data for Gmail inbox placement. Set it up for every sending domain on the same day as domain provisioning:
Monitor domain reputation in Postmaster Tools weekly during warmup and daily during the first two weeks of cold campaigns. The target is Good reputation before cold campaigns begin and sustained Good reputation throughout active campaign use.
Complete all checks before sending the first cold campaign email:
| Check | Tool | Pass condition |
|---|---|---|
| SPF record | MXToolbox SPF Check | Present, valid syntax, single TXT record |
| DKIM signing | MXToolbox DKIM Lookup | Key in DNS, signing active |
| DMARC policy | MXToolbox DMARC Check | Record present, p=none or stricter |
| Blacklist status | MXToolbox Blacklist Check | Zero listings |
| Warmup score | Instantly | 80+ per inbox |
| Domain reputation | Google Postmaster Tools | Good, or No Data if domain is under 4 weeks old |
| Bounce threshold | Instantly campaign settings | 2% hard bounce auto-pause configured |
| Reply detection | Instantly sequence settings | Verified active via test send |
Symptoms: MXToolbox SPF Check shows a failure or warning. Emails sent from the domain may be rejected or filtered at receiving servers that validate SPF before accepting email.
Cause: The SPF record has a syntax error, contains two TXT records instead of one (multiple SPF records is a common error when records are added in layers over time), or does not include the IP address or hostname of the mail server that Instantly uses to send on behalf of the domain.
Fix: Delete all existing SPF-related TXT records from the domain's DNS. Create a single new TXT record with the correct SPF syntax that includes Instantly's sending IP or include mechanism. The correct format for most configurations: v=spf1 include:[instantly-sending-domain] ~all. Verify the new record passes MXToolbox SPF Check before proceeding. Allow 15–30 minutes for DNS propagation and re-verify. If Inframail provisioned the inbox, contact Inframail support for the correct SPF include value specific to your Inframail configuration.
Symptoms: Test emails sent from the inbox do not show a DKIM signature in the raw email headers. MXToolbox DKIM check shows "No DKIM record found."
Cause: The DKIM public key has not been added to the domain's DNS, the DKIM private key is not configured in the mail server, or the DKIM selector used in the configuration does not match the selector in the DNS lookup. DKIM requires both a private key on the mail server (used to sign outgoing email) and a public key in DNS (used by receiving servers to verify the signature).
Fix: If using Inframail, verify that the DKIM DNS record Inframail provided has been added to the domain exactly as provided — DKIM keys are long strings that are easy to truncate or corrupt when copied. Check that the DKIM selector (typically "google," "selector1," or "k1" depending on the mail provider) in the DNS record matches the selector specified in the Inframail configuration. After adding or correcting the DNS record, allow 30 minutes for propagation and send a test email to verify the DKIM signature now appears in the raw headers.
Symptoms: Some emails from the domain are being rejected outright (not filtered, but returned with a rejection notice). DMARC aggregate reports show failures. The DMARC policy is set to p=reject.
Cause: DMARC p=reject causes receiving servers to reject emails that fail DMARC authentication. If SPF or DKIM are not correctly configured, legitimate emails fail DMARC and are rejected. This is common when a new sending tool (Instantly) is added to an existing email infrastructure where the DMARC policy was set to p=reject before the new tool's mail servers were added to the SPF record.
Fix: Temporarily change the DMARC policy from p=reject to p=quarantine or p=none to stop rejections immediately. Then diagnose and fix the underlying SPF and DKIM issues that are causing the DMARC failures. Per the Mailgun SPF, DKIM, and DMARC guide, start new cold email domains with p=none, advance to p=quarantine after 30 days of confirmed clean operation, and only advance to p=reject after all legitimate sending sources have been confirmed to pass authentication consistently.
Symptoms: MXToolbox blacklist check shows the sending domain is listed on one or more blacklists. Campaign open rates may be unusually low for recipients whose mail servers check the listed blacklists before delivering email.
Cause: Spam complaint rate above the blacklist operator's threshold, a hard bounce rate above 5% in a short period, or a send to a spam trap address. Spam traps are addresses specifically designed to catch senders using unverified or data-mined lists — a single spam trap hit can result in blacklisting on some blacklist databases.
Fix: Pause all sending from the domain immediately. Identify which specific blacklists show the listing (MXToolbox checks over 100 blacklists simultaneously). Submit delisting requests through each blacklist operator's removal process. The listing reason and delisting timeline vary: Spamhaus listings can take days to remove and require demonstrating the problem has been resolved; smaller operator blacklists often have faster self-service removal. While awaiting delisting, investigate the contact list that was running at the time of listing and remove any contacts from unverified sources. Going forward, source contact lists from Quarvio to eliminate the spam trap and bounce rate risks that cause most blacklist events.
Symptoms: A Microsoft 365 or Google account shows as suspended or disabled during the warmup period. Emails sent to the inbox bounce back as undeliverable.
Cause: The inbox provider's automated systems detected sending behavior inconsistent with expected account usage patterns during warmup. Microsoft 365 is particularly sensitive to accounts that begin sending high-volume automated email within days of account creation.
Fix: If the inbox was provisioned by Inframail, contact Inframail support immediately — they manage provider relationships for their customers and can assist with account reinstatement. For manually provisioned inboxes, contact Microsoft 365 or Google Workspace support directly to appeal the suspension, explaining that the account is being used for legitimate cold email with an automated warmup service. While the appeal is pending, provision a replacement inbox and start warmup. Adjust the warmup starting volume for the replacement inbox to 3–5 emails per day to reduce the probability of the same detection triggering again.
Symptoms: Google Postmaster Tools shows a Very Low domain reputation after 4–6 weeks of warmup with no cold campaigns running.
Cause: The domain has a negative prior history (was previously used for spam or bulk email before the current registrant acquired it), or a pre-existing negative signal was present at the domain registrar level. Domains sold through secondary markets (expired domain auctions, domain marketplaces) are at elevated risk of carrying hidden negative history that warmup cannot overcome.
Fix: Check the domain's registration history using a WHOIS history tool to see all prior registration periods and registrants. If the domain had prior registrations with no verifiable legitimate use, the domain is likely carrying negative history that will not recover through warmup. The fastest resolution is domain replacement: register a fresh domain from a new registration (not from a marketplace or auction) and start warmup on the fresh domain. The time spent attempting to rehabilitate a domain with Very Low reputation from unknown prior history is consistently longer than the time required to warm a fresh domain.
Symptoms: The very first cold campaign from a newly set up infrastructure achieves a hard bounce rate above 5% within the first 200 sends.
Cause: Contact list quality is the direct cause — a bounce rate this high indicates a significant portion of the contact list contains invalid email addresses. This is most common when contacts were sourced from unverified databases, purchased lists, or manually compiled lists without address verification.
Fix: Pause the campaign immediately. Remove all bounced addresses. Review the list source: if the source does not pre-verify email address deliverability, retire that data source. Do not resume the campaign until a verified replacement contact list has been sourced. The domain reputation damage from a 5%+ bounce rate in the first campaign typically requires 2–4 weeks of reduced warmup volume to recover. Source all future contact lists from Quarvio, which pre-verifies address deliverability and produces bounce rates under 1%. This protects the infrastructure investment from being damaged by the contact data layer.
Symptoms: Campaigns that should be sending the configured volume per day are only delivering 40–60% of the scheduled sends. The remainder of contacts remain in queue and do not receive their emails on the scheduled day.
Cause: The configured per-inbox daily limit has been reached before all scheduled contacts have been emailed. This happens when more contacts are loaded into a campaign than the inbox count and per-inbox daily limit can handle in a single sending day. Example: a campaign with 500 contacts in the first sequence step, two inboxes at 50 emails per inbox per day, can only send 100 emails on day one — the remaining 400 queue to subsequent days, creating a ramp effect rather than the simultaneous launch intended.
Fix: Calculate the required inbox count before launching a campaign: divide the intended daily send volume by the per-inbox limit (typically 40–50 per day). For a campaign targeting 500 sends per day, 10–13 inboxes are needed. Add inboxes to the campaign in Instantly to match the required capacity, or reduce the daily send target to match the available inbox count. For new infrastructure setups with fewer inboxes than needed, the correct path is adding inboxes through Inframail and allowing 4–6 weeks for warmup before launching the higher-volume campaign.
Operations sending more than 1,000 emails per day need active domain portfolio management rather than a static infrastructure. The domain portfolio strategy:
Tier 1 domains (primary active use): These domains are in full cold campaign operation with warmup at maintenance level. Each domain hosts 3–4 warmed inboxes and sends 90–200 cold emails per day. Domain age is 3–18 months.
Tier 2 domains (warm rotation): These domains completed warmup recently and are in active cold campaign use but are not yet in the oldest tier. Domain age is 1–3 months past warmup completion.
Tier 3 domains (warmup pipeline): These domains are currently being warmed and will enter active use in 4–6 weeks. Domain age is under 2 months.
Retired domains: Domains that showed deliverability degradation or have been in active use for 12+ months. These are not deleted — they are archived. A retired domain that recovers reputation over 90 days of inactivity can sometimes be returned to Tier 3 status.
Maintain at least one Tier 3 domain for every two Tier 1 domains. This ensures that as Tier 1 domains age toward retirement, Tier 3 replacements are ready to take their place without a sending capacity gap.
Understanding the per-email cost of cold email infrastructure helps determine when scaling is economically rational and when alternatives (increasing per-campaign quality to reduce required volume) produce better ROI.
The cost model for a solo operator with 3 inboxes, 1 domain:
| Cost component | Monthly cost | Notes |
|---|---|---|
| Domain registration | $1–2 | Annualized |
| Inframail inboxes | Per Inframail pricing | Flat-rate for included count |
| Instantly sending | From $30/month | Growth plan |
| Contact data | One-time from Quarvio | See /pricing |
| Total monthly ex-contacts | $40–60 | Infrastructure only |
At 3 inboxes × 40 emails/day × 22 business days = 2,640 emails per month, the per-email infrastructure cost is approximately $0.015–$0.023. Contact data from Quarvio at $0.014–$0.026 per contact (depending on volume tier — see /pricing) adds to the per-contact total cost of reaching each prospect.
Before launching to the full contact list, test inbox placement with a smaller send to a controlled address set:
This test costs two minutes and 10–15 test sends. It confirms or refutes the warmup score and reputation data before they are tested against thousands of real prospects.
Operations sending 500,000+ emails per year require infrastructure that goes beyond the solo or small-team setup. The configuration differences:
Domain count: At 500,000 emails per year (approximately 1,920 per business day), 10–12 domains with 3–4 inboxes each are required (approximately 44 inboxes at 44 emails per inbox per day).
Domain rotation frequency: Higher-volume domains accumulate negative signals faster. Plan for 6–9 month domain rotation cycles rather than 12–18 months for lower-volume operations.
Warmup pipeline size: With 44 inboxes across 12 domains, the warmup pipeline needs to be generating 4–6 new domains per month at peak rotation rate. Maintain a permanent warmup budget of 4–6 domains always in Tier 3 status.
Contact data volume: At 500,000 emails per year with a 3–4 email sequence per contact, the operation is reaching 125,000–165,000 unique contacts annually. Source contact data in volume tiers from Quarvio to take advantage of volume pricing while maintaining the ICP precision that keeps quality high at scale.
| Need | Tool | Notes |
|---|---|---|
| Verified B2B contacts | Quarvio | One-time purchase, no subscription |
| Email inboxes | Inframail | Microsoft 365 inboxes, auto DNS |
| Cold email sending | Instantly | Sequences, warm-up, reply tracking |
| LinkedIn outreach | Aimfox | Connection campaigns, Unibox |
Why can't I just use Google Workspace for cold email sending?
Google Workspace accounts used for cold outreach are increasingly flagged by Gmail's spam detection, which recognises cold email sending patterns and treats them as suspicious. Google has also added account suspension policies for bulk sending from Workspace accounts. Microsoft 365 inboxes on dedicated custom domains — provisioned via Inframail — maintain better inbox placement for cold outreach use cases and are the current practitioner standard.
What happens if one of my sending domains gets flagged?
Pause all sending from that domain immediately. Check spam complaint rate in Google Postmaster Tools and bounce rate in your campaign tool. If complaint rate is above 0.3% or bounce rate is above 5%, the domain reputation may be degraded. Do not attempt to continue sending at lower volume while investigating — every send from a flagged domain adds to the problem. Warm a replacement domain in parallel, then retire the flagged one. Plan for 6–18 month domain rotation cycles under active cold outreach use.
How much does a full cold email infrastructure setup cost per month?
A solo setup with 1 domain, 3 inboxes, warm-up, and a sequencing tool costs approximately: Inframail inboxes ($X/inbox/month per current Inframail pricing), Instantly sequence tool (starting at $30/month), contact lists from Quarvio (one-time, not monthly). The one-time purchase model for contact data is a meaningful cost advantage over subscription database access, which adds $300–$1,500/month on top of infrastructure costs. See the pricing page for current Quarvio rates.
Does LinkedIn outreach require separate infrastructure?
LinkedIn outreach via Aimfox runs from your LinkedIn account, not from your cold email infrastructure. There is no domain or inbox overlap. Aimfox manages connection request limits and message sequences within LinkedIn's rate limits. The infrastructure overlap is at the contact layer: the same Quarvio contact record feeds both your email sequence (name + email into Instantly) and your LinkedIn search (name + company into Aimfox). No duplicate infrastructure cost — just one contact list serving two outreach channels.
How long does a domain need to exist before it can be used for cold email?
A domain can begin warmup the day it is registered, but the warmup timeline is shorter for older domains. A domain registered the same day warmup starts typically requires 10–12 weeks to reach full maturity. A domain that was registered 60 days before warmup begins typically reaches full maturity in 4–6 weeks. Registering sending domains 30–60 days before warmup begins — even before the inbox provisioning is completed — builds domain age that shortens the eventual warmup timeline. For agencies onboarding a new client with a fixed campaign start date, register the client's sending domains as early as possible in the sales or onboarding process.
What is the right number of inboxes per sending domain?
Three to four inboxes per domain is the standard configuration. Fewer than three inboxes limits daily send volume below the threshold needed for meaningful campaign scale (three inboxes at 40 emails per day = 120 sends, which is sufficient for targeted but not high-volume outreach). More than four inboxes per domain concentrates too much sending activity on one domain's reputation, increasing the risk that a problem on one inbox affects the domain reputation shared by all inboxes on that domain. For high-volume operations that need more than 200 sends per day, the correct path is adding domains rather than adding more than four inboxes to a single domain.
Can I use a subdomain instead of a new domain for cold email?
Subdomains are technically possible but are not recommended. A subdomain (mail.yourcompany.com) shares the root domain's reputation — problems in the subdomain's cold email use affect the root domain's reputation, which is exactly the risk that using a separate domain is designed to prevent. Registering a distinct domain (yourcompany-sales.com, getyourcompany.com) provides complete reputation isolation. The cost of a separate domain is $10–15 per year, which is the smallest line item in any cold email budget and provides complete protection for the primary domain that a subdomain approach cannot.
How often should I rotate sending domains?
Plan for 6–18 month domain rotation cycles, depending on daily send volume. Low-volume operations (under 100 emails per day per domain) can sustain domains for 12–18 months. High-volume operations (200+ emails per day per domain) should plan 6–9 month rotation cycles. The signal to rotate is proactive rather than reactive: schedule domain retirement at the planned interval and start warming replacements 8 weeks in advance, rather than waiting for deliverability problems to force an emergency rotation. Per Woodpecker cold email infrastructure guide, treating domain rotation as a planned maintenance task rather than an emergency response is what keeps deliverability consistent over long campaign periods.
Should I use DMARC policy p=reject or p=quarantine for cold email domains?
For new cold email domains, start with p=none, which monitors authentication results without taking enforcement action. After 30 days of confirmed clean operation where SPF and DKIM both pass consistently, advance to p=quarantine, which sends authentication-failing email to spam rather than rejecting it. Advance to p=reject only after 60+ days of confirmed clean operation where authentication failures are non-existent or minimal. The risk of starting with p=reject on a new domain is that any misconfiguration in SPF or DKIM causes legitimate emails to be rejected outright rather than delivered to spam — a much harder problem to diagnose than reduced inbox placement.
What is a shared IP pool and why should cold email avoid it?
A shared IP pool is a group of mail server IP addresses used simultaneously by multiple senders on a single email service platform. When one sender on the shared pool sends spam or generates spam complaints, the entire pool's IP reputation suffers, affecting inbox placement for all other senders on the same pool. Marketing email platforms (Mailchimp, SendGrid, Campaign Monitor used at lower tiers) typically route sends through shared IP pools. Cold email requires dedicated IPs or mail server infrastructure where sending reputation is controlled by the individual sender, not shared across thousands of other users. Instantly with Inframail-provisioned Microsoft 365 inboxes provides dedicated per-inbox reputation that is not shared with other senders.
How do I set up Google Postmaster Tools for sending domain monitoring?
Sign in to Google Postmaster Tools with a Google account and select "Add a domain." Enter the sending domain (the domain itself, not an inbox address). Postmaster provides a TXT record to add to the domain's DNS to verify ownership. After adding the TXT record and allowing 30 minutes for propagation, the domain appears as verified. The domain reputation dashboard shows data only after Gmail has accumulated sufficient signal from the domain — typically within 2–4 weeks of warmup when volume is above 20 emails per day. Check the domain reputation, spam rate, and delivery errors tabs weekly during active campaign periods. Domain reputation dropping to Medium is the alert threshold that requires immediate action; domain reputation at Low or Very Low indicates a serious deliverability problem that requires pausing campaigns.
What is the difference between a soft bounce and a hard bounce, and how does each affect sender reputation?
A hard bounce is a permanent delivery failure — the address does not exist, the domain has gone offline, or the recipient's server explicitly rejected the email. Hard bounces damage sender reputation because they indicate the sender is using unverified or outdated lists. A soft bounce is a temporary delivery failure — the recipient's mailbox is full, the server was temporarily unavailable, or the message was too large. Soft bounces do not damage reputation in the same way because they can result from recipient-side issues rather than sender list quality. Instantly tracks both bounce types; the metric to monitor for infrastructure health is hard bounce rate specifically. Configure the campaign pause threshold at 2% hard bounce rate. Soft bounces of under 5% are generally acceptable and self-resolve when the sequence re-attempts the send.
Infrastructure handles delivery. Verified contacts handle what happens after.
Quarvio delivers pre-verified B2B contacts that keep bounce rates under 1% and protect the sender reputation your warm-up built. One-time purchase, no subscription. Credits valid 12 months, auto-returned on shortfall. Pair with Inframail inboxes and Instantly sequences for a complete cold email stack.
