Smartlead deliverability troubleshooting checklist

Smartlead deliverability troubleshooting starts by naming the broken outcome. A campaign that stopped sending is different from a message that bounced. A bounce is different from a message accepted and placed in spam. Low replies are different again.

Do not change DNS, replace mailboxes, and rewrite copy at the same time. Preserve the evidence, classify the failure, fix one cause, then rerun the same check.

Classify the Smartlead symptom first

Use Smartlead’s campaign, sender, bounce, and SmartDelivery evidence to place the problem in one row.

Symptom	What it proves	Check first
Campaign paused or no sends	Smartlead did not complete the planned send	Campaign state, bounce protection, schedule, mailbox connection, available volume
Sender Bounced	The failure points to the sending mailbox or setup	Connection, authentication, blocklists, reputation, warmup
Lead bounced	The recipient address or domain rejected the message	SMTP response, address validity, recipient MX, list source
SmartDelivery shows Missing	The seed mailbox did not record the test message	Sender authentication, routing, rejection evidence, test account status
Message is in spam	The receiver accepted the message and filtered it	Reputation, message headers, links, content, complaints, recipient policy
Opens or replies fell	Campaign performance changed	First prove sends and acceptance, then review placement and message fit

These rows can overlap. One disconnected mailbox can reduce send volume while another mailbox keeps the campaign active. One bad lead segment can raise bounces without affecting every sender. Work at mailbox, domain, campaign, and recipient-provider level instead of relying on one account-wide average.

1. Confirm the campaign and mailbox actually sent

Start inside Smartlead. Check the campaign status, sending schedule, sender-account status, and recent send counts. Smartlead documents several reasons a campaign can pause, including high-bounce protection and exhausted email availability.

Confirm:

• The campaign is active and has an open sending window.
• High-bounce protection did not pause the campaign.
• Assigned mailboxes are connected and enabled.
• OAuth, SMTP, and IMAP credentials still work where applicable.
• Each mailbox has available daily volume.
• Leads remain eligible for the next step in the sequence.

Compare planned sends with completed sends by mailbox. If the count dropped because two mailboxes disconnected, there is no placement result to diagnose for the messages that never left.

Smartlead’s account health checklist covers mailbox connectivity, DNS, warmup, bounce handling, and blacklist status. Use the platform status to find the affected account, but verify external infrastructure separately when the fault can exist outside Smartlead.

2. Separate Sender Bounced from lead bounces

Smartlead’s Sender Bounced category means the lead may still be valid. The platform says this category points to a sending-side problem such as domain misconfiguration, weak reputation, a flagged domain, or incomplete warmup. Its Sender Bounced documentation warns against treating these leads as invalid by default.

For every bounce cluster, preserve:

• The full SMTP response code and text.
• The Smartlead bounce category.
• Sending mailbox and domain.
• Recipient domain and mailbox provider.
• Campaign, sequence step, and timestamp.

A 550 no such user across many domains points toward list quality. A 421 or policy rejection concentrated at one provider points toward throttling or reputation. A Sender Bounced cluster on one mailbox points toward that mailbox or its sending identity.

Use the cold email bounce rate troubleshooting checklist when the main symptom is rejection. Use the recipient domain preflight checker to find dead domains, missing MX records, free inboxes, and common security gateways before another send.

3. Verify SPF, DKIM, DMARC, and MX outside the dashboard

A green setup state can become stale after a DNS change, mailbox migration, or provider change. Read the live records and compare them with a received message.

Confirm:

• The sending domain has working MX records.
• Exactly one SPF record exists and includes every active sending source.
• SPF stays within the 10 DNS lookup limit.
• DKIM is enabled and the selector in the message exists in DNS.
• The DKIM d= domain or SPF identity aligns with the visible From domain for DMARC.
• The DMARC record is valid and published at the correct policy domain.

Smartlead’s authentication troubleshooting guide also directs operators to check duplicate records, selector mismatches, and DNS propagation. Do not stop at record presence. A DKIM record can exist under an old selector while the current message signs with another one.

Run the SPF, DKIM, and DMARC checker for a combined public lookup. Then inspect Authentication-Results, DKIM-Signature, From, and Return-Path in one message received from the live campaign.

4. Check warmup and sending changes

Warmup is an operating signal, not proof that a live campaign will reach the inbox. Still, a stopped or failed warmup can reveal a disconnected mailbox, disabled account, provider limit, bounce event, or block.

Confirm:

• Warmup is enabled for the intended mailbox.
• Warmup sends and replies have not gone flat.
• The mailbox can send and receive a manual test.
• The daily ramp did not jump after a quiet period.
• Live campaign volume fits the age and history of the domain and mailbox.
• No provider limit or cool-off period is suppressing activity.

Smartlead’s failed warmup troubleshooting guide recommends checking DNS, mailbox connectivity, current warmup activity, bounces, blocklists, and alignment. If Smartlead shows a mailbox issue, record the stated reason before reconnecting or replacing anything.

Do not respond to a placement drop by increasing warmup and live volume together. Hold volume, fix the identified failure, and resume gradually with a measured segment.

5. Read SmartDelivery results by category

SmartDelivery adds placement evidence from test messages. Its result categories distinguish Inbox, Tabs, Spam, Missing, Unmailable, and Bounced. These outcomes require different next actions.

