Delivery asks whether the receiving mail system accepted the message rather than rejecting it during transmission.
A delivered message may still end up somewhere the recipient rarely looks.
Email Marketing Guide · Deliverability
Email Deliverability Basics: How to Reach the Inbox
Sending an email is not the same as reaching the inbox. Deliverability depends on technical identity, recipient expectations, sender reputation, list quality, mailbox-provider requirements, and the signals your campaigns create over time.
This guide gives you a practical way to diagnose that system — from SPF, DKIM, and DMARC to complaints, bounces, unsubscribe handling, and provider monitoring.
The Delivery Path
Identity
Can the receiver verify who sent the message?
Permission
Did the recipient reasonably expect this email?
Transport
Does the message meet technical sending requirements?
Reputation
What does previous sending behavior signal?
Placement
Inbox, spam, another tab, temporary failure, or rejection?
Feedback
What do complaints, bounces, and provider data tell you next?
Start with the distinction
Delivery and deliverability are not the same thing
These terms are often used interchangeably, but diagnosing email problems becomes much easier when you separate them.
Deliverability is the broader question of whether accepted email reaches a useful destination — especially the inbox rather than spam or another low-visibility placement.
That depends on more than whether the receiving server says “accepted.”
A 99% “delivered” report does not prove 99% inbox placement.
Your email platform can often tell you whether messages bounced or were accepted. It usually cannot convert that number into a perfect measurement of where every mailbox provider placed every accepted message.
Diagnostic model
Six checkpoints determine what happens after you press Send
Who sent it?
Authentication gives mailbox providers technical evidence about the sending domain.
Was it expected?
Permission and subscriber expectations influence complaints and long-term list quality.
Is the setup valid?
DNS, encryption, message formatting, and sending infrastructure matter before content is evaluated.
What happened before?
Domains and sending infrastructure develop histories based on how mail is sent and received.
Where did it go?
Accepted mail can still be filtered differently across providers and recipients.
What did users do?
Spam reports, unsubscribes, bounces, and engagement create information for future sends.
August 2026
Mailbox-provider requirements you should know now
Gmail, Yahoo, and Microsoft do not use one universal definition of a bulk sender, and their exact requirements differ. Use each provider's current documentation rather than relying on an old checklist copied from another marketer.
| Provider | Who is affected? | Authentication | Unsubscribe | Complaint / Spam guidance |
|---|---|---|---|---|
| Gmail | Requirements apply to all senders. Additional bulk requirements apply at roughly 5,000+ messages to personal Gmail accounts in 24 hours. |
All senders: SPF or DKIM minimum. Bulk: SPF + DKIM + DMARC, with From-domain alignment through SPF or DKIM. |
Bulk marketing and subscribed messages require one-click unsubscribe plus a clearly visible unsubscribe link. | Google recommends keeping the Postmaster Tools spam rate below 0.1% and avoiding 0.3% or higher. |
| Yahoo | All senders have baseline requirements. Yahoo intentionally does not publish a fixed numeric threshold for its “bulk sender” classification. |
All senders: SPF or DKIM minimum. Bulk: SPF + DKIM + DMARC with at least p=none and required alignment. |
Bulk senders need List-Unsubscribe support, a visible body link, and should honor unsubscribes within 2 days. | Yahoo says to keep its spam complaint rate below 0.3%. |
| Outlook.com | Microsoft's current high-volume requirements apply to large senders to its consumer email services, including Outlook.com and Hotmail.com. | High-volume senders: SPF and DKIM must pass, a DMARC record must be published, and DMARC validation/alignment must pass. | Follow applicable legal, platform, and sender-policy requirements for commercial mail. | Authentication failures can lead to rejection, including documented 550 5.7.515 errors. |
Important:
Provider rules change. The numbers above describe current published requirements and guidance
as of August 2026. They are not permanent universal constants.
Current official references:
Gmail Email Sender Guidelines
,
Yahoo Sender Requirements
,
and
Microsoft high-volume sender requirements
.
Checkpoint 1 · Identity
SPF, DKIM, and DMARC solve different parts of the identity problem
These three terms are often bundled together, which makes them sound interchangeable. They are not.
Who is allowed to send?
Sender Policy Framework publishes information in DNS about which systems are authorized to send mail for a domain used during mail transport.
If you use an email service provider, its infrastructure normally needs to be represented correctly in your SPF setup.
Audit question:
Does your SPF record include every legitimate platform that sends mail on behalf of the domain?
Does your SPF record include every legitimate platform that sends mail on behalf of the domain?
Was the message signed?
DomainKeys Identified Mail adds a cryptographic signature to outgoing messages. The receiver can use the public key published in DNS to validate that signature.
Your email platform normally provides the DNS records or CNAMEs needed to activate DKIM.
Audit question:
Are your campaigns actually being DKIM-signed with the domain you expect?
Are your campaigns actually being DKIM-signed with the domain you expect?
Does identity line up?
DMARC evaluates whether the visible From domain aligns with an authenticated SPF or DKIM identity. It also allows a domain owner to publish policy and receive reports.
A DMARC record alone is not proof that messages pass DMARC. Authentication and alignment still need to work correctly.
Audit question:
Does at least one authenticated identity align with the visible From domain?
Does at least one authenticated identity align with the visible From domain?
DMARC p=none does not mean “DMARC is off.”
A monitoring policy can still evaluate authentication and alignment while requesting no quarantine or reject action from receiving systems. Gmail and Yahoo currently allow p=none as the minimum published DMARC policy for their relevant bulk-sender requirements. That does not mean every organization should remain at p=none forever.
Do not copy random DNS records from a tutorial.
SPF, DKIM, and DMARC values depend on your domain, sending platforms, and infrastructure.
Use the exact setup instructions provided by your email service and verify the results afterward.
Checkpoint 2 · Transport
Authentication is important, but it is not the entire technical layer
Forward & reverse DNS
Gmail and Yahoo both include valid forward and reverse DNS records among their sender
requirements. Reverse DNS is commonly associated with the PTR record for a sending IP.
TLS
Gmail requires senders to use TLS for transmitting mail. In most modern email marketing
setups your provider handles this, but it is still part of the delivery chain.
Message formatting
Major mailbox providers expect standards-compliant email formatting. Gmail references RFC 5322,
while Yahoo references RFC 5321 and RFC 5322.
Sending infrastructure
Determine whether your platform uses shared infrastructure, a dedicated IP, or another arrangement.
A dedicated IP gives you more direct control over IP reputation but also makes you responsible for
establishing and maintaining it.
Consistent identity
Avoid changing domains, From identities, or infrastructure unnecessarily. When something changes,
document the change so a future deliverability decline can be compared against it.
Checkpoint 3 · Reputation
Your DNS can be perfect and your inbox placement can still struggle
Authentication helps prove identity. It does not automatically make a sender wanted.
Mailbox providers can also evaluate signals associated with the history of your domain, sending infrastructure, volume patterns, recipient feedback, and messages.
Domain reputation
Your sending domain develops a history across campaigns. That is one reason changing IP addresses is not a universal fix for deliverability problems.
IP reputation
Sending IPs can develop reputations too. On shared infrastructure, your ESP manages much of this layer. On dedicated infrastructure, more responsibility moves to you.
User feedback
Spam complaints are a direct signal that recipients did not want or recognize a message. Monitor them instead of focusing only on opens and clicks.
Do not treat a new IP address as an eraser.
If the underlying problem is poor permission, irrelevant targeting, misleading messages, or aggressive volume, changing infrastructure without changing behavior does not solve the cause.
Checkpoint 4 · Audience
List quality starts before the first campaign
Deliverability is not only a server problem. It is also an audience-selection problem.
If people do not remember subscribing, no longer care about the topic, receive content different from what they expected, or were never a suitable audience in the first place, technical authentication cannot make that relationship healthy.
Build lists around clear expectations and use email segmentation when different subscribers need meaningfully different communication.
Ask these questions
Source:
Where did this address come from?
Expectation:
What did the subscriber believe they were signing up for?
Age:
Has this contact received relevant communication recently?
Fit:
Is this campaign actually appropriate for this subscriber?
Suppression:
Are unsubscribed, invalid, or otherwise suppressed contacts excluded correctly?
Purchased or scraped lists create more than a legal question.
Even where a particular law does not universally require prior opt-in, mailbox providers,
ESP policies, complaint behavior, and recipient expectations can make unsolicited lists a
serious deliverability risk.
Bounces
A bounce is a symptom. Read the reason before choosing the fix.
“Bounce rate went up” is not yet a diagnosis.
Permanent-style failures
Examples may include addresses or domains that do not exist, or receiving systems that permanently reject a message.
Email platforms often classify these as hard bounces, but use the actual SMTP response and your provider's classification rather than assuming every failure fits the same label.
Temporary-style failures
A receiver may temporarily defer mail because of rate limiting, infrastructure problems, mailbox conditions, reputation, or another transient reason.
Your ESP may retry these automatically. Again, the response code and provider explanation matter more than the generic label.
1
Separate the affected providers.
A problem concentrated at Gmail requires a different investigation from a simultaneous failure across every destination.
2
Read the SMTP / bounce reason.
Look for authentication failures, nonexistent users, policy rejections, rate limiting, or other explicit clues.
3
Compare against recent changes.
New domain? New provider? New IP? Imported contacts? Volume increase? Authentication update? A timeline often narrows the investigation.
4
Fix the cause before increasing volume.
Sending more mail through a failing configuration can create more negative evidence, not clearer evidence.
Checkpoint 5 · Exit
An unsubscribe link and one-click unsubscribe are not the same mechanism
Visible unsubscribe
This is the link the subscriber can see in the email itself.
It may lead directly to an unsubscribe action or to an appropriate preference page, depending on your system and applicable requirements.
One-click unsubscribe
This is implemented through message headers, typically using the List-Unsubscribe and List-Unsubscribe-Post mechanism described by RFC 8058.
Mailbox providers can use those headers to provide their own unsubscribe interface.
A footer link does not automatically satisfy Gmail's one-click requirement.
Gmail specifically states that simply putting an unsubscribe link or mailto address in the message body does not replace the required List-Unsubscribe implementation for affected bulk marketing mail.
In practice, your email service provider should normally generate the technical headers. Your job is to verify that the feature is enabled and working for the message types where it is required.
Compliance timelines can differ.
US CAN-SPAM gives senders up to 10 business days to honor qualifying opt-out requests.
Yahoo's current bulk-sender policy says unsubscribes should be honored within 2 days.
Meeting one rule does not automatically mean you meet every mailbox-provider requirement.
References:
RFC 8058
,
Gmail Sender Guidelines
,
Yahoo Sender Requirements
,
and
FTC CAN-SPAM Guide
.
Checkpoint 6 · Feedback
Monitor mailbox-provider evidence, not just campaign reports
Your ESP dashboard is useful, but mailbox providers can expose additional information about how they see your traffic.
Useful for qualifying traffic sent to personal Gmail accounts.
- Compliance status
- User-reported spam rate
- Domain reputation
- IP reputation
- Authentication
- Encryption
- Delivery errors
Provides sender resources and complaint-management capabilities for Yahoo-managed domains.
- Domain verification
- Sender insights
- Complaint data
- Complaint Feedback Loop
- Sender support
Your email platform remains an essential operational view.
- Bounce classifications
- Spam complaints
- Unsubscribes
- Authentication setup
- Campaign trends
- Suppression handling
Do not expect every monitoring dashboard to show data immediately.
Google states that Postmaster Tools data is not real time, typically updates within about 24 hours, can take longer, and may not display complete information at low sending volumes.
Current monitoring references:
Google Postmaster Tools dashboards
and
Yahoo Complaint Feedback Loop
.
Interactive diagnostic
Provider Requirements Switcher
Choose the sender situation closest to yours and mark what is already configured. This tool does not test your DNS. It helps you identify what to verify next.
Your review priorities
Gmail bulk sender
This is a planning aid, not a live compliance test. Verify configuration against your ESP and the current mailbox-provider documentation.
Troubleshooting
Start with the symptom, then investigate in the right order
Deliverability troubleshooting becomes expensive when every possible fix is attempted at once. Choose the symptom first.
Content layer
Content matters — but avoid the mythical “spam word” checklist
Deliverability advice sometimes gets reduced to lists of words you should supposedly never use. That is too simplistic.
Keep promises consistent
The email should match the reason someone subscribed and the expectation created by the subject line.
For the inbox-facing layer, see Email Subject Lines.
Write useful messages
Manipulative wording is not repaired by replacing one supposedly forbidden word. The larger question is whether recipients recognize and value the communication.
For body content, see the Email Copywriting Guide.
Make exits easy
Do not hide unsubscribe options to artificially preserve list size. A smaller list of people who still want the communication is operationally more useful than forcing uninterested recipients to remain.
Quick audit
A practical deliverability checklist
Authentication
Verify SPF, DKIM, and DMARC using the actual domain and platform that sends your campaigns.
Alignment
Confirm that the visible From domain aligns through a passing SPF or DKIM identity as required.
Infrastructure
Confirm DNS, PTR where applicable, TLS, and standards-compliant message formatting.
Permission
Know where every major list segment came from and what those contacts reasonably expect to receive.
Bounces
Suppress invalid contacts according to your provider's handling and investigate unusual provider-specific failures.
Complaints
Monitor user-reported spam rather than assuming low unsubscribe numbers mean recipients are satisfied.
Unsubscribe
Verify the visible unsubscribe flow and, where applicable, RFC 8058 one-click unsubscribe support.
Monitoring
Use your ESP plus mailbox-provider tools when your volume makes useful data available.
Change log
Record major changes in domains, ESPs, sending IPs, forms, list imports, authentication,
frequency, and volume so you can correlate future problems with real events.
System context
Sometimes the deliverability problem begins somewhere else
The wrong people
If recipients repeatedly receive irrelevant messages, review email segmentation.
The wrong timing
Sending duplicate or obsolete automated messages can create negative experiences. Review email marketing automation.
The wrong relationship
Subscribers who never receive a useful introduction may not recognize future campaigns. Review your welcome email sequence.
FAQ
Email deliverability questions
What is email deliverability?
Email deliverability describes your ability to get email into useful recipient placements, particularly the inbox rather than spam or another filtered destination. It is influenced by authentication, reputation, infrastructure, audience quality, complaints, bounces, and provider policies.
What is the difference between email delivery and deliverability?
Delivery generally refers to whether the receiving system accepts the message. Deliverability goes further and considers where accepted mail is placed and whether it reaches a destination where the recipient is likely to see it.
Do I need SPF, DKIM, and DMARC?
Major mailbox providers increasingly expect strong authentication, especially from bulk and high-volume senders. Gmail and Yahoo require SPF plus DKIM plus DMARC for affected bulk senders, while Microsoft requires all three for affected high-volume senders. Even smaller senders can benefit from configuring all three correctly.
What does SPF do?
SPF publishes which systems are authorized to send mail using a domain in the mail transport process. Your SPF configuration should account for the legitimate services that send mail on behalf of that domain.
What does DKIM do?
DKIM adds a cryptographic signature to outgoing mail. The receiving system can use a public key published in DNS to verify the signature and the signing domain.
What does DMARC do?
DMARC uses SPF and DKIM results together with domain alignment to determine whether the visible From identity is appropriately authenticated. It also lets domain owners publish a policy and receive reporting data.
What spam complaint rate is safe?
There is no single universal safe percentage across every provider and context. Gmail currently recommends keeping the user-reported spam rate in Postmaster Tools below 0.1% and avoiding 0.3% or higher. Yahoo tells senders to remain below 0.3%. Treat these as provider-specific guidance, not a universal marketing benchmark.
Do I need one-click unsubscribe?
Gmail requires it for marketing and subscribed messages from affected bulk senders. Yahoo also requires easy unsubscribe for bulk marketing and subscribed mail. The technical mechanism uses List-Unsubscribe headers and is separate from simply displaying an unsubscribe link in the email body.
Will removing spam words fix deliverability?
Not by itself. Modern deliverability involves authentication, sender history, complaints, audience quality, infrastructure, provider policies, message relevance, and other signals. Replacing a few words does not repair a broken authentication setup or an unwanted mailing list.
Can a delivered email still go to spam?
Yes. A message can be accepted by the receiving system and then placed in spam or another filtered destination. That is one reason delivery rate and inbox placement should not be treated as identical metrics.
What should I check first when deliverability suddenly drops?
Start with what changed. Compare providers, review rejection or bounce messages, verify authentication, inspect complaint trends, check recent list imports or volume changes, and use provider-specific monitoring such as Google Postmaster Tools where available.
Does a DMARC record with p=none count as DMARC?
Yes. It is a monitoring policy rather than an enforcement policy. Gmail and Yahoo currently accept p=none as the minimum DMARC policy for their relevant bulk-sender requirements, provided the other authentication and alignment requirements are met.
Email Marketing Hub
Build the complete email system
Deliverability protects the path to the inbox. The other guides help you build the audience, write the message, automate the journey, and turn email into a useful long-term channel.
01
What Is Email Marketing?
02
Email Marketing for Beginners
03
How to Build an Email List
04
Lead Magnet Ideas
05
How to Create a Lead Magnet
06
Opt-In Page Best Practices
07
How to Create a Welcome Email Sequence
08
How to Build an Email Marketing Funnel
09
Email Segmentation Explained
10
Email Marketing Automation
11
How to Write Better Email Subject Lines
12
Email Copywriting Guide
13
Email Deliverability Basics
14
Email Marketing for Digital Products
15
Email Marketing Mistakes to Avoid