Email Deliverability Best Practices
This guide is written for most businesses and SaaS teams, whether you send through SendGrid, Postmark, Mailgun, Amazon SES, or another provider. The principles stay the same even if the UI changes.
Authentication
Prove your mail is legitimate with SPF, DKIM, and DMARC.
Consent
Send only to people who clearly asked to hear from you.
Warm-up
Ramp up gradually so mailbox providers learn to trust you.
Separation
Keep transactional and promotional mail apart.
Monitoring
Watch complaints, bounces, and engagement every week.
Content
Make emails easy to read, easy to trust, and easy to leave.
Why deliverability matters
Inbox placement is mostly about trust. Mailbox providers look at whether your domain is authenticated, whether recipients expect your emails, whether they complain, and whether your sending patterns look stable. If you skip the basics, even legitimate email can get filtered, rate-limited, or blocked.The five-part playbook
1) Authenticate every sending domain
At minimum, every sending domain should have SPF and DKIM. If you send at bulk volume, you should also publish DMARC. In practice, most teams should set up all three from the start.Enable DKIM
Turn on DKIM signing for your sending domain and use a strong key length when supported.
Publish DMARC
Start with a monitoring policy such as
p=none, review reports, then tighten later if your alignment is healthy.2) Send only to people who expect your email
This is where many teams lose deliverability. A technically perfect setup still performs badly if recipients did not ask for the message. Do this:- Use clear opt-in language
- Keep your send frequency consistent with what people signed up for
- Remove hard bounces immediately
- Stop mailing people who never engage
- Make unsubscribing simple
- Buy lists
- Scrape leads
- Add users through pre-checked boxes
- Keep blasting inactive contacts forever
The quality of your recipient list has more impact on deliverability than your template design.
3) Warm up new domains and new streams gradually
A new domain, subdomain, or dedicated IP has no reputation history. Treat it carefully. Start small. Send to your best recipients first, the people most likely to open, click, or reply. Increase volume in steady steps instead of sudden spikes. Good warm-up behavior:- Low starting volume
- Stable daily sends
- Highest-quality recipients first
- Gradual increases over days and weeks
- No sudden campaigns to cold lists
- Sending thousands on day one
- Long silence followed by a spike
- Mixing low-quality leads into the first sends
- Changing domains and templates at the same time
4) Separate transactional and promotional email
Not all email has the same risk profile. Transactional mail includes password resets, receipts, booking confirmations, shipping updates, and account alerts. Promotional mail includes newsletters, campaigns, product announcements, and sales sequences. These should not share the same reputation stream if you can avoid it.Transactional email
Needs the highest reliability and should be protected from the risk of bulk campaigns.
Promotional email
Carries more complaint risk and should be isolated from critical product emails.
- one subdomain for transactional mail
- one subdomain for promotional mail
- separate suppression and reporting where possible
5) Monitor reputation every week
Deliverability is not set-and-forget. You need a simple operating rhythm. Track:- hard bounce rate
- spam complaint rate
- unsubscribe rate
- open and click trends
- inbox placement issues by provider
- DMARC reports
- block, deferral, or rate-limit errors from mailbox providers
What good email sending looks like
A healthy program usually looks boring:- authenticated domain
- consistent volume
- permission-based list
- clear sender identity
- obvious unsubscribe path
- clean segmentation
- separate streams for different email types
- weekly review of reputation signals
What hurts deliverability fastest
Sending to old or purchased lists
Sending to old or purchased lists
This creates bounces, complaints, and low engagement. Mailbox providers read that as unwanted mail.
Huge volume spikes
Huge volume spikes
Sudden increases look suspicious, especially from new domains or low-history senders.
Mixing all email on one stream
Mixing all email on one stream
A bad marketing blast can hurt your critical transactional email if everything shares the same reputation.
Generic tracking and redirect domains
Generic tracking and redirect domains
Branded sending domains and branded links usually build more trust than generic provider-hosted domains.
Making unsubscribe hard
Making unsubscribe hard
If people cannot leave easily, they report spam instead. That is far more damaging.
A simple rollout plan
Week 1: Fix authentication
Set up SPF, DKIM, and DMARC for every sending domain. Enable branded links and custom return-path if your provider supports them.
Week 1: Clean your list
Remove invalid, bounced, and clearly unengaged recipients. Split transactional and promotional audiences.
Week 2: Start warm-up
Send low volume to your most engaged recipients first. Keep volume steady and increase gradually.
Week 2+: Add monitoring
Review complaints, bounces, unsubscribes, and provider errors every week. Pause bad segments early.
Best practices by category
Authentication
- Set up SPF
- Enable DKIM
- Publish DMARC
- Use a sending subdomain
- Brand tracking links
List quality
- Send only to opted-in recipients
- Remove bounces immediately
- Suppress complainers and unsubscribes
- Sunset inactive contacts
- Avoid purchased or scraped lists
Sending patterns
- Warm up gradually
- Avoid spikes
- Send consistently
- Prioritize engaged recipients first
- Keep frequency aligned with expectations
Content and UX
- Use a clear From name
- Keep the message readable
- Avoid misleading subject lines
- Include a visible unsubscribe option
- Make the email look like it came from a real business
FAQ
Do I need DMARC if I already have SPF and DKIM?
Do I need DMARC if I already have SPF and DKIM?
If you send at any meaningful volume, yes. DMARC adds alignment and reporting, and it is part of current bulk sender expectations for major mailbox providers.
Should I use a dedicated IP?
Should I use a dedicated IP?
Not always. Dedicated IPs help when you have enough steady volume to build and maintain reputation. Low or inconsistent volume often does better on a healthy shared setup.
Should transactional and marketing email share one domain?
Should transactional and marketing email share one domain?
What matters more: template quality or list quality?
What matters more: template quality or list quality?
List quality. Great design cannot overcome sending to the wrong people.
Final takeaway
Deliverability is not a hack. It is reputation. If you remember only five things, remember these:- Authenticate every sending domain
- Send only to people who asked for it
- Warm up new domains and streams slowly
- Separate transactional and promotional mail
- Monitor complaints, bounces, and engagement every week