Skip to main content

Follow email sending best practices

Best Practices for Maintaining Email Deliverability 📧

Updated today

Cold outreach only works if your message reaches the inbox. Deliverability is a trust game: inbox providers reward consistent, authenticated senders who generate positive engagement, and penalize anything that looks risky or misleading.

This guide teaches the core principles and practical techniques to protect your sender reputation, reduce spam placement, and build an outreach motion that scales safely.


Why This Matters

If your emails land in spam (or get blocked), your copy and targeting don’t matter, you simply won’t get replies. Poor sending practices can damage your domain reputation, making future campaigns less effective even if you “fix” the content later.

Strong deliverability also improves sales efficiency: more inbox placement leads to more opens, more replies, and cleaner signal on what messaging actually works.


Core Principles / Mindset

  • Principle 1: Trust is earned through authentication and consistency. Inbox providers want proof you are who you claim to be (authentication) and that your behavior is predictable (consistent sending patterns and infrastructure).

  • Principle 2: Segmentation protects reputation. Mixing very different message types (transactional, promotional, cold outreach) makes it harder for inbox providers to classify your traffic and can increase complaints.

  • Principle 3: Engagement is the long-term “deliverability moat.” When recipients interact positively (reply, move to inbox, mark “not spam”), filters learn your mail is wanted.

  • Principle 4: Shortcuts create long-term damage. Purchased lists, spoofing, and forced opt-ins may look like quick wins, but typically increase spam complaints and bounces—two of the fastest ways to hurt deliverability.


Key Techniques / Strategic Approaches

Technique 1: Authenticate Your Emails (SPF + DKIM)

When to use: Always—before sending at scale from any domain used for outreach.

How it works: Add SPF and DKIM DNS records so inbox providers can verify the servers allowed to send for your domain and validate message signatures.

Why it works: Authentication reduces spoofing risk signals and improves trust, which supports better inbox placement.


Technique 2: Keep Consistency in IP Usage

When to use: Whenever you have control over sending infrastructure (or when your provider’s setup can vary IPs).

How it works: Ideally, send from the same IP address. If multiple IPs are unavoidable, assign one IP per message type (for example: one for product notifications, one for promotional newsletters, one for cold outreach).

Why it works: Consistent IP behavior builds a stable sending reputation. Separating message types prevents one stream (e.g., promotional bursts) from dragging down another (e.g., critical transactional mail).


Technique 3: Protect List Quality and Consent Signals

When to use: Before every campaign and whenever you change lead sources.

How it works: Avoid purchased lists and use clear opt-in methods where appropriate. Don’t rely on pre-checked/default opt-in forms.

Why it works: Recipients who didn’t expect your email are more likely to ignore it or mark it as spam, which harms sender reputation and future inbox placement.


Technique 4: Create Positive Engagement Loops

When to use: If you notice spam placement, low reply rates, or recipients saying they didn’t see earlier emails.

How it works: Encourage legitimate recipients to mark messages as not spam if they were incorrectly filtered and to reply when relevant.

Why it works: User actions are strong training signals for inbox filters and can improve placement over time.


Common Scenarios & How to Handle Them

  • Scenario 1: “Your email went to my spam.”
    ​What’s happening: The inbox provider is uncertain about your domain/IP reputation or the recipient’s mailbox has strict filters.
    ​How to respond: Ask them to mark the message as not spam, then reply to the thread (even a short reply). This helps train their inbox for future messages.
    ​Example reply you can send: “Thanks for letting me know—could you mark it as ‘Not spam’ so my next note lands correctly? Appreciate it.”

  • Scenario 2: “Transactional emails are fine, but outreach is getting filtered.”
    ​What’s happening: Different content types can earn different reputations, especially if they share the same domain/IP and one stream triggers complaints.
    ​How to respond: Separate streams by message type (and, when possible, by IP). Keep cold outreach and transactional messaging operationally distinct.

  • Scenario 3: “We changed providers/infrastructure and deliverability dropped.”
    ​What’s happening: Inbox providers see new sending patterns (new IPs, new signing behavior, different routing) and re-evaluate trust.
    ​How to respond: Re-check SPF/DKIM and return to consistent sending behavior; avoid big spikes and keep message types segmented.


