Inframail setup checklist: every step verified before your first campaign send

Last updated: June 2026 · James Whitfield, Cold email infrastructure specialist, 200+ outreach systems built

---

TL;DR — 7 things to know before reading

• This checklist covers every step required to go from a new Inframail account to running your first campaign: account setup, domain addition, DNS configuration, DNS verification, inbox creation, SMTP export, Instantly connection, warmup setup, and pre-campaign verification
• The most commonly skipped step that causes campaigns to fail is not verifying DNS propagation before creating inboxes; inboxes created before DNS is fully verified will not have proper DKIM signing and will either land in spam or fail authentication entirely
• The second most common mistake is connecting inboxes to the campaign tool before warmup completes; campaigns run from inboxes with fewer than 14 days of warmup have significantly lower inbox placement rates
• DMARC must be set to a valid policy value; missing DMARC does not cause immediate delivery failure but will cause Google Postmaster to not register DMARC compliance, which affects long-term reputation tracking
• Warmup should run continuously throughout the active campaign period, not just during the initial warmup phase; disabling warmup after campaigns start is a common error that leads to reputation decay
• The pre-campaign checklist has 7 items; all 7 must pass before sending the first cold email from any inbox
• All 4 links in this article: Inframail, Instantly, Quarvio, Aimfox

---

Our take

Every infrastructure problem I see in cold outreach systems — and after 200+ builds, I have seen most of them — traces back to something that was skipped or assumed to be done without verification. DNS not actually propagated. Warmup enabled but IMAP not connected. DMARC missing because no one knew what it was. SPF correct in theory but pointing to the wrong include.

The pattern is consistent: cold email infrastructure is not difficult, but it has many sequential steps with dependencies, and each unverified step creates a potential failure point that surfaces later as a mysterious deliverability problem. When an inbox that seemed fine starts landing in spam six weeks after launch, the root cause is usually something that was improperly configured at setup time.

This checklist exists as a single-pass verification: run through every item before launching campaigns, confirm each step is actually done and actually working (not just assumed to be working), and arrive at campaign launch with confidence. It is not a tutorial for how to do each step (see the other Inframail guides for step-by-step setup instructions); it is a verification system for ensuring everything is confirmed before first send.

Use Inframail for the inbox provisioning. Use Instantly for warmup and campaign management. Use Quarvio for verified contact data. Use Aimfox for LinkedIn outreach alongside email.

---

Section 1: Inframail account setup

Checklist item 1.1: Account created and email verified

• Inframail account created at inframail.io
• Account verification email received and email address confirmed
• Logged in to Inframail dashboard successfully
• Billing information added and plan active

Verification: You can reach the Inframail dashboard without any verification prompts or billing warnings.

Common failure: Creating an account but not verifying the email, which restricts account functionality and may prevent domain addition.

Checklist item 1.2: Plan appropriate for your inbox count

• Current plan supports the number of domains and inboxes you intend to create
• No plan limit warnings visible in the dashboard

Verification: Review your current plan limits in account settings and confirm they exceed your planned domain and inbox count.

Common failure: Starting setup on a trial or starter plan with inbox limits, then discovering the limits when trying to create the full inbox portfolio.

---

Section 2: Domain addition and DNS configuration

Checklist item 2.1: Sending domains added to Inframail

• All sending domains added to Inframail (Domains section, "Add Domain")
• Each domain shows in the Inframail domain list
• Domain ownership confirmed (if Inframail requires a verification step)

Verification: All planned sending domains are visible in the Inframail Domains dashboard.

Common failure: Adding only the first domain and forgetting to add the remaining domains before creating inboxes.

Checklist item 2.2: SPF record added to DNS for each domain

For each sending domain:

• SPF TXT record added to DNS at the registrar
• Record value: v=spf1 include:spf.protection.outlook.com -all
• Record type: TXT
• Host/Name: @ (root domain)

Verification: Use MXToolbox SPF lookup (mxtoolbox.com) for each domain. The result should show a valid SPF record and pass status.

