Cold email deliverability: a practical checklist
The settings and habits that keep your emails landing in the inbox: SPF, DKIM, DMARC, warm-up, plus the human factors that matter most.
Deliverability is mostly a reputation problem, not a technical one. Authentication gets you to the table; relevance and engagement keep you there. Here is the checklist that matters.
What authentication should you set up once?
- SPF: authorize the servers allowed to send for your domain.
- DKIM: cryptographically sign your mail so receivers can verify it.
- DMARC: tell receivers what to do with mail that fails the above.
Why does sender reputation matter more than settings?
Mailbox providers watch how people react to your email. Replies and opens build reputation; spam complaints and deletes destroy it. No amount of warm-up offsets sending email people did not want.
Which human factors beat any deliverability setting?
- Send fewer, more relevant emails to people who will actually want to hear from you.
- Send from your real, established inbox rather than throwaway domains.
- Make it easy to reply. Engagement is the strongest positive signal.
This is why Ember sends from your real inbox, in low volume, to people you have a genuine reason to contact. That is the opposite of the volume game, and far better for deliverability.
What do people ask?
- What hurts deliverability the most?
- Sending high volumes of unwanted email is the single biggest factor. Authentication (SPF/DKIM/DMARC) matters, but engagement and relevance matter more. Recipients marking mail as spam is what truly damages a sender.
More guides
Stop sequencing. Start closing.
Ember reads your pipeline, writes in your voice, and keeps every relationship moving. Approval is the default; auto-send is optional.