SmartDelivery result	Next investigation
Inbox or Tabs	Compare by provider and preserve the test configuration
Spam	Inspect reputation, content, links, headers, cadence, and provider-specific patterns
Missing	Check whether the sender completed the send, then look for rejection or routing evidence
Unmailable	Fix sender mailbox authentication or connection before rerunning
Bounced	Read the SMTP response and classify sender-side vs recipient-side failure

Smartlead’s placement score documentation lists these categories and the technical, reputation, content, and list factors that can affect them.

Treat the test as a sample. A seed result says what happened to those messages at that time. It cannot prove placement for a different recipient, corporate gateway, message, or future send.

6. Inspect the message that was actually received

If SPF, DKIM, and DMARC pass but a message lands in spam, stop editing authentication records. The remaining evidence lives in reputation, sending behavior, the message surface, and recipient filtering.

Inspect:

• The connecting IP and every Received hop.
• SPF, DKIM, DMARC, and alignment in Authentication-Results.
• Every click redirect and open-tracking host.
• Link destinations added by templates, signatures, or calendar tools.
• Plain-text and HTML parts.
• Unsubscribe headers when they apply.
• Differences between the tested message and the live campaign step.

A branded tracking CNAME can resolve correctly while the final message still contains another shared redirect or pixel host. Use the tracking domain checker for the configured host, then inspect the .eml to discover every host the receiver saw.

Follow why authenticated emails still go to spam for the full placement investigation across reputation, tracking, SMTP identity, and recipient-side rules.

7. Check the infrastructure Smartlead cannot grade independently

Smartlead is the sending platform and SmartDelivery is its placement test. Both provide useful first-party operating evidence. A launch decision can still need an independent read of the surrounding infrastructure.

Check:

• Live public DNS rather than a saved setup state.
• Domain age and current blacklist evidence.
• Tracking-domain DNS, HTTPS, certificate, and redirect behavior.
• PTR, forward-confirmed reverse DNS, HELO, and banner identity for custom SMTP egress.
• Receiver requirements across every sending domain in the workspace.
• Whether a rerun preserved the original failure and verified the fix.

This does not replace Smartlead. It answers a different question. Smartlead operates campaigns and supplies mailbox, bounce, and placement evidence. OutboundQA checks the external setup and records a Ready, Needs Fix, or Do Not Launch verdict across the workspace. The Smartlead alternative page explains where the two evidence classes fit together.

Smartlead deliverability troubleshooting checklist

Require evidence in every row before resuming or scaling a campaign.

Area	Evidence	Decision
Campaign state	Active status, schedule, send counts, pause reason	Ready / Needs Fix / Do Not Launch
Mailbox connection	OAuth or SMTP and IMAP status, manual send and receive	Ready / Needs Fix / Do Not Launch
Bounces	Category, SMTP response, sender, recipient provider	Ready / Needs Fix / Do Not Launch
Authentication	Live SPF, DKIM, DMARC, MX, and message alignment	Ready / Needs Fix / Do Not Launch
Warmup and volume	Recent activity, ramp, limits, domain history	Ready / Needs Fix / Do Not Launch
Placement test	Provider-level Inbox, Tabs, Spam, Missing, Unmailable, Bounced	Evidence only
Message surface	Headers, tracking hosts, links, plain text, unsubscribe	Ready / Needs Fix / Do Not Launch
External infrastructure	Blacklists, tracking HTTPS, SMTP identity, receiver rules	Ready / Needs Fix / Do Not Launch

FAQ

Why is my Smartlead campaign not sending emails?

Check whether the campaign is paused, its bounce protection fired, the mailbox disconnected, the sending account ran out of available volume, or the schedule has no active window. A campaign that did not send is an operations problem, not proof of poor inbox placement.

What does Sender Bounced mean in Smartlead?

Smartlead uses Sender Bounced when the failure points to the sending mailbox or setup rather than the lead. Investigate mailbox connectivity, SPF, DKIM, DMARC, domain or IP reputation, blocklists, and warmup before suppressing the recipient as invalid.

Why do Smartlead emails go to spam when SPF, DKIM, and DMARC pass?

Authentication proves identity and alignment. Providers can still filter an accepted message using domain and IP reputation, complaint history, sending patterns, message content, tracking hosts, and recipient-side rules. Inspect the received message and compare outcomes by provider.

Does a passing SmartDelivery test guarantee inbox placement?

No. A placement test records what happened to a test message across its seed mailboxes at that time. It does not guarantee the result for every prospect, provider, corporate gateway, or future send.

Should I pause a Smartlead campaign with high bounces?

Yes. Pause the affected sending path while you classify the SMTP responses and separate invalid leads from sender-side failures. Continuing to send before the cause is fixed can add more reputation damage and make the evidence harder to read.

Run an independent check before the next send

Start with the free email deliverability checker for one sending domain. It checks observable authentication, routing, reputation, tracking, domain-age, and SMTP identity signals. A passing result removes known infrastructure blockers. It does not guarantee inbox placement.

For a client workspace, preserve the Smartlead campaign evidence beside the independent infrastructure verdict and the verified rerun. The result is a troubleshooting record another operator can review instead of a collection of dashboard screenshots.