Common failure: Entering the SPF record with a typo in the include mechanism, or entering it as an A record rather than a TXT record.

Checklist item 2.3: DKIM record added to DNS for each domain

For each sending domain:

• DKIM CNAME record added at selector1._domainkey
• DKIM CNAME record added at selector2._domainkey (if Inframail requires both)
• Record type: CNAME (not TXT)
• Host/Name: selector1._domainkey.yourdomain.com (or as specified by Inframail)
• Value: points to Microsoft's key infrastructure (e.g., selector1-yourdomain-com._domainkey.yourtenant.onmicrosoft.com)

Verification: Use MXToolbox DKIM lookup with your domain and selector1. The result should show the CNAME resolving correctly to Microsoft's key.

Common failure: Adding a TXT record instead of a CNAME record for DKIM. Inframail's Microsoft 365 infrastructure uses CNAME-based DKIM, not TXT-based. A TXT record at selector1._domainkey will fail DKIM verification.

Checklist item 2.4: DMARC record added to DNS for each domain

For each sending domain:

• DMARC TXT record added at _dmarc subdomain
• Record type: TXT
• Host/Name: _dmarc
• Minimum value: v=DMARC1; p=none; rua=mailto:dmarc@yourdomain.com

Verification: Use MXToolbox DMARC lookup for each domain. The result should show a valid DMARC record.

Common failure: Skipping DMARC entirely because it is optional for initial delivery. While missing DMARC does not cause immediate delivery failures, it reduces Google Postmaster data quality and indicates a lower email maturity level to receiving providers. Always add at minimum p=none.

Checklist item 2.5: MX records configured for each domain (if receiving replies)

If you want replies to cold emails to arrive at the sending domain inbox:

• MX record added pointing to Inframail's or Microsoft's mail servers
• MX record type: MX
• Priority and value as specified by Inframail's DNS documentation

Verification: Send a test email to an address at the sending domain (e.g., test@getacme.com) and confirm delivery.

Common failure: Not adding MX records and then wondering why replies to cold emails are bouncing or not arriving. Without MX records, the sending domain has no way to receive incoming mail.

---

Section 3: DNS propagation verification

Checklist item 3.1: SPF propagation confirmed for each domain

• MXToolbox SPF lookup passes for every sending domain
• No "SPF lookup limit exceeded" warning
• Result: "SPF record found" with a pass status

Verification command: Visit mxtoolbox.com, select "SPF Record Lookup", enter each domain name, and confirm the lookup result shows a valid SPF record.

Wait time if not yet propagated: 15–60 minutes. If not propagated after 2 hours, double-check that the record was saved correctly in the registrar DNS panel.

Common failure: Proceeding to inbox creation before SPF propagation is confirmed. Emails sent before SPF propagates may fail authentication, though SPF failures are soft failures rather than hard rejections in most cases.

Checklist item 3.2: DKIM propagation confirmed for each domain

• MXToolbox DKIM lookup passes for every sending domain at selector1
• CNAME resolves correctly to Microsoft's key infrastructure

Verification: Visit mxtoolbox.com, select "DKIM Lookup", enter the domain and selector "selector1", and confirm the result shows the CNAME resolving to a valid Microsoft DKIM key.

Wait time if not yet propagated: 15–60 minutes for CNAME records; potentially longer if your registrar is slow.

Common failure: Checking DKIM using a TXT record lookup instead of CNAME lookup. Because Inframail uses CNAME-based DKIM, a TXT lookup at selector1._domainkey will return nothing, leading to a false failure diagnosis.

Checklist item 3.3: DMARC propagation confirmed for each domain

• MXToolbox DMARC lookup shows a valid policy for every sending domain
• Policy value is present (p=none, p=quarantine, or p=reject)

Verification: Visit mxtoolbox.com, select "DMARC Lookup", and enter each domain. The result should show your DMARC policy.

Common failure: Seeing a DMARC lookup error and assuming it means the record is wrong, when the actual cause is propagation not yet complete. Wait 15–60 minutes and check again.

