emailsecuritygrade.com

Email Deliverability Best Practices: 10 Steps to Stop Landing in Spam

November 17, 2026

Email deliverability — whether your messages actually reach the inbox — comes down to a short list of things you control. Most deliverability problems come from the same handful of mistakes, and fixing them is straightforward once you know the order to work through them.

Here are ten email deliverability best practices that cover the three layers that matter: authentication, reputation, and engagement.

Key facts

  • Gmail and Yahoo have required SPF, DKIM, and DMARC since February 2024 for senders of 5,000+ messages per day (Google Workspace Updates, 2023-10-03).
  • A spam complaint rate above 0.1% (1 per 1,000 deliveries) damages your domain reputation in Google Postmaster Tools.
  • SPF records must stay under 10 DNS lookups — each include: statement counts as one (RFC 7208 §4.6.4).
  • DMARC policies escalate from p=none (monitoring only) to p=quarantine (spam folder) to p=reject (hard fail).
  • A new sending domain needs 2-4 weeks of gradual volume ramp-up before mailbox providers trust it.
  • Forwarded email breaks SPF authentication because the forwarding server isn't in the original SPF record, but a valid DKIM signature survives forwarding.

1. Publish all three authentication records

SPF, DKIM, and DMARC are the foundation. If any one is missing, receiving servers have no reliable way to confirm the email came from you. Start here before touching anything else.

  • SPF lists every server authorized to send mail for your domain, and ends with -all to reject anything not on the list.
  • DKIM publishes a public key your mail server signs every message with. Keep the selector stable — changing it breaks verification for in-flight mail.
  • DMARC ties them together with a policy. Start at p=none to collect reporting data, then move to p=quarantine once you're confident no legitimate senders are missing.

Most senders fix deliverability by fixing just these three records. Scan your domain with a free SPF, DKIM & DMARC checker to see exactly which records are present, missing, or misconfigured.

2. Keep your SPF record under 10 DNS lookups

Every include: statement in an SPF record triggers a DNS lookup. Each third-party service you add — SendGrid, Mailchimp, Salesforce, Google Workspace — adds another include. Once you hit 10 lookups, SPF returns permerror and the receiving server can't evaluate the record at all.

Fix it: flatten your SPF record by resolving all includes into their IP ranges and listing them as ip4: statements instead. SPF flattening tools are free and widely available. If you must keep includes, audit every third party service and remove any that no longer sends mail for your domain.

3. Don't skip DMARC reporting

DMARC reports are XML files that tell you who is sending email as your domain — including anyone spoofing it. Set rua= in your DMARC record to receive aggregate reports, and ruf= for forensic reports if you want details on individual failures.

Without reports, you're guessing which services are authenticated and which are being spoofed. Read the reports weekly at first to catch missing senders before you tighten your DMARC policy.

4. Monitor your spam complaint rate

Google Postmaster Tools gives every domain that sends to Gmail a direct look at its spam rate, domain reputation, and delivery errors. The critical number: keep your spam complaint rate under 0.1%. Above 0.3%, many providers start filtering all your mail.

If you see a spike, the most common cause is sending to stale or purchased lists. Addresses that haven't engaged in months are more likely to mark your mail as spam than to read it.

5. Warm up new sending domains

A domain with no sending history arrives with zero reputation. Mailbox providers default to "filter cautiously" when there's nothing to trust.

The industry standard warmup is 2-4 weeks: start with 10-20 messages per day in week one, increase gradually to 50-100 in week two, and continue ramping up each week. The goal is to look like organic, human-initiated sending — not a script firing thousands of messages into the unknown.

Warmup tools that generate real engagement signals (opens, replies, folder moves from real mailboxes) can shorten this window by proving to providers that people want your mail.

6. Authenticate forwarded email

When a recipient has email forwarding enabled (common with legacy corporate setups), the forwarding server becomes the delivery server — and unless that server is in your SPF record, SPF fails. DMARC sees the SPF failure and can quarantine or reject the message.

DKIM survives forwarding. As long as the original message has a valid DKIM signature, the forwarding server doesn't need to be in your SPF. This is the strongest technical argument for deploying DKIM even if SPF is already working.

7. Clean your list quarterly

List hygiene is not optional. Addresses that bounce, haven't opened in 6+ months, or were acquired through a signup you no longer trust — all of them hurt your reputation.

Remove these addresses every quarter:

  • Hard bounces (the address doesn't exist)
  • Addresses with zero opens in 6 months
  • Addresses that generated a spam complaint

A list of 1,000 engaged subscribers delivers better than 10,000 stale ones. The reduced volume hurts nothing — mailbox providers reward consistency, not volume.

8. Use consistent sending patterns

Sending 200 messages a day every day builds more trust than sending 5,000 once a month. Inconsistent volume — especially sudden spikes — looks like a compromised account or a purchased list.

If you need to increase volume, ramp up gradually over days or weeks. A 2x increase overnight triggers filters at every major provider. A 20-30% increase every few days goes unnoticed.

9. Make unsubscribing easy

As of February 2024, Google and Yahoo require bulk senders to offer one-click list-unsubscribe. But even if you're below the threshold, making unsubscription frictionless reduces spam complaints more effectively than any technical fix.

Key rules:

  • One-click unsubscribe from the message itself (RFC 8058), not just a link to a web page
  • Process unsubscribes immediately — don't make recipients wait for a confirmation email
  • Never require login to unsubscribe

A frustrated recipient who can't find the unsubscribe button will click "mark as spam" instead. That single complaint triggers reputation damage that can take weeks to undo.

10. Test before sending, monitor after

Before you send to your full list, test your authentication with a DNS checker to confirm every record resolves correctly. After sending, watch your Postmaster Tools spam rate and your open rates over time.

A drop in opens that doesn't recover in a few days is usually a reputation problem — not a content problem. Catch it early, and you can pull back volume, check blocklists, and fix what's wrong before it compounds.

Check your grade free

Don't guess what's broken — see it. Scan your domain free at emailsecuritygrade.com and get an instant A-F grade on your SPF, DKIM, DMARC, and MX records, with a plain-language fix for anything failing. No signup, no install — it runs in your browser.

If your emails are still landing in spam after fixing the records, a deliverability tool like InboxAlly can train mailbox providers to trust your sending — worth a look once your grade is solid.

Fixed your records? Now fix deliverability.

Correcting SPF, DKIM, and DMARC is step one — but inbox providers don't trust a domain overnight. InboxAlly trains Gmail, Outlook, and Yahoo to trust your sending domain by generating real engagement signals, so your emails stop landing in spam within weeks instead of months. Most users see open rates double in 2–4 weeks.

Start free with InboxAlly →