Skip to main content

Send a test email to verify preview

Master Email Deliverability: Step-by-Step Guide to Check Email Deliverability

Updated over a week ago

Learning objective

By the end of this tutorial, you’ll know how to preview an email step, run a spam score check, and interpret the key deliverability signals before you launch.

Why this matters

Checking your spam score before launch helps you catch common issues (formatting, content patterns, authentication signals) that can reduce inbox placement. A quick pre-flight check can prevent poor campaign performance and protect your sender reputation.

Prerequisites

  • You have a campaign created with at least one Email step.

  • Your user account has an email provider connected (required to send the test).

Core workflow: Preview and check spam score

1) Open the email step preview
From your campaign, go to Sequence, click the Email step you want to verify, then click Preview (eye icon). This opens the Email Step Preview so you can validate how the message renders and run deliverability checks.

Screenshot

2) Run the spam score check
In the Email Step Preview, click Check spam score. This sends a test email to lemlist servers and generates a report highlighting potential spam-related issues.

Screenshot

3) Review the spam score report
Review your SpamAssassin score and the authentication results (such as SPF, DKIM, and DMARC) shown in the report. A higher score indicates a higher likelihood of landing in spam, and failed authentication signals can negatively impact deliverability.

Screenshot

Practical application: what to look for in the report

  • SpamAssassin score: Use it as a quick risk indicator before launch.

  • Inbox/labeling signal: Helps confirm how the message is categorized in the test.

  • SPF / DKIM / DMARC: “Pass” results strengthen authenticity and improve deliverability.

Troubleshooting & pitfalls

Issue: The test email won’t send
Root cause: The logged-in user doesn’t have an email provider connected.
Fix: Connect an email provider to the logged-in user, then run Check spam score again.

Issue: SPF/DKIM/DMARC fail in the report
Root cause: DNS records aren’t set up correctly (or haven’t propagated yet).
Fix: Verify your domain DNS configuration and re-test after updates propagate. Learn more about DNS testing here.

Note: Test emails are sent from the email address of the logged-in user, not the campaign’s sender address.

If the logged-in account lacks a connected email provider, the test email won’t send.

Did this answer your question?