What NOT to Do / Common Mistakes

  • Mistake: Mixing content types (promotional + transactional).
    ​Why it backfires: It confuses filtering systems and exposes critical mail to the risks of higher-complaint streams.
    ​Do this instead: Separate streams and keep message intent consistent.

  • Mistake: Spoofing domains or impersonating senders.
    ​Why it backfires: This is a major trust violation and can lead to blocks and reputation damage.
    ​Do this instead: Authenticate properly and send only from domains you control.

  • Mistake: Flagging internal messages as spam.
    ​Why it backfires: It teaches filters that your domain is unwanted—even by your own organization.
    ​Do this instead: Use “not spam” and move-to-inbox actions when needed.

  • Mistake: Purchasing email lists.
    ​Why it backfires: Low relevance increases complaints and harms reputation quickly.
    ​Do this instead: Build targeted lists and prioritize relevance and intent signals.

  • Mistake: Using default/pre-checked opt-in forms.
    ​Why it backfires: It can violate local regulations and often produces unengaged contacts.
    ​Do this instead: Use clear, explicit opt-in methods.


Practice This / Skill Development

  • Exercise 1: Deliverability baseline checklist. Before launching any campaign, verify SPF and DKIM are in place and confirm you’re not mixing message types on the same sending stream.

  • Exercise 2: Stream separation map. List every email type you send (transactional, newsletters, cold outreach) and decide where each should live (domain/IP/provider) so one stream can’t harm the others.

  • Exercise 3: Engagement recovery script. Write a short, polite message asking a trusted recipient to mark “not spam” if needed, and keep it ready for moments when spam placement appears.


How lemlist Enables This

  • Operational discipline for outreach. lemlist helps you run repeatable outreach campaigns, making it easier to keep cold outreach separate from other business-critical email streams.

  • Process reinforcement. Pair these best practices with a repeatable pre-launch routine, and keep your outreach motion consistent over time.


Measuring Success

  • Spam placement rate (qualitative + feedback). Track how often prospects say they found your email in spam and whether it improves after authentication and stream separation.

  • Reply rate stability. When deliverability improves, reply rates typically become more stable across similar audiences and campaigns.

  • Complaint signals. Fewer “this is spam” actions and fewer negative replies (“stop spamming me”) usually correlate with better inboxing.


Real Examples

  • Example 1: Authentication prevents avoidable filtering. A team started outreach from a new domain without DKIM. Replies were inconsistent and several prospects reported spam placement. After adding SPF and DKIM and keeping outreach on a consistent sending stream, “spam” feedback dropped and reply rates stabilized.

  • Example 2: Separating message types protects critical mail. A company sent product notifications and promotional blasts through the same stream. During a promotional push, complaints increased and some notifications began landing in spam. They separated streams by message type, and notification deliverability recovered.


Quick Reference / Cheat Sheet

  • Authenticate: SPF + DKIM set up and verified.

  • Be consistent: Prefer one IP; if multiple, assign one per message type.

  • Don’t mix: Keep promotional and transactional streams separate.

  • No shortcuts: No spoofing, no purchased lists, no default/pre-checked opt-ins.

  • Fix spam placement: Ask recipients to mark “not spam” and reply to train filters.


What to Do if Messages Are Marked as Spam

Even when you follow best practices, some legitimate emails may still end up in spam. If a recipient tells you this happened, ask them to:

  • Mark your email as not spam (or move it to the inbox), and reply to the thread.

These actions help their mailbox provider learn that emails from your domain are legitimate and should land in the inbox going forward.

Did this answer your question?