Email Deliverability: A Simple Guide to Reaching the Inbox
Email delivery means a server accepted your message. Email deliverability means the message reached the inbox instead of spam or a promotions tab. A sent message can be delivered and still be invisible to the person you wanted to reach.
There is no trick that guarantees inbox placement. Inbox providers look at a pattern: can they verify who you are, do people want these messages, and do you send in a steady, honest way? That is good news, because the important work is practical.
This guide is for a business sending permission-based marketing email. It explains the moving parts without pretending that a prettier subject line can repair a broken sending reputation.
Start here
Use a real sending domain
Send marketing mail from a domain you control, such as news@yourcompany.com. A free mailbox can be fine for one-to-one conversations, but it does not give you the same control or proof of identity. Keep the From name and address stable so subscribers recognise you.
Set up SPF
SPF is a DNS record that lists the services allowed to send mail for your domain. Think of it as a guest list at the door. Ask every service that sends as your domain—your email platform, help desk, and workspace provider—for its SPF instructions.
Do not create two SPF records; merge approved senders into one.
Turn on DKIM
DKIM adds a signed seal to every message. The receiving inbox checks that the message was signed by a domain allowed to use that seal and that it was not changed on the way. Your sending platform normally creates the key; you add its DNS record and enable signing.
Send a test after setup, not just a screenshot of the DNS page.
Publish DMARC
DMARC tells receiving providers how to use SPF and DKIM results and where to send reports. Start in monitoring mode (p=none) while you learn which services send on your behalf. It is a safety net against impersonation, not an instant inbox pass.
Gmail asks bulk senders to use SPF, DKIM, and DMARC, plus alignment between the visible From domain and authentication.
Send only to people who expect you
The fastest way to damage a sending reputation is sending to purchased, scraped, or old lists. Permission is not merely a legal checkbox. It changes how people act: a person who asked for your emails is more likely to open, click, ignore quietly, or unsubscribe instead of pressing Spam.
Increase volume slowly
A new domain has no history. Do not go from zero to a huge campaign in one day. Start with your most engaged subscribers, use a sensible schedule, and increase only while bounces and complaints stay low.
“Warm-up” is not a hack; it is the ordinary process of building a consistent sending history.
The details that make the difference
Reputation is earned by behaviour
Domain reputation is an inbox provider’s running estimate of whether your mail is wanted. It is influenced by complaints, bounces, engagement, authentication, and sudden changes in volume. You cannot buy a good reputation from a tool.
You build it by doing the same good things for long enough.
Keep promotional and transactional mail separate
A password reset and a sale announcement have different expectations. Where your setup allows it, use separate streams or subdomains and clear From addresses. If a promotion underperforms, it should not make a receipt or account alert look suspicious.
Do not use this separation to evade complaints; the same permission rules still apply.
Clean the list with care
Remove hard bounces immediately. For people who have been inactive for a long time, run a short re-permission campaign before sending them regular mail again. Do not keep mailing them forever because a large subscriber number looks good on a dashboard.
A smaller list of real readers is healthier.
Make leaving easy
Every marketing email needs an obvious unsubscribe link. Hiding it does not retain customers; it turns a normal “no thanks” into a spam complaint. For high-volume Gmail mail, one-click unsubscribe is also a sender requirement.
Honour unsubscribes quickly and do not add those contacts back through another import.
Check links and identity
Use links people can understand and trust. A message from Cresca that sends people through an unrelated short-link domain looks risky. Keep the display name truthful, avoid fake reply prefixes, and make the landing page match the promise in the email.
Trust is built from these small consistent signals.
Watch the right signs
Look at hard bounces, spam complaints, unsubscribe rate, and whether the same campaigns keep being opened or clicked. Open rate alone is not a verdict because privacy features can affect it. If inbox placement suddenly falls, first check authentication, list source, recent volume changes, and recent creative changes.
A practical setup check, step by step
Deliverability work feels technical because some of it happens in DNS, a place many marketers never visit. The job becomes much simpler if you split it between the people who own the domain and the people who send campaigns. Do not ask either person to guess.
Make a short list of every service that can send mail using your domain: Google Workspace or Microsoft 365, Cresca, a support desk, an invoicing tool, a booking tool, and any older platform that might still be connected.
Then give that list to the person who controls DNS. For each service, ask three questions: Does it send mail using our domain in the visible From address? Which SPF mechanism or DKIM records does it require?
Is it still active? The last question matters. Old services often leave records behind, and nobody is sure whether they still send.
Removing a service blindly can break receipts or support replies, so confirm before changing anything.
After records are added, do not stop at “the record exists.” Send a real campaign test to a Gmail address you control. Open the message, use Gmail’s Show original view, and check whether SPF and DKIM passed. Look at the visible From address too. If you send as news@example.com but the signed domain is unrelated, the message may not pass DMARC alignment. The point is not to become a DNS expert. The point is to confirm that a real inbox sees the proof you intended to publish.
SPF, DKIM, and DMARC without the acronyms getting in the way
| Tool | Plain-English job | What you should do |
|---|---|---|
| SPF | Lists who is allowed to send for your domain. | Keep one SPF record and include every approved sender. |
| DKIM | Adds a tamper-evident signature to each email. | Enable it in every platform that sends as your domain and test a real message. |
| DMARC | Checks whether the visible sender matches authentication and sends you reports. | Start with monitoring, read reports, then decide whether stronger protection is safe. |
These three tools work together. SPF alone can fail when a message is forwarded. DKIM is useful because its signature can survive forwarding if the message is not changed.
DMARC tells the receiving provider to check whether the identity it sees matches the one you claim in the From line. This is why copying a record from an old tutorial is risky: the correct setup depends on the domain and the services you actually use.
Do not begin with an aggressive DMARC policy because someone on a forum said it improves deliverability. A strict policy can protect your brand, but it can also reject legitimate mail if you have not found all your senders. Begin in monitoring mode, receive reports, identify every source, and move carefully.
Security and delivery both improve when the setup reflects reality.
A worked example: a sudden spam problem
Imagine a small store sends a weekly product email. For months, it reaches the inbox. Then a campaign lands in spam for many Gmail readers.
The team immediately rewrites the subject line five times. That is understandable, but it skips the useful investigation.
- Check what changed. The store imported 18,000 addresses from an old point-of-sale export and sent to all of them at once. That is a much stronger clue than the words in the subject line.
- Check list quality. Many addresses are years old. Some hard-bounce, and many never engage. The store should suppress the hard bounces, separate the old list, and ask those people to re-confirm interest before sending them normal promotions.
- Check identity. A test email shows DKIM is passing, but the new campaign links through an unfamiliar tracking domain. The team should verify that the tracking setup is legitimate and use a branded link domain where available.
- Change the next send. Instead of another full-list promotion, the store sends a genuinely helpful seasonal guide to recent customers and recent openers. It sends at a normal volume and makes unsubscribing easy.
- Watch the outcome. Bounces, complaints, clicks, and unsubscribes are compared with prior sends. If complaints stay high, the team pauses and investigates again instead of increasing volume.
Nothing in that example requires a secret deliverability tool. The recovery comes from reducing unwanted mail and restoring a consistent, trustworthy pattern. The same approach works whether the issue began with a poor import, an authentication change, or an over-eager promotion calendar.
Your first 30 days of deliverability work
Week 1: make a map
List every sending domain, From address, sending platform, and type of email. Mark each one as promotional, transactional, or personal. Send a test from each platform.
This exercise often finds a forgotten service or a From address that nobody recognises. It also tells you who needs to approve DNS changes.
Week 2: fix the foundations
Set up or correct SPF, DKIM, and DMARC. Make sure the unsubscribe process works. Confirm that hard bounces and unsubscribes are automatically excluded from future sends.
Check whether your platform supports a branded tracking domain and whether its links work correctly.
Week 3: improve the audience
Separate active subscribers from old or unknown contacts. Do not delete people simply because they did not open one email; privacy features and busy weeks exist. Instead, define a sensible inactivity window for your business, send a small re-permission campaign, and stop regular marketing to people who do not respond.
Week 4: set a routine
Choose a monthly review. Look at bounces, complaints, unsubscribes, and engagement by campaign type. Note any new tools that send from your domain.
Deliverability gets worse when it becomes an emergency-only task. A twenty-minute recurring review catches small problems while they are still small.
Questions teams ask most often
Should we use a dedicated IP address?
Not automatically. A dedicated IP gives you more direct control over its sending history, but it also means you must generate enough consistent, healthy volume to build that history. Many smaller senders do well on a reputable provider’s shared infrastructure.
Fix permission and authentication before treating an IP choice as the answer.
Will asking people to add us to contacts solve it?
It can help an individual recipient recognise your mail, but it is not a substitute for good sending practices. Earn that action by sending something people want, with a recognisable From name. Never make it sound like the reader must rescue you from spam to receive what they requested.
How quickly can reputation recover?
There is no honest universal timeline. It depends on the scale of the problem, your volume, and whether you truly changed the behaviour that caused it. The reliable path is to stop the harmful pattern, focus on engaged subscribers, and build back gradually.
A rushed “recovery blast” often makes the problem last longer.
A simple checklist
- One stable From name and address for each type of message.
- SPF, DKIM, and DMARC checked with a real test email.
- No purchased, scraped, or silently imported contacts.
- Hard bounces and unsubscribes suppressed automatically.
- Volume rises gradually, starting with engaged subscribers.
- A monthly review of complaints, bounces, and inactive contacts.
The short version
Deliverability is trust made visible in technical records and subscriber behaviour. Authenticate the domain, send to people who asked, make it easy to leave, and keep your sending pattern steady. Do those basics before worrying about clever deliverability tricks.
For current Gmail rules, check Google’s Email Sender Guidelines before a large send.
Continue learning
Related Cresca resources
External references