# Email Deliverability Best Practices: A Technical Guide to Inbox Placement

> Improve email deliverability and inbox placement with this technical guide covering SPF, DKIM, DMARC, list hygiene, and sender reputation management.

- **Published:** 2025-08-03
- **Author:** Clixo
- **Reading time:** 5 min read
- **Tags:** deliverability, email-infrastructure, inbox-placement, technical
- **Canonical URL:** https://clixo.sh/blog/email-deliverability-best-practices-inbox-placement

You can have a near-perfect send rate and still lose more than a third of your emails to spam folders or outright rejection. Delivery rate and inbox placement rate are not the same metric, and most teams optimize for the wrong one until their campaigns stop working.

Deliverability is an infrastructure and behavioral problem, not a content problem. Fixing your subject lines will not save you if your sending domain has a poor reputation or your authentication records are incomplete.

## Why Inbox Placement Breaks Down

Email providers classify incoming mail using a combination of signals: authentication records, sender reputation, list quality, and engagement patterns. A failure on any one of these dimensions pushes mail toward spam or causes it to be rejected before it arrives at all.

Since late 2025, Gmail permanently rejects non-compliant bulk mail with hard SMTP errors. This is a meaningful shift — previously, non-compliant mail might land in spam. Now it can bounce entirely. Other major providers are moving in the same direction.

## Authentication: The Non-Negotiable Foundation

```mermaid
sequenceDiagram
  participant S as Sender MTA
  participant R as Receiving Server
  participant DNS as DNS
  S->>R: SMTP connection with MAIL FROM
  R->>DNS: SPF lookup for authorized IPs
  DNS-->>R: SPF result
  R->>DNS: DKIM key lookup via selector
  DNS-->>R: Public key
  R->>R: Verify DKIM signature
  R->>R: Apply DMARC policy
  R-->>S: Accept / Quarantine / Reject
```

### SPF

Sender Policy Framework tells receiving mail servers which IP addresses are authorized to send on behalf of your domain. Your SPF record lives in DNS as a TXT record. Keep it clean — overly long SPF records with too many lookup mechanisms fail silently. Stay under ten DNS lookups.

### DKIM

DomainKeys Identified Mail attaches a cryptographic signature to outgoing messages. Receiving servers verify the signature against a public key in your DNS. Use a 2048-bit key. Rotate keys periodically. If you send through multiple platforms (your product, your ESP, a third-party automation tool), each one needs its own DKIM selector.

### DMARC

DMARC ties SPF and DKIM together and tells receiving servers what to do when authentication fails: `none` (monitor only), `quarantine` (send to spam), or `reject` (block entirely). Start at `none` with reporting enabled, watch the aggregate reports, fix misalignments, then move to `quarantine` and eventually `reject`. Do not jump straight to `reject` on a domain with active sending without reviewing your alignment reports first.

## Sender Reputation

Your sender reputation is a score that major email providers assign to your sending IP and your sending domain. It reflects your history: how often your mail gets opened, how often it gets marked as spam, whether you send to invalid addresses, and whether your volume is consistent or erratic.

**The spam complaint rate is the most critical signal.** Gmail's hard threshold is 0.30%, but exceeding 0.10% consistently will damage your reputation before you ever get throttled. Monitor your complaint rate in Google Postmaster Tools, which is free and gives you domain-level reputation data directly from Google.

Keep your bounce rate below 2%. Hard bounces — invalid addresses — should be removed immediately and permanently. Soft bounces should be retried a finite number of times, then suppressed.

## List Hygiene

### Validate at the point of signup

Use a real-time email validation API at signup to catch typos, disposable addresses, and known spam traps before they enter your list. This is the cheapest form of list hygiene because it prevents the problem rather than cleaning it up later.

### Sunset inactive subscribers

Subscribers who have not opened or clicked any email in six to twelve months drag down your engagement rates and hurt your reputation. Run a re-engagement campaign for this segment. If they do not respond, suppress them. Sending to a smaller, engaged list is always better for deliverability than sending to a large, disengaged one.

### Never buy lists

Purchased lists are densely populated with spam traps, invalid addresses, and people who never agreed to hear from you. Sending to a purchased list is one of the fastest ways to destroy a domain's reputation.

## Sending Infrastructure

Separate your transactional and marketing sending. Use different subdomains — `mail.yourdomain.com` for transactional, `marketing.yourdomain.com` for campaigns. This ensures that a deliverability problem on your marketing side does not affect password reset emails and receipts.

If you are warming up a new IP address, ramp volume slowly over four to six weeks. Start with your most engaged subscribers. Sudden volume spikes on a new IP look like spam behavior to receiving servers.

## What to Monitor

Set up alerts for:

- Domain reputation in Google Postmaster Tools
- Spam complaint rate per campaign
- Hard bounce rate
- DMARC aggregate report failures

Review these weekly during active campaigns. Deliverability problems tend to compound quickly once they start — catching a reputation issue early is far easier than recovering from a block.

If you are building a product that sends email at volume and need the infrastructure set up correctly from the start, [Clixo can help](https://clixo.sh/#contact). We handle the architecture so your emails actually arrive.

---

Clixo · 1141 W Bryn Mawr Ave, Itasca, IL 60143, US · [hello@clixo.sh](mailto:hello@clixo.sh)
[Start a build](https://clixo.sh/#contact) · [All services](https://clixo.sh/services) · [Agent guide (llms.txt)](https://clixo.sh/llms.txt)