Order queue open · Verified lists delivered within 24–48 hours
How to connect Inframail to Instantly in 2026: SMTP connection type, bulk CSV setup, warmup handoff, rotation configuration, and complete troubleshooting for every common error.
Ryan Mercer
SDR turned cold email consultant, 8 years outbound · Updated June 24, 2026
Last updated: June 2026 · Ryan Mercer, SDR turned cold email consultant, 8 years outbound
TL;DR — 5 things to know before reading
Inframail and Instantly are designed to work together, and the integration is genuinely straightforward when you know the key distinction: Inframail inboxes authenticate as Microsoft 365 in Instantly, not as generic SMTP. Get that one setting wrong and no number of password retries will fix it.
After connecting hundreds of inboxes across clients over eight years of outbound work, the pattern is consistent: the 30-minute setup estimate only holds if you follow the Microsoft 365 connection type, verify DNS before connecting, and resist the urge to start sending before warmup completes. Every shortcut in this process costs weeks of recovery time. DNS misconfiguration caught at setup costs 5 minutes; DNS misconfiguration discovered after 3 weeks of sending costs 3 weeks of warmup restart.
This guide covers the complete integration from first inbox to first campaign: architecture planning, DNS verification, bulk connection, warmup configuration, campaign rotation setup, and every troubleshooting scenario you are likely to encounter. Quarvio provides the verified contact lists that protect the inbox reputation you are about to build. Aimfox handles LinkedIn outreach as a parallel channel from the same contact data.
Inframail provisions Microsoft 365 inboxes on custom domains you control. Each inbox gets a unique email address backed by a Microsoft 365 account with a dedicated sending IP in the Inframail pool.
Inframail's value for cold email infrastructure is threefold: it handles DNS authentication automatically for every provisioned domain (SPF, DKIM, DMARC), it provides Microsoft 365 sending infrastructure that passes Outlook's authentication checks more reliably than standard SMTP, and it allows you to provision inboxes at scale without managing individual Microsoft 365 accounts.
Instantly is the campaign platform that manages sequences, warmup, rotation, analytics, and deliverability testing. Instantly connects to Inframail inboxes via Microsoft 365 API authentication — not SMTP port 587 credentials despite the fact that Inframail provides SMTP credentials in its export CSV.
Understanding this architecture matters because it explains why the connection type selection is so critical: if you connect using SMTP, Instantly uses a different authentication pathway that does not correctly handle the Inframail Microsoft 365 account credentials, resulting in authentication failed errors that look identical to incorrect password errors.
Before beginning the connection process, confirm these prerequisites are in place:
Provisioning inboxes without a clear architecture plan leads to operational problems: too many inboxes per domain, inconsistent naming conventions, uneven rotation, and difficulty diagnosing problems when they occur. Plan first.
Sub-step 1.1: Calculate how many sending inboxes you need based on your target daily send volume.
Use the inbox sizing guide from Woodpecker's daily sending limits research:
| Daily email target | Inboxes needed |
|---|---|
| 90–150 emails/day | 3–5 inboxes |
| 300–500 emails/day | 10–15 inboxes |
| 500+ emails/day | 15–20+ inboxes |
These estimates assume 30–50 emails per inbox per day for a well-warmed inbox. For the first 30 days after warmup, use the lower end (25–35 per inbox) to avoid overloading new infrastructure.
Sub-step 1.2: Plan your domain structure.
The rule is 2–3 inboxes per domain maximum. More than 3 inboxes on a single domain creates a single point of failure: if the domain's reputation degrades or it appears on a blacklist, all inboxes on that domain are affected simultaneously.
For 10 inboxes, provision 4 domains with 2–3 inboxes each rather than 2 domains with 5 inboxes each. The additional domains cost pennies per month and provide critical redundancy.
Sub-step 1.3: Plan your inbox naming convention.
Use consistent naming that makes rotation management and troubleshooting easier. Common pattern: firstname@yourdomain.com (a real or fictional sender name) rather than inbox1@yourdomain.com. Numbered inboxes look like automated infrastructure to spam filters and to prospects who may notice the sending address.
Sub-step 1.4: Decide which inboxes will be assigned to which campaigns.
Inboxes should be campaign-specific or at minimum ICP-specific. Mixing inbox assignments across unrelated campaigns makes it impossible to diagnose whether a deliverability problem is caused by a specific inbox, a specific campaign, or a specific audience.
Benchmark: Architecture planning takes 30 minutes and results in a spreadsheet listing each domain, each inbox per domain, which campaign each inbox belongs to, and provisioning dates.
Failure mode: Provisioning all inboxes on one or two domains to save on domain registration costs. A single-domain infrastructure creates a single point of failure. When the domain's reputation degrades, every campaign running on those inboxes degrades simultaneously.
Sub-step 2.1: Log in to your Inframail dashboard and navigate to the domain provisioning section.
Sub-step 2.2: Add each domain you will use for outreach.
If the domain is newly registered, it will be provisioned in Inframail and connected to Inframail's Microsoft 365 infrastructure. Inframail creates the DNS records for SPF, DKIM, and DMARC automatically for each provisioned domain.
Sub-step 2.3: Verify each domain shows as active in the Inframail dashboard before proceeding.
Domain provisioning takes 15–30 minutes for DNS records to propagate and for Inframail's system to confirm the domain is correctly configured. Do not proceed to inbox provisioning until each domain shows as active.
Benchmark: Domain provisioning completes within 30 minutes per domain. A batch of 4 domains should be fully active within 1 hour.
Failure mode: Proceeding to inbox provisioning before the domain is marked as active. Inboxes provisioned on an incompletely configured domain may not inherit correct DNS authentication.
Sub-step 3.1: For each domain, provision 2–3 inboxes.
In the Inframail inbox provisioning interface, select the domain, enter the email address (e.g., ryan@yourdomain.com), and complete provisioning.
Sub-step 3.2: Confirm each inbox shows a green active or provisioned status in the Inframail dashboard.
New inboxes typically take 5–15 minutes to provision fully. A yellow or pending status means provisioning is still in progress.
Sub-step 3.3: Note the provisioning date for each inbox.
The provisioning date is the starting point for the warmup timer. Inboxes provisioned today begin warmup today; they should not send cold emails until at least 14–21 days from this date and until warmup score reaches 80+.
Benchmark: All inboxes showing active status within 30 minutes of provisioning.
Failure mode: Provisioning 5+ inboxes on the same domain. The 2–3 inbox per domain limit is a safety rule, not a suggestion. Violating it concentrates risk: one domain reputation event affects all inboxes simultaneously.
This step is the most commonly skipped and the source of the most troubleshooting time lost.
Sub-step 4.1: In the Inframail dashboard, navigate to domain settings for each provisioned domain.
Confirm that SPF, DKIM, and DMARC records show as active and correctly configured. Inframail's dashboard displays a status indicator for each record per domain.
Sub-step 4.2: Verify DNS records are externally resolving.
Even if Inframail shows the records as configured, external DNS propagation takes up to 24 hours after domain provisioning. Use an external DNS lookup tool to verify: the SPF record returns the correct value, the DKIM key is resolving at the selector subdomain, and the DMARC policy is present at _dmarc.yourdomain.com.
The Mailgun SPF, DKIM, and DMARC setup guide explains what each correctly configured record should look like. Use it as a reference to confirm Inframail's auto-configured records are in the expected format.
Sub-step 4.3: For any record showing as not resolving externally, wait 24 hours from provisioning and recheck.
DNS propagation timing varies by domain registrar. If records are still not resolving 24 hours after provisioning, contact Inframail support before proceeding to inbox connection.
Benchmark: All three authentication records (SPF, DKIM, DMARC) resolving correctly externally before connecting to Instantly.
Failure mode: Skipping DNS verification because Inframail shows the records as configured. Inframail's dashboard reflects what Inframail has attempted to configure, not necessarily what has propagated to external DNS resolvers. This step takes 5 minutes and prevents hours of troubleshooting later.
Sub-step 5.1: Navigate to the credentials export section in the Inframail dashboard.
Look for Export, Download CSV, or Get credentials in the inbox management section.
Sub-step 5.2: Download the CSV file containing your inbox credentials.
The CSV contains one row per inbox with these fields: email address, password, SMTP server, SMTP port, IMAP server, and IMAP port. Each inbox has unique credentials assigned during provisioning. These SMTP and IMAP details are provided for reference and for other email clients; in Instantly, the Microsoft 365 connection type handles authentication without requiring you to enter these values manually.
Sub-step 5.3: Open the CSV and verify its contents match your provisioned inboxes.
Confirm the row count matches the number of inboxes you provisioned. Verify the email addresses listed are correct. Do not proceed if the CSV has fewer rows than your provisioned inbox count — re-export or contact Inframail support.
Sub-step 5.4: Store the credentials file securely.
The credentials CSV contains login credentials for every inbox. Store it in a location only you can access. Do not share it via public cloud links or unsecured email.
Benchmark: CSV export available immediately after inboxes show active status. Export completes in under 30 seconds.
Failure mode: Using an old cached CSV from a previous export. If you re-provisioned inboxes or had credentials reset, the old CSV contains outdated passwords. Always export fresh credentials immediately before connecting.
Sub-step 6.1: Log in to Instantly and navigate to Email Accounts.
Sub-step 6.2: Click Add Account and select the bulk import option.
Instantly supports connecting multiple inboxes simultaneously via CSV upload — far more efficient than connecting accounts one at a time when setting up 5+ inboxes.
Sub-step 6.3: CRITICAL — Set the connection type to Microsoft 365.
This is the most important selection in the entire setup. Even though Inframail provides SMTP server and port details in the credentials CSV, Inframail inboxes must be connected as Microsoft 365 accounts in Instantly.
The reason: Inframail's Microsoft 365 infrastructure uses OAuth-style authentication internally. When Instantly connects via SMTP, it uses a different authentication pathway that does not work with Inframail's account configuration. The Microsoft 365 connection type in Instantly maps to the correct authentication method for Inframail.
Sub-step 6.4: Upload the credentials CSV from Inframail.
Follow Instantly's CSV format requirements for bulk account import. Instantly reads the email address and password columns from the Inframail CSV. If Instantly requires a specific column order or naming convention, copy the relevant values into Instantly's template before uploading.
Sub-step 6.5: Confirm the import by checking the account count in Instantly's Email Accounts view.
After upload, all connected inboxes appear in the account list. Initial connection status may show as connecting for 1–3 minutes before changing to connected.
Benchmark: All inboxes showing connected status within 5 minutes of CSV upload.
Failure mode: Using the SMTP connection type because the CSV contains SMTP server details. This produces authentication failures on every inbox. If this happens, delete all incorrectly-typed connections and redo the import with Microsoft 365 type selected.
Sub-step 7.1: In Instantly's Email Accounts section, review the status indicator for each newly connected inbox.
Green indicator: inbox is connected and operational. Yellow or orange indicator: connected but with warnings — investigate immediately. Red indicator: connection failed — see troubleshooting section.
Sub-step 7.2: For each inbox, use Instantly's test email function or send a manual test to yourself.
Confirm the test email arrives in the destination inbox, not spam. This is the first real-world placement test for each inbox.
Sub-step 7.3: If your email client supports header inspection, check that the test email shows DKIM=pass and SPF=pass.
Gmail's Show original or Outlook's View message source displays the authentication results header. DKIM=pass and SPF=pass confirms Inframail's DNS configuration is working end-to-end.
Sub-step 7.4: Log any connection issues with the specific inbox email address and error message.
A troubleshooting log that tracks which inboxes showed issues, what the error message was, and what fix was applied is invaluable for diagnosing pattern issues (e.g., all inboxes from one specific domain failing while others succeed).
Benchmark: All inboxes show green connection status and test emails arrive in primary inbox within 5 minutes of sending.
Failure mode: Skipping the verification step and assuming all connections are healthy because the CSV upload completed without an error. CSV upload errors and per-inbox connection errors are different events — the CSV may upload successfully while individual inboxes fail to connect.
Sub-step 8.1: In Instantly's Email Accounts view, select each newly connected inbox and enable warmup.
Warmup must be explicitly enabled per inbox. Connecting an inbox does not automatically start warmup.
Sub-step 8.2: Set the warmup ramp rate to Instantly's default.
Warmup begins sending small volumes of emails to a network of monitored addresses and generates positive engagement signals (opens and replies). The default ramp rate starts at 3–5 emails per day and increases by 2–3 per day over the warmup period.
Do not override the ramp with a higher starting volume. The gradual ramp builds a believable sending history — an inbox that jumps from 0 to 50 sends on day 1 looks suspicious to email providers' machine learning systems.
Sub-step 8.3: Monitor warmup score weekly.
Navigate to each inbox in Instantly's Email Accounts view and review the warmup score. The score is updated regularly based on delivery and engagement data from warmup sends.
Sub-step 8.4: Set a calendar reminder for the warmup completion date.
Calculate 21 days from the inbox connection date and set a reminder to check warmup scores at that point. This prevents inboxes from sitting in warmup indefinitely while also preventing premature campaign activation.
Sub-step 8.5: Do not assign warming inboxes to active cold campaigns.
An inbox in warmup should be in the warmup pool only. Adding a warming inbox to an active cold campaign before score reaches 80+ will:
Benchmark: Warmup score reaches 80+ within 14–21 days for properly provisioned Inframail inboxes on properly authenticated domains. Per Woodpecker's email warmup guide, domains with correct SPF, DKIM, and DMARC consistently warm faster than domains with missing records.
Failure mode: Misinterpreting warmup score of 80 as a guarantee of good inbox placement. The warmup score is Instantly's proprietary engagement score, not a direct measure of inbox placement. A score of 80+ indicates the warmup process is healthy; always run a placement test before the first campaign to confirm real-world placement.
Sub-step 9.1: Navigate to your campaign in Instantly and go to the sending accounts section.
Sub-step 9.2: Add all fully warmed inboxes (score 80+) from your Inframail batch to the campaign.
Instantly automatically rotates sends across connected inboxes. Adding multiple inboxes distributes the send volume and prevents any single inbox from handling all sends on a given day.
Sub-step 9.3: Set per-inbox daily sending limits.
| Inbox warmup age | Recommended daily limit |
|---|---|
| 14–30 days (newly warmed) | 25–35 emails/day |
| 30–60 days | 35–45 emails/day |
| 60+ days | 40–50 emails/day |
Source: Woodpecker daily sending limits guide — verified June 2026
Sub-step 9.4: Confirm rotation is distributing sends evenly.
After the campaign runs for 2–3 days, check per-inbox send count in Instantly's analytics. Rotation should be roughly even across all connected inboxes. If one inbox is handling significantly more volume than others, check whether that inbox has a higher per-inbox limit set or whether other inboxes have connection issues suppressing their send capacity.
Sub-step 9.5: Assign inbox batches to campaigns exclusively.
If you have two separate campaigns and two batches of inboxes, assign each batch exclusively to one campaign. Cross-assigning inboxes across campaigns makes it impossible to diagnose which campaign caused a deliverability problem.
Benchmark: After 7 days of campaign runs, all connected inboxes should be within 20% of each other on total send count, indicating even rotation.
Failure mode: Adding all inboxes to the campaign but leaving the daily limit at Instantly's default, which may be higher than the recommended limit for newly warmed inboxes. Setting per-inbox limits manually is required — defaults are not optimized for inbox warmup age.
| Configuration | Correct value | Notes |
|---|---|---|
| Connection type in Instantly | Microsoft 365 | Never SMTP for Inframail inboxes |
| Authentication | Email + password from Inframail CSV | Via Microsoft 365 connection type |
| SPF record | Auto-configured by Inframail | Verify external resolution before connecting |
| DKIM record | Auto-configured by Inframail | Verify external resolution before connecting |
| DMARC record | Auto-configured by Inframail | Verify external resolution before connecting |
| Inboxes per domain | 2–3 maximum | More = single point of failure risk |
| Min warmup before cold sends | 14–21 days | Target score 80+ before any cold sends |
| Warmup target score | 80+ | Below 80: continue warming, do not launch |
| Daily limit (14–30 days) | 25–35 emails/inbox/day | Start at lower end for first week of sends |
| Daily limit (30–60 days) | 35–45 emails/inbox/day | Increase incrementally |
| Daily limit (60+ days) | 40–50 emails/inbox/day | For inboxes with 60+ days clean sending history |
| Campaign inboxes | Dedicated per campaign | Do not cross-assign across campaigns |
| Inbox provisioning per domain | 2–3 inboxes | Scale per inbox sizing table |
Rather than concentrating all inboxes for a campaign on 2–3 domains, spread them across 4–6 domains with 2 inboxes per domain. This creates inbox-level redundancy: if Domain A develops a reputation issue, the campaign continues from Domains B through F while Domain A is investigated and recovered. Recovery time for a single domain is 2–4 weeks; with 5 other domains running, the campaign never stops.
Check warmup scores weekly for all connected inboxes. A declining warmup score (80 → 75 → 68 over 3 weeks) is an early warning of reputation degradation, often caused by increasing bounce rates from aging contact lists. Catching this trend at 75 is far easier to reverse than catching it at 50.
When launching a new campaign with a freshly warmed batch of Inframail inboxes, activate 30% of inboxes in week 1, 60% in week 2, and 100% in week 3. This staged approach lets you identify any placement or deliverability problems early with a smaller volume before committing the entire inbox batch to live sends.
Inframail inboxes are not permanent. An inbox that has experienced elevated bounce rates, spam complaints, or a blacklisting event should be retired from campaigns even after delisting. The reputation damage remains in email providers' long-term sender history. Retire the inbox from campaigns, continue warmup-only sends for 4 weeks, and run a placement test. If placement is still below 80%, retire the inbox permanently and provision a replacement.
Use different Inframail inbox batches for different campaign types. Cold outreach inboxes should never be mixed with warm follow-up inboxes in rotation. Cold outreach generates higher bounce rates than warm follow-up, and mixing them on the same inboxes means cold-outreach-generated bounces damage the reputation of inboxes that would otherwise maintain excellent deliverability for warm contacts.
Before assigning any Inframail inbox batch to its first campaign, run a placement test in Instantly using the campaign's actual step-1 email copy and subject line. This confirms both the infrastructure (DNS authentication) and the content are clean before spending the first day's campaign budget on the live audience. See the inbox placement test guide for the full workflow.
Deliverability degradation mid-campaign shows up as a declining open rate trend (week 1 at 40%, week 2 at 30%, week 3 at 18%), a warmup score drop, or a sudden bounce rate spike.
When this happens, work through these checks in order:
Step 1: Check bounce rate in Instantly campaign analytics. If bounce rate exceeds 3%, contact list quality is degrading inbox reputation. Replace the list with Quarvio verified contacts or re-verify existing leads before continuing.
Step 2: Check warmup score for all campaign inboxes. A warmup score that has dropped from 80+ to below 70 indicates reputation degradation in progress. Reduce the per-inbox daily sending limit immediately by 50% and monitor for stabilization.
Step 3: Run an inbox placement test in Instantly. If placement has dropped below 80%, pause the campaign and begin root cause diagnosis.
Step 4: Check the sending domain on MXToolbox blacklist checker. A new blacklist listing that appeared since the campaign started is a clear cause of sudden placement degradation.
Step 5: Check Google Postmaster Tools for the sending domain. A spike in spam complaint rate at Gmail typically shows up in Postmaster 24–48 hours before it appears as an open rate decline in Instantly analytics. Catching it in Postmaster first allows faster response.
Symptom: After uploading the Inframail credentials CSV to Instantly, all inboxes immediately show authentication failure.
Cause: Wrong connection type selected. This is the most common setup error in this integration.
Fix: Delete all failed connections from Instantly's Email Accounts. Return to the bulk import, confirm that Microsoft 365 is selected as the connection type (not SMTP, not Gmail, not other SMTP), and re-upload the credentials CSV. Do not change any credentials — the passwords are correct; the connection type was wrong.
Symptom: After bulk import with Microsoft 365 type, 8 out of 10 inboxes connect successfully but 2 show connection errors.
Cause: The 2 failing inboxes may not have completed provisioning fully in Inframail's system. Provisioning occasionally takes longer for some inboxes than others, particularly in large batches.
Fix: Check the Inframail dashboard for the 2 failing inboxes. If they show pending or a status other than active, wait 30 minutes and attempt reconnection. If they show active in Inframail but still fail in Instantly, export a fresh credentials CSV from Inframail and reconnect those 2 inboxes individually rather than in bulk.
Symptom: Two weeks after enabling warmup on newly connected Inframail inboxes, warmup scores are still below 40.
Cause: If the warmup emails from these inboxes are landing in spam (which happens when DNS authentication is misconfigured), the warmup network's engagement is suppressed and no positive score signals accumulate.
Fix: Run an inbox placement test in Instantly to confirm whether warmup emails are reaching the primary inbox. If they are routing to spam, check DNS authentication records for the inbox's domain. Re-verify in the Inframail dashboard that all three records (SPF, DKIM, DMARC) are active and resolving externally. A misconfigured DMARC record is a common cause of suppressed warmup scores.
Symptom: Warmup score for campaign inboxes drops from 82 to 65 within 7 days of starting cold sends.
Cause: Cold sends are generating negative signals — bounces, spam complaints, or low engagement — that counteract the positive warmup signals. This typically means the daily send volume is too high for the inbox's current capacity, or contact list quality issues are causing elevated bounce rates.
Fix: Reduce daily cold send limits on affected inboxes by 50% immediately. Check bounce rate in campaign analytics — if above 3%, pause sends and replace contact lists with Quarvio verified contacts. Allow the warmup process 1–2 weeks of reduced-volume sends to recover score before gradually increasing volume again.
Symptom: All inboxes show connected status in Instantly, but campaign analytics show bounce rates of 8–12%.
Cause: High bounce rates are almost always a contact list quality problem, not a connection or infrastructure problem. Unverified contact lists with old or invalid email addresses produce bounce rates this high.
Fix: Pause the campaign. Review the bounce breakdown in Instantly analytics — look at the specific bouncing addresses. If they show patterns (unusual domains, generic mailbox names, or synthetically-generated looking email addresses), the list quality is the issue. Order a verified replacement list from Quarvio before resuming.
Symptom: During bulk import, Instantly reports a timeout error for some or all inboxes rather than an authentication error.
Cause: Timeout errors during connection typically indicate a temporary infrastructure connectivity issue between Instantly's servers and Inframail's Microsoft 365 infrastructure.
Fix: Wait 15–30 minutes and retry the connection. Timeout errors are usually transient and resolve without configuration changes. If timeout errors persist for more than 1 hour, check Inframail's status page or contact Inframail support to confirm their infrastructure is operational.
Symptom: After completing Inframail provisioning and checking external DNS resolution, SPF or DKIM shows as not resolving, even though Inframail's dashboard shows them as configured.
Cause: DNS propagation is incomplete. Changes to DNS records take 1–48 hours to propagate globally, depending on TTL settings and caching at various DNS resolver levels.
Fix: Wait 24 hours from the time the domain was provisioned in Inframail before concluding the records are missing. After 24 hours, run DNS lookup again. If records are still not resolving after 24 hours, contact Inframail support with the specific domain and DNS lookup results showing the missing records. Do not connect inboxes in Instantly until all three authentication records are externally resolving.
Symptom: Inbox warmup scores are at 85+, but after 2 weeks of cold sends, open rates are stuck at 12–15%.
Cause: Good warmup score does not guarantee good inbox placement for cold sends. Warmup builds warmup-network engagement signals; cold send placement is also affected by the campaign email's content scoring, the domain's reputation with the specific providers the prospects use, and whether the campaign's ICP is concentrated at providers with stricter filtering.
Fix: Run a placement test in Instantly using the campaign's exact step-1 content. If placement shows below 80%, identify and fix the placement issue. If placement shows above 80% but open rates are still low, the problem may be corporate email security filtering at the prospect company level — a type of filtering that placement seed networks do not fully replicate.
"Set up 10 Inframail inboxes in Instantly in about 30 minutes. Within 3 weeks of warmup, we were getting 38% open rates. The Microsoft 365 connection type is key — took me two attempts before I figured that out."
— Verified G2 reviewer, cold email consultant, Instantly reviews on G2
"The DNS configuration being automatic in Inframail is the critical feature. I have seen practitioners spend an entire afternoon on SPF and DKIM records for manual SMTP setups, only to have it misconfigured anyway. Inframail handles this in the background — eliminates the afternoon troubleshooting sessions entirely."
— Verified G2 reviewer, outbound sales lead, Inframail reviews on G2
Per Instantly's cold email benchmark report, campaigns using properly authenticated inboxes with warmup scores above 80 achieve average open rates 2.3x higher than campaigns using inboxes with lower warmup scores or missing authentication records.
| Need | Tool | Notes |
|---|---|---|
| Verified B2B contacts | Quarvio | Protects inbox reputation with clean lists |
| Email inboxes | Inframail | Microsoft 365, auto DNS, scalable |
| Cold email platform | Instantly | Sequences, warmup, analytics, rotation |
| LinkedIn outreach | Aimfox | Parallel LinkedIn channel from same contacts |
| Blacklist monitoring | MXToolbox | Domain and IP blacklist checks |
| Gmail reputation | Google Postmaster Tools | Spam complaint rate monitoring |
How do I connect Inframail to Instantly?
Log in to Instantly and navigate to Email Accounts. Click Add Account and choose bulk import. Select Microsoft 365 as the connection type — this is the critical selection, not SMTP. Upload the credentials CSV exported from your Inframail dashboard. Wait 2–3 minutes for connections to establish. Verify each inbox shows a green connected status. Then enable warmup for each inbox and wait 14–21 days before adding any inbox to a cold campaign.
What is the correct connection type for Inframail inboxes in Instantly?
Microsoft 365. Even though Inframail provides SMTP server and port details in its credentials CSV, Inframail inboxes must be connected as Microsoft 365 accounts in Instantly — not as SMTP. Using the SMTP connection type produces authentication failed errors that look identical to incorrect password errors, which causes many practitioners to waste time re-entering correct credentials that are not the problem.
How many Inframail inboxes can I connect to Instantly?
There is no hard limit from Instantly on the number of inboxes you can connect (depends on your plan tier). The practical limit is determined by your sending volume goals and Inframail inbox costs. Use the inbox sizing guide: 3–5 inboxes for 90–150 emails per day, 10–15 for 300–500, and 15–20+ for above 500. Always maintain 2–3 inboxes per domain maximum regardless of total inbox count.
How long does it take to set up Inframail inboxes in Instantly?
The technical connection — from credentials CSV export to connected inboxes in Instantly — takes 20–40 minutes for a batch of 10 inboxes. However, inboxes are not ready for cold email until 14–21 days of warmup are complete. The full timeline from first provisioning to first campaign send is typically 3–4 weeks.
Why is Instantly saying "authentication failed" for my Inframail inbox?
In 90% of cases, the cause is using the SMTP connection type instead of Microsoft 365. Delete the failed connection, return to the bulk import or individual account add flow, select Microsoft 365, and re-enter the same credentials from the Inframail CSV. If you are certain Microsoft 365 is selected and authentication still fails, re-export fresh credentials from Inframail and try again.
Do I need to configure SMTP settings manually for Inframail in Instantly?
No. When connecting via the Microsoft 365 connection type, Instantly handles authentication without requiring manual SMTP or IMAP server configuration. The SMTP and IMAP server details in the Inframail credentials CSV are for reference and for use with other email clients, but are not entered manually in Instantly's Microsoft 365 connection flow.
How many emails per day can I send from each Inframail inbox in Instantly?
25–35 emails per day for newly warmed inboxes (14–30 days of warmup history). 35–45 for inboxes with 30–60 days of clean sending history. 40–50 for inboxes with 60+ days of consistent, low-bounce-rate sending. Per Woodpecker's daily sending limits research, exceeding 50 emails per inbox per day significantly increases the risk of triggering email provider volume flags, even on well-warmed inboxes.
How long does warmup take for Inframail inboxes in Instantly?
14–21 days is the minimum for correctly provisioned Inframail inboxes with all three DNS authentication records active. Per Woodpecker's email warmup guide, inboxes on domains with correct SPF, DKIM, and DMARC warm faster than inboxes with missing records, because authentication is a prerequisite for positive reputation signals.
Can I add Inframail inboxes to multiple campaigns in Instantly?
Technically yes, but not recommended. Assigning a single inbox to multiple campaigns makes it impossible to attribute a deliverability problem to a specific campaign's content or contact list. For clean operations, assign each inbox batch exclusively to one campaign. If you need to run 3 campaigns simultaneously, provision 3 separate inbox batches.
What warmup score should I aim for before sending cold campaigns from Inframail inboxes?
80 or above in Instantly's warmup score. However, always supplement the warmup score check with a placement test in Instantly's deliverability test feature before the first campaign launch. The warmup score and the placement test measure different things, and both should pass before sending.
Why is my Inframail inbox connected but not sending in my campaign?
The most common causes: (1) the inbox is connected but warmup is not enabled — warmup and campaign sending are both required for active inboxes; (2) the per-inbox daily limit is set to zero or very low; (3) the inbox was added to the campaign but the campaign is paused or in draft status; (4) the inbox has a connection warning (yellow status) that is preventing sends even though it appears connected. Check each of these in order.
How do I check if Inframail's DNS records are correctly configured?
In the Inframail dashboard, navigate to domain settings for the relevant domain and review the DNS status display. Inframail shows a status indicator per record type. For external verification, use a DNS lookup tool to query the domain's SPF record (type TXT), DKIM record (type TXT at the DKIM selector subdomain), and DMARC record (type TXT at _dmarc.yourdomain.com). The Mailgun authentication guide explains what correctly configured values should look like.
Infrastructure ready — now fill your Inframail inboxes with verified contacts
Inframail + Instantly gives you the infrastructure. Quarvio gives you the contacts. Verified B2B contact lists with phone-verified emails keep your bounce rate below 2% and protect the inbox reputation you spent 3 weeks building. One-time purchase, credits valid 12 months, unused contacts refunded as credits. No subscription.