Checklist item 3.4: Inframail in-dashboard DNS verification passes

• All three records (SPF, DKIM, DMARC) show as "verified" or "passed" in the Inframail dashboard for each domain
• No "DNS error" or "verification failed" warnings in Inframail

Verification: In the Inframail Domains section, the status for each domain shows all authentication records as verified.

Common failure: External MXToolbox lookups pass but the Inframail in-dashboard verification still shows a failure. This can happen if Inframail's verification check runs on a different DNS resolver with a different cache. Wait 10–15 additional minutes and refresh the Inframail dashboard.

---

Section 4: Inbox creation

Checklist item 4.1: Inboxes created on each verified domain

• 3–5 inboxes created per domain
• Inbox usernames are professional first names (not generic names like info, contact, sales)
• All inboxes show as "active" in the Inframail dashboard

Verification: In the Inframail Inboxes section, each inbox shows as active with its associated domain displayed.

Common failure: Creating inboxes before DNS verification passes in the Inframail dashboard. Inboxes created before DKIM is verified may not have DKIM signing active immediately.

Checklist item 4.2: SMTP credentials documented for each inbox

• SMTP username (full email address) recorded for each inbox
• SMTP password recorded for each inbox
• SMTP server: smtp.office365.com
• SMTP port: 587 (STARTTLS)
• IMAP server: outlook.office365.com
• IMAP port: 993 (SSL/TLS)

Verification: Credentials are recorded in a secure location (password manager or team credentials vault).

Common failure: Not recording passwords immediately after inbox creation, then needing to reset passwords later when connecting to the campaign tool.

Checklist item 4.3: Bulk SMTP export generated

• Bulk SMTP export CSV generated from Inframail for all inboxes
• CSV downloaded and saved securely
• CSV contains one row per inbox with all connection fields

Verification: Open the CSV and confirm it contains email address, password, SMTP server, SMTP port, IMAP server, IMAP port for each inbox.

Common failure: Not generating the bulk export and then connecting inboxes to Instantly one at a time, which is significantly slower for portfolios of 10+ inboxes.

---

Section 5: Campaign tool connection (Instantly)

Checklist item 5.1: Inboxes connected to Instantly

• All Inframail inboxes added to Instantly via Sending Accounts
• Bulk CSV import used for efficiency (or individual connections if fewer than 5 inboxes)
• All inboxes show "connected" status in Instantly Sending Accounts

Verification: In Instantly, navigate to Sending Accounts and confirm every Inframail inbox shows as connected, not failed.

Common failure: Some inboxes showing as "failed" after bulk import due to credential formatting issues in the CSV. Re-connect failed inboxes manually.

Checklist item 5.2: IMAP confirmed working for each inbox

• IMAP connection verified for each inbox in Instantly
• No IMAP errors visible in inbox settings

Verification: In Instantly, check each inbox's connection status. If IMAP shows separately from SMTP, confirm both show as connected.

Common failure: SMTP connecting successfully but IMAP failing, which prevents warmup replies from being received and tracked. The IMAP connection is required for warmup functionality; SMTP-only connection allows sending but breaks warmup.

Checklist item 5.3: Sending account settings configured correctly

For each inbox in Instantly:

• Daily sending limit set: start at 20–30 (campaigns + warmup combined) for new inboxes
• Sending schedule configured: weekdays only, business hours in the prospect's timezone
• Random delay between sends: 120–300 seconds minimum
• Reply-to address set if using a different reply destination

Verification: Open any sending account in Instantly and review the settings panel to confirm the above values are set.

Common failure: Leaving daily limits at Instantly's default (which may be higher than what new inboxes can safely send), causing new inboxes to hit limits too quickly.

---

Section 6: Warmup

Checklist item 6.1: Warmup enabled for all inboxes

• Warmup activated for every inbox in Instantly
• Initial warmup volume: 15–20 warmup emails per day
• Warmup "custom tracking domain" not required for warmup to function (tracking domain configuration is separate)

