EquitleEducationTry for free

Lesson 2 of 11 · Owner outreach fundamentals

Email deliverability

7 min read · Updated Nov 16, 2026

The short answer

Deliverability is whether your email lands in the inbox instead of the spam folder or nowhere at all. It depends on proving the message came from your domain, using SPF, DKIM and DMARC, and on a sending reputation built from steady volume, few bounces and very few spam complaints.

By the end of this lesson you will be able to:

  • Explain what SPF, DKIM and DMARC each prove to a receiving mail server
  • Describe how volume, bounces and spam complaints shape a sender's reputation
  • Plan outreach on a dedicated domain that is warmed before use

What a receiving mail server checks

  1. 1
    SPFIs this server allowed to send for the domain?
  2. 2
    DKIMIs the signature valid?
  3. 3
    DMARCDoes either match the From address?
  4. 4
    ReputationHow has this sender behaved?
  5. 5
    PlacementInbox, spam or refused
Simplified. A message has to prove where it came from before reputation decides where it lands.

Key takeaways

  • Mailbox providers decide where a message lands. A sent email is not a delivered one.
  • SPF lists the servers allowed to send for a domain, DKIM signs each message, and DMARC ties both to the address the reader sees.
  • Google asks senders to keep reported spam below 0.10% and never reach 0.30%. Yahoo sets its limit at 0.3%.
  • Use a separate domain for outreach, raise volume slowly and send at a steady rate.
  • Remove bounced addresses at once and stop writing to anyone who asks.

What deliverability means

Sending an email and having it read are different things. Between the two sits the recipient's mailbox provider, such as Gmail, Outlook or Yahoo Mail. It decides whether each message goes to the inbox, goes to spam or is refused. Deliverability is how much of your mail makes it to the inbox.

Email is usually the first step in a multi-channel campaign, and you are writing to people who do not know you. If your notes go to spam, the campaign fails quietly: nothing bounces and nobody replies. Two things decide the outcome. Authentication is whether you can prove the message came from you. Reputation is how you have behaved as a sender.

Authentication: SPF, DKIM and DMARC

Email was designed without a way to check who sent a message. Three standards, each published in the RFC series that sets out how the internet works, fill the gap. Each is a short text record in your domain's DNS, the public directory that tells the internet where a domain's services live.

SPF is Sender Policy Framework. DKIM is DomainKeys Identified Mail. DMARC is Domain-based Message Authentication, Reporting and Conformance.
StandardWhat it provesWhere it is defined
SPFThe domain has listed which servers may send its mail, and this message came from one of them.RFC 7208, April 2014
DKIMThe sending domain signed the message. The receiver checks the signature against a public key in DNS.RFC 6376, September 2011
DMARCThe domain in the From address matches a domain that passed SPF or DKIM. It also says what to do when neither matches.RFC 7489, March 2015, replaced by RFC 9989 in May 2026

These records are required, not just advised. Google's Email sender guidelines say every sender to personal Gmail accounts must set up SPF or DKIM. Senders of more than 5,000 messages a day to Gmail accounts need SPF, DKIM and DMARC, and the domain in the From address must line up with the SPF or DKIM domain. Yahoo's sender requirements follow the same pattern. Both have applied since February 2024.

Reputation: how you have behaved

Passing authentication only proves who you are. Whether you are welcome depends on your record. Mailbox providers watch three signals closely.

  • Spam complaints. When a reader marks your message as spam, it counts against you. Google tells senders to keep the spam rate reported in its Postmaster Tools below 0.10% and to avoid ever reaching 0.30%. Yahoo asks senders to stay below 0.3%.
  • Bounces. Mail to addresses that do not exist suggests a poor list. Yahoo tells senders to remove invalid recipients promptly.
  • Volume. Google advises increasing volume slowly and sending at a consistent rate, not in bursts. It warns that suddenly doubling volume can lead to rate limits or a drop in reputation.

A rate of 0.10% is one complaint in every 1,000 messages. Outreach lists are short, so very few complaints are enough to do damage.

