Order queue open · Verified lists delivered within 24–48 hours
What SMTP is in cold email: the protocol explained simply, how SMTP servers differ from dedicated inboxes, and why the inbox provider matters more than the protocol.
Priya Nair
B2B growth marketer, ex-Apollo user · Updated June 23, 2026
Last updated: August 2026 · Priya Nair, B2B growth marketer, ex-Apollo user
TL;DR — 5 things to know before reading
SMTP appears in cold email discussions in ways that range from technically accurate to misleading. "SMTP server" sometimes means a raw bulk mail server, sometimes an inbox provider's sending infrastructure, and sometimes a feature in a sending tool. The confusion matters because these are different things with very different implications for cold email deliverability.
The protocol itself — SMTP — is not a product choice. It is the universal standard that all email uses. The relevant choice for cold email is what infrastructure sits behind the SMTP connection: which IP addresses are sending the email, what reputation those IPs carry, and what inbox and domain reputation has been built through warmup and authentication.
This guide explains what SMTP is in simple terms, how it fits into cold email infrastructure, and why the practical choice for most B2B cold email senders is dedicated inbox provisioning rather than direct SMTP service access.
SMTP stands for Simple Mail Transfer Protocol. It is the standard communication protocol for sending email between mail servers. Every email — from a transactional receipt to a marketing newsletter to a cold outreach email — is transmitted using SMTP.
When you send an email from any inbox (Gmail, Outlook, or a custom domain inbox), your email client connects to your mail server using SMTP and hands off the email. The mail server then uses SMTP to deliver the email to the recipient's mail server, which delivers it to the recipient's inbox.
SMTP is infrastructure-layer technology: it is a standard, not a product. There is no choice between "using SMTP" and "not using SMTP" for cold email — all email uses SMTP. The relevant choice is which service provides and manages the SMTP infrastructure.
What SMTP is not:
A cold email infrastructure stack has four components (covered in detail in the cold email infrastructure guide):
SMTP is the protocol that the sending platform uses to connect to the inboxes and send email. When Instantly connects to a Microsoft 365 inbox provisioned via Inframail, it connects via IMAP (to read email, monitor replies, detect bounces) and SMTP (to send email sequences). The sender does not configure the SMTP protocol directly — Instantly and Inframail handle the connection.
The inbox provider — not the SMTP protocol itself — is what determines deliverability. Microsoft 365 inboxes send from Microsoft's IP infrastructure, which carries established reputation with all major mailbox providers. A generic bulk SMTP service sends from its own IP pool, which may or may not carry equivalent reputation, requires its own warmup, and requires the sender to manage IP reputation directly.
Provision individual email inboxes on a custom sending domain through a provider like Inframail. Each inbox is a full email account (username@sendingdomain.com) with its own SMTP and IMAP access, sending reputation, and warmup history.
The inbox provider's SMTP infrastructure is used to send email. Authentication (SPF, DKIM, DMARC) is configured per domain. The sending platform (Instantly) connects to each inbox via standard SMTP/IMAP and handles sequence sending, inbox rotation, and warmup.
Why this is the right approach for B2B cold email:
Bulk SMTP services like Mailgun and SendGrid are designed for high-volume transactional email: receipts, notifications, password resets. They provide SMTP relay service where the sender's emails are delivered through the service's IP infrastructure.
These services are powerful tools for the use case they are designed for. They are not well-suited to B2B cold email because:
Volume thresholds: Mailgun and SendGrid impose per-day sending limits tied to the pricing plan. Getting above those limits requires plan upgrades proportional to volume.
Shared IP risk: Bulk SMTP services use shared IP pools across many customers. A customer on the same shared IP who sends spam can affect deliverability for other customers — the same risk exists with any shared IP, but bulk SMTP services have less active monitoring incentive than Microsoft's enterprise business.
Cold email policy: Many bulk SMTP providers explicitly prohibit cold email or require opt-in lists in their terms of service. Violations can result in account suspension.
No inbox reputation: Bulk SMTP services do not build individual inbox reputation through warmup. Each send goes out from the shared IP pool without the per-inbox reputation history that dedicated inbox warmup creates.
Self-hosting an SMTP server (Postfix, Exim, or similar) gives maximum technical control but requires server administration, IP management, and active blacklist monitoring for the server's IP addresses. This approach is appropriate for large-scale email operations with dedicated technical teams. For B2B cold email at 1,000–100,000 contacts per month, the operational overhead is not justified by the control advantage.
Cold email senders using Instantly encounter both protocols:
| Protocol | Function | Used for |
|---|---|---|
| SMTP | Outgoing email delivery | Sending sequences, replies |
| IMAP | Incoming email access | Detecting replies, tracking bounces, warmup receives |
When connecting an Inframail inbox to Instantly, both SMTP (outgoing) and IMAP (incoming) credentials are used. Instantly needs IMAP access to detect when a prospect replies (to pause the sequence) and to participate in warmup network email exchanges (to generate positive engagement signals by opening and replying to warmup emails).
Some cold email tools advertise "custom SMTP" as a feature. This means the tool allows you to connect any SMTP-compatible email account rather than requiring you to use the tool's own built-in email service.
Instantly supports custom SMTP connections: connect Microsoft 365 inboxes provisioned via Inframail, Google Workspace inboxes, or any other SMTP-compatible inbox. The "custom SMTP" feature is what enables Instantly to manage sequences from inboxes hosted on the sender's own domains rather than from Instantly's own email addresses.
This is the correct architecture for cold email: the sender controls the inbox, the domain, the reputation, and the warmup history. The cold email tool (Instantly) manages the sequence logic and connects to the sender's inboxes via standard SMTP.
SPF, DKIM, and DMARC records (per the Mailgun SPF, DKIM, and DMARC guide) authenticate the SMTP connection at the domain level. When an email is sent via SMTP from a Microsoft 365 inbox:
Authentication operates at the domain DNS level and does not change the SMTP protocol. Both authenticated and unauthenticated email uses the same SMTP protocol — authentication adds verification layers on top of the delivery mechanism.
Inframail configures SPF, DKIM, and DMARC automatically during inbox provisioning, so the SMTP connection from provisioned inboxes is fully authenticated without manual DNS work.
When practitioners ask about SMTP and deliverability, they are usually asking: "Will my cold emails reach the inbox?" The answer depends on:
The SMTP protocol itself is not a deliverability variable. SMTP is the delivery mechanism; the factors above determine whether what SMTP delivers reaches the inbox or the spam folder.
Per Woodpecker's 2025 cold email benchmark study, top-quartile cold email senders achieve 15–20% reply rates. None of that performance difference is attributable to SMTP configuration. All of it is attributable to domain reputation, authentication, warmup, contact quality, and copy.
"I spent two weeks researching SMTP configurations before our first cold email campaign and came away more confused than when I started. The breakthrough was realizing that SMTP is just the delivery vehicle and the real decisions are which inbox provider to use and how to warm up the domains. Once we got off a bulk SMTP service and onto dedicated Microsoft 365 inboxes through Inframail, our inbox placement went from around 50% to 90%+ within six weeks. The SMTP protocol was the same in both setups. The IP reputation and warmup were what changed." — G2 reviewer, Inframail reviews on G2
Instantly holds a 4.9/5 rating from 2,800+ verified reviews on G2, with custom SMTP inbox connection, warmup network, and deliverability monitoring cited as the infrastructure features that make dedicated inbox cold email performant without requiring direct SMTP management by the sender.
| 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 |
Does SMTP configuration affect cold email deliverability?
Not directly. SMTP is the universal email delivery protocol used by all email regardless of provider. Deliverability is determined by the reputation of the IP addresses used to send the SMTP connection, the domain reputation built through warmup, authentication records (SPF, DKIM, DMARC), and sending behavior (complaint rate, bounce rate, sending limits). The SMTP protocol itself is identical across providers.
What is the difference between SMTP relay and a dedicated inbox for cold email?
An SMTP relay service (like Mailgun or SendGrid) receives your email via SMTP and forwards it using the service's IP infrastructure. A dedicated inbox (like a Microsoft 365 inbox provisioned via Inframail) is a full email account on your sending domain, which sends email using the inbox provider's IP infrastructure and builds its own sending reputation through warmup. Dedicated inboxes are better suited for B2B cold email because they build per-inbox reputation, support ongoing warmup, and give the sender control over the domain and inbox lifecycle.
Why does Instantly ask for SMTP credentials when setting up an inbox?
Instantly connects to each sending inbox via SMTP (to send email) and IMAP (to receive email, detect replies, and participate in warmup). The SMTP credentials are the inbox account's outgoing email settings — username, password, and SMTP server address. Inframail provides these credentials during inbox provisioning. Instantly uses them to send sequences from the inbox on the sender's behalf.
Can I use bulk SMTP services like Mailgun for cold email?
Mailgun is technically compatible with cold email tools that support custom SMTP. However, Mailgun and similar bulk services are designed for transactional email and many prohibit cold email (unsolicited outreach) in their terms of service. More practically, bulk SMTP services lack per-inbox warmup capability and use shared IP pools that may carry different reputation characteristics than Microsoft 365's infrastructure. For B2B cold email, dedicated inbox provisioning via Inframail is the more appropriate infrastructure choice.
The SMTP protocol is the same everywhere. Contact quality is not.
Inbox placement depends on domain reputation, warmup, and authentication — all of which can be set up correctly. The variable that collapses performance even on a correctly configured infrastructure is bounce rates from unverified contacts. Quarvio delivers pre-verified B2B contacts so the SMTP connection reaches a valid inbox every time. One-time purchase, no subscription.