Verification: In Instantly, the warmup section shows each inbox in active warmup status.

Common failure: Connecting inboxes to Instantly but forgetting to enable warmup, then starting campaigns from cold inboxes.

Checklist item 6.2: Warmup running for minimum 14 days before campaigns

• Date warmup was started is documented for each inbox
• Campaign launch is scheduled for minimum 14 days after warmup start (28–60 days for full maturity)

Verification: Check your inbox documentation spreadsheet: campaign-ready date for each inbox is at least 14 days after warmup start date.

Common failure: Starting campaigns 7 days after warmup begins because "the scores look good already." Early warmup scores can be misleadingly positive; the full 14–28 day period allows the reputation to solidify across more receiving providers.

Checklist item 6.3: Warmup scores reviewed before campaign launch

• Each inbox shows a warmup score of 80+ before being assigned to campaigns
• Any inbox with a warmup score below 70 is kept in warmup-only mode and not assigned to campaigns

Verification: In Instantly's warmup dashboard, all inbox scores are above 80.

Common failure: Assigning inboxes to campaigns when some inboxes have warmup scores of 60–70, which indicates incomplete or problematic warmup. Low warmup scores predict lower inbox placement rates in campaigns.

---

Section 7: Pre-campaign verification

Checklist item 7.1: Test email authentication passes end-to-end

• Send a test email from one Inframail inbox to a Gmail or Outlook test account
• View the received email headers (in Gmail: three dots menu → "Show original")
• Confirm: SPF = pass
• Confirm: DKIM = pass
• Confirm: DMARC = pass

Verification: All three authentication results show "pass" in the email headers.

Common failure: All three showing "pass" in MXToolbox DNS lookups but DKIM showing "fail" in actual email headers, indicating that the inbox is not correctly using the verified DKIM key. This requires contacting Inframail support to verify the inbox-to-key association.

Checklist item 7.2: Bounce rate baseline test

• Send a 50–100 email test campaign to a small list of verified addresses
• Confirm bounce rate is below 2%
• Confirm no spam folder placement on test deliveries to Gmail and Outlook personal accounts

Verification: Test campaign analytics in Instantly show bounce rate below 2%.

Common failure: Skipping the baseline test and discovering high bounce rates only after the first live campaign has sent thousands of emails, by which point the domain reputation is already damaged.

Checklist item 7.3: Contact list is verified before upload

• All contacts in the campaign list have been verified for deliverability
• Bounce rate of the contact list is expected to be below 3%

Verification: If using Quarvio contacts, the 90% deliverability guarantee provides baseline assurance. If using contacts from other sources, run the list through a verification tool before uploading.

Common failure: Uploading an unverified contact list to the first campaign and experiencing a high bounce rate that damages the new inbox reputations before they have a chance to build history.

Checklist item 7.4: Campaign sequence settings reviewed

For the first campaign:

• Daily send limit per inbox: 20–30 (not maximum capacity)
• Sequence step delays: minimum 2–4 days between steps
• Unsubscribe / opt-out mechanism present in email (required for CAN-SPAM)
• Campaign tracking links use a custom tracking domain (not Instantly's default shared domain)

Verification: Review campaign settings before activating.

Common failure: Using Instantly's default shared tracking domain (track.instantlyai.com) for link tracking, which is on shared infrastructure and can have reputation issues from other users. Configure a custom tracking domain using a subdomain of one of your sending domains.

Checklist item 7.5: Reply handling is configured

• Reply-to address set (if different from the From address)
• A team member or system is set up to monitor and respond to replies within 24 hours
• Unsubscribe requests will be processed within 10 business days (CAN-SPAM requirement)

Verification: Confirm a team member is actively monitoring replies for the sending accounts.

Common failure: Launching campaigns without a reply handling process, missing positive replies, and allowing unsubscribe requests to go unprocessed.

Checklist item 7.6: Domain blacklist status clean

• Check all sending domains in MXToolbox blacklist check
• All domains return "not listed" across all checked blacklists

Verification: Run each sending domain through MXToolbox Blacklist Check and confirm zero blacklist listings.

Common failure: Starting campaigns from a domain that was previously used for something else and already appears on one or more blacklists. Blacklisted domains have severely impaired delivery regardless of how perfect the DNS setup and warmup are.

Checklist item 7.7: Google Postmaster Tools connected

• Google Postmaster Tools account created at postmaster.google.com
• Each sending domain added and verified in Google Postmaster
• Domain reputation monitoring enabled

Verification: Sending domain shows in Google Postmaster Tools dashboard (reputation data will only populate after you start sending to Gmail addresses).

Common failure: Not setting up Postmaster Tools until after deliverability problems are discovered, at which point historical reputation data is unavailable and diagnosis is harder.

---

Master checklist summary

Section 1: Account

• 1.1 Account created and verified
• 1.2 Plan appropriate for inbox count

Section 2: DNS Configuration

• 2.1 Domains added to Inframail
• 2.2 SPF records added
• 2.3 DKIM records added (CNAME type)
• 2.4 DMARC records added
• 2.5 MX records configured (if receiving replies)

Section 3: DNS Verification

• 3.1 SPF propagation confirmed (MXToolbox)
• 3.2 DKIM propagation confirmed (MXToolbox)
• 3.3 DMARC propagation confirmed (MXToolbox)
• 3.4 Inframail in-dashboard verification passes

Section 4: Inbox Creation

• 4.1 Inboxes created on verified domains
• 4.2 SMTP credentials documented
• 4.3 Bulk SMTP export generated

Section 5: Instantly Connection

• 5.1 Inboxes connected to Instantly
• 5.2 IMAP confirmed working
• 5.3 Sending account settings configured

Section 6: Warmup

• 6.1 Warmup enabled for all inboxes
• 6.2 Warmup running minimum 14 days before campaigns
• 6.3 Warmup scores 80+ before campaign launch

Section 7: Pre-Campaign

• 7.1 Test email authentication passes (SPF/DKIM/DMARC all pass)
• 7.2 Bounce rate baseline test below 2%
• 7.3 Contact list verified
• 7.4 Campaign sequence settings reviewed
• 7.5 Reply handling configured
• 7.6 Domain blacklist status clean
• 7.7 Google Postmaster Tools connected

Total: 24 items. All 24 must be confirmed before the first campaign send.

---

Configuration reference

---

Advanced tactics

Tactic 1: Complete the checklist per-domain, not per-batch

It is tempting to complete all DNS configuration for all domains simultaneously, then verify all simultaneously. The risk is that DNS problems on one domain can be confused with problems on another domain. Work through the checklist domain by domain: add DNS for domain 1, verify domain 1, create inboxes on domain 1, then move to domain 2. This makes troubleshooting clearer when a step fails.

Tactic 2: Use a separate checklist instance for each domain

If you are setting up multiple domains, create a separate copy of the checklist for each domain. Name each copy with the domain name. This prevents the common error of marking a step "done" for the whole batch when it is only done for one domain.

Tactic 3: Set calendar reminders for warmup graduation dates

When you start warmup for a new inbox batch, immediately set a calendar reminder for 14 days later: "Warmup batch [name] eligible for campaigns. Verify warmup scores first." This prevents the scenario where inboxes complete warmup, get forgotten for weeks, and then get added to campaigns without a warmup score check.

Tactic 4: Re-run authentication checks quarterly

DNS records can be accidentally modified during other changes to your domain's DNS (adding a new service, SSL certificate renewals, registrar changes). Run MXToolbox SPF, DKIM, and DMARC checks for all active sending domains quarterly, not just at setup time. Catching a broken record before it causes campaign damage is much better than discovering it after open rates drop.

Tactic 5: Document the setup date for each inbox and domain

Record when each domain was added to Inframail and when each inbox was created. This historical record is invaluable when troubleshooting future problems: if an inbox starts having deliverability issues 90 days after creation, knowing the exact creation date, warmup start date, and campaign start date provides a timeline for diagnosis. Without documentation, this history is impossible to reconstruct.

---

Troubleshooting the checklist

Problem: DKIM verification failing after DNS records added

Symptoms: MXToolbox DKIM lookup for selector1 returns "DKIM record not found" or CNAME lookup fails.

Diagnosis steps:

1. Confirm the record was added as a CNAME (not TXT or A)
2. Confirm the host field is exactly selector1._domainkey (without the main domain appended, as some registrars auto-append the domain)
3. Check propagation time: CNAME records can take up to 60 minutes

Fix: Delete the existing record if incorrectly typed, re-add with correct type (CNAME) and host value, wait for propagation, and re-verify.

Problem: SPF record adding returns "multiple SPF records" error

Symptoms: MXToolbox SPF lookup shows a "Multiple SPF records found" error.

Diagnosis steps:

1. Check whether the domain already had an SPF record from a previous email provider
2. Only one SPF TXT record is allowed per domain; multiple records cause SPF lookup failure

Fix: Delete the old SPF record and keep only the Inframail/Microsoft 365 SPF record: v=spf1 include:spf.protection.outlook.com -all. If you need to include another provider, merge them into one record: v=spf1 include:spf.protection.outlook.com include:other.provider.com -all.

Problem: Warmup scores starting high then dropping

Symptoms: Warmup scores for new inboxes start above 80 in the first week, then drop to 60–70 in week 2–3.

Diagnosis steps:

1. Check IMAP connectivity: if IMAP fails, warmup reply detection stops working, reducing score
2. Check whether any campaign sends (not just warmup) started from these inboxes during the warmup period

Fix: Confirm IMAP is connected and functional. Ensure no campaign sends are happening from inboxes still in warmup. Extending warmup duration and pausing campaigns from affected inboxes.

Problem: Test email failing DKIM in headers despite DNS passing

Symptoms: MXToolbox DKIM DNS lookup passes, but the received email headers show DKIM: fail.

Diagnosis steps:

1. This indicates the Microsoft 365 mailbox is not yet associated with the DKIM selector despite the DNS record being correct
2. This can happen when inboxes are created before Microsoft propagates the DKIM key internally
3. There may be a delay between DNS record creation and Microsoft activating DKIM signing for new inboxes

Fix: Wait 24–48 hours and re-test. If the problem persists, contact Inframail support: they can manually trigger DKIM activation for the affected inboxes.

Problem: Instantly showing "authentication failed" for inboxes after bulk import

Symptoms: After bulk importing the Inframail SMTP CSV, several inboxes show authentication failures.

Diagnosis steps:

1. Check the specific credentials in the CSV for failed inboxes
2. Passwords containing special characters may not have exported cleanly in CSV format
3. Verify the SMTP server value is exactly smtp.office365.com and port is 587

Fix: Re-export SMTP credentials for failed inboxes individually from Inframail and re-enter them manually in Instantly.

---

What practitioners say

A verified user on Inframail reviews on G2:

"The checklist approach is the only thing that keeps setup from turning into chaos when you are setting up 10+ domains. I built my own checklist from mistakes in the first few setups: the first time, I forgot to verify DNS before creating inboxes. The second time, I forgot to enable warmup before the inboxes were added to campaigns. By the third batch, I had a checklist, and nothing got missed."

— Verified buyer on Inframail reviews on G2

A thread in r/coldemail (1,447 upvotes):

"The biggest thing I see people miss is the DKIM record type. Inframail/M365 uses CNAME-based DKIM, not TXT. If you add a TXT record, it looks fine in DNS but fails at send time. Check this specifically if you are having authentication failures and everything else seems right."

— r/coldemail, 1,447 upvotes

A reviewer on Instantly reviews on G2, where Instantly holds 4.9/5 from 2,800+ reviews:

"IMAP is the one that catches everyone. People connect Instantly to their Inframail inboxes, see the SMTP green checkmark, and think they are done. Then warmup scores stay low because the IMAP connection failed silently. Always verify the IMAP connection separately from SMTP."

— Verified buyer on Instantly reviews on G2

---

Our actual stack

---

Frequently asked questions

How long does the full Inframail setup take from start to campaign-ready?

The technical setup (account, DNS, inboxes, Instantly connection) takes 2–4 hours per 5-domain batch. Warmup requires a minimum 14 days (28–60 for full maturity) after the technical setup is complete. Total time from start to first campaign send: 14–60 days, primarily determined by warmup duration.

What is the most important step in the Inframail setup checklist?

DNS verification before inbox creation. Inboxes created before DNS is fully verified may not have proper DKIM signing active from the start. All authentication records — SPF, DKIM, and DMARC — should show as verified in both MXToolbox and the Inframail dashboard before any inboxes are created.

Can I run campaigns and warmup simultaneously from the same inboxes?

Yes, and you should. Warmup should run continuously throughout the active campaign period, not just during the initial warmup phase. Keeping warmup active while campaigns run maintains positive engagement signals that partially offset cold outreach signals.

How many inboxes should I set up on each domain?

3–5 inboxes per domain is the recommended range. More than 5 concentrates reputation risk: if one campaign from this domain triggers complaints, all inboxes on the domain are affected. Fewer than 3 makes the per-inbox cost of the domain higher. 4 inboxes per domain is a common balance.

What warmup score should I require before starting campaigns?

A warmup score of 80 or above is the minimum for assigning inboxes to campaigns. Scores between 70 and 80 should stay in warmup-only for an additional 1–2 weeks. Scores below 70 indicate a setup problem (often IMAP failure or DNS issue) that should be diagnosed and fixed before campaigns.

Do I need Google Postmaster Tools for every sending domain?

Yes. Google Postmaster provides the only publicly available view into how Gmail is evaluating your sending domains and IP addresses. Without Postmaster Tools data, you are flying blind on the 40–60% of cold email contacts who use Gmail. Setting it up costs nothing and provides irreplaceable data once you start sending.

What should I do if authentication fails on the first test email?

Check the email headers to identify which authentication check is failing (SPF, DKIM, or DMARC). If DKIM is failing despite the DNS CNAME record passing in MXToolbox, contact Inframail support — the internal DKIM key activation for the inbox may need to be triggered manually. Do not proceed to campaign sends until all three authentication checks pass.

How often should I re-run the checklist after initial setup?

Run the authentication portions of the checklist (Section 3 items 3.1–3.3 and Section 7 item 7.1) quarterly. DNS records can be accidentally modified during other domain changes. Run the blacklist check (Section 7 item 7.6) monthly. Run warmup score reviews (Section 6 item 6.3) weekly.

What if I skip warmup and just start campaigns immediately?

Short-term: your open rates will be lower because inbox placement rates are worse for un-warmed inboxes. Medium-term: if the un-warmed inboxes receive complaint signals before building reputation, the domain reputation can be damaged quickly. Long-term: domains that get blacklisted from rapid campaign sends without warmup are difficult and time-consuming to rehabilitate. The warmup period is the most important operational protection for your infrastructure investment.

Can I use the same Inframail inboxes for multiple campaigns simultaneously?

Yes, but manage the combined daily send volume carefully. If an inbox is assigned to two campaigns and both are sending aggressively, the combined sends per day can exceed the safe limit. Ensure the total sends from all campaigns assigned to a given inbox stays within the per-inbox daily limit (20–30 for new inboxes, 40–50 for mature inboxes).

---

Start your outreach with verified contacts

A correctly configured Inframail and Instantly infrastructure is only as good as the contact data flowing into it. High bounce rates from unverified contacts damage the reputation of newly established inboxes faster than any other variable.

Quarvio delivers pre-verified B2B contacts with a 90% deliverability guarantee. Pricing: $129 for 5,000 contacts, $199 for 10,000, $399 for 25,000, $699 for 50,000. Unused credits roll forward for 12 months.

Start your contact order at Quarvio →