Why outreach uses its own domain

Most teams do not send cold outreach from the domain their firm uses for everyday mail. If outreach damages a domain's reputation, every message from that domain suffers, including notes to investors, lenders and portfolio companies. A dedicated sending domain is a separate, similar-looking domain used only for outreach, with its own inboxes and its own SPF, DKIM and DMARC records. Yahoo's guidance makes a related point: keep different kinds of mail apart, so trouble with one does not spill into another.

Warm-up means starting a new inbox with a small amount of mail and raising it gradually, so providers see steady, normal use before a campaign begins. Several inboxes each sending a modest amount put less at risk than one inbox sending everything.

Habits that keep you in the inbox

  • Send only to addresses you have reason to believe are current, and remove any that bounce.
  • Keep daily volume per inbox low and even.
  • Write short, plain notes to one person. The first email an owner answers shows how.
  • Make it easy to say no, and stop when asked. A reader who can opt out has less reason to press the spam button.
  • Watch for warning signs: a rise in bounces, or replies drying up across a whole inbox.

Rules on content and opting out sit alongside these technical ones, and outreach rules covers them. Once mail is landing, measuring a campaign explains what to track.

How Equitle helps

You do not buy domains, set up the records or warm inboxes by hand: you choose a domain and how many inboxes you want, and Equitle registers it, sets the SPF, DKIM and DMARC records and starts warming. An inbox that is still warming stays out of your campaigns until it is ready, and your other inboxes keep sending. If bounces spike on an inbox, Equitle rests it and brings it back on its own.

Key terms

Sources

  1. Google (2026). Email sender guidelines, Google Workspace Admin Help (undated page, read November 2026; the requirements have applied since February 1, 2024): authentication rules for all senders and for senders of more than 5,000 messages a day to Gmail accounts, the 0.10% and 0.30% spam rate thresholds, and the advice to raise volume slowly and send at a consistent rate. View source
  2. Yahoo (2026). Sender Best Practices, Yahoo Sender Hub (undated page, read November 2026; enforcement began in February 2024): SPF, DKIM and DMARC requirements, the 0.3% spam rate limit, honoring unsubscribes within 2 days, removing invalid recipients and keeping different kinds of mail apart. View source
  3. RFC Editor (2014). RFC 7208, Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1, April 2014: how a domain lists the hosts allowed to send its mail and how a receiver checks the list. View source
  4. RFC Editor (2011). RFC 6376, DomainKeys Identified Mail (DKIM) Signatures, September 2011: how a domain signs a message and how a receiver verifies the signature with a public key held in DNS. View source
  5. RFC Editor (2015). RFC 7489, Domain-based Message Authentication, Reporting, and Conformance (DMARC), March 2015: alignment between the From domain and SPF or DKIM, and the none, quarantine and reject policies. The RFC Editor page marks it as obsoleted by RFCs 9989, 9990 and 9991. View source
  6. RFC Editor (2026). RFC 9989, Domain-Based Message Authentication, Reporting, and Conformance (DMARC), May 2026: the current DMARC specification, which obsoletes RFC 7489. View source

Common questions

Do these rules apply if I only send a few dozen emails a day?

In part. Google requires every sender to personal Gmail accounts to set up SPF or DKIM and to keep spam rates below 0.3%, whatever the volume. The stricter set, which adds DMARC, applies to senders of more than 5,000 messages a day. Setting up all three is good practice at any size.

What is the difference between a bounce and a spam complaint?

A bounce is the receiving server refusing a message, most often because the address does not exist. A spam complaint is a person marking a delivered message as spam. Both count against the sender.

How long does warm-up take?

There is no official figure. Google says to increase volume slowly and to reduce it if messages start bouncing or being deferred. Treat warm-up as a gradual build, and let bounces and replies set the pace.

Does the DMARC policy have to be set to reject?

No. Google says the DMARC policy can be set to none, and Yahoo asks for at least none. A stricter policy protects your domain from being impersonated, and you can adopt it once you are sure your own mail passes.