Delivery is not the same as deliverability. A provider can accept your message and still route it to a folder nobody opens. The job is reaching the inbox, not reaching the server.
Email deliverability is whether a message you send actually reaches the recipient's inbox rather than being filtered into spam, promotions, or quietly dropped. It depends on four layers: identity authentication (SPF, DKIM, DMARC), sender reputation on your IP and domain, message content, and recipient engagement. A high send volume does not help if any one layer fails. Deliverability is earned over weeks, not configured in an afternoon.
The six things to understand before sending another campaign, and the reason most senders blame their content when the real problem is somewhere else.
A mailbox provider can accept your message with a 250 OK response and still file it in spam, promotions, or an updates tab you will never see opened. Deliverability measures what percentage of your sends land in the primary inbox. Delivery rate measures what percentage of sends were not bounced. The gap between those two numbers is where most senders lose their program.
Every inbox decision is made by weighing four signals. Identity proves the message really came from you. Reputation is the receiving provider's history with your IP and domain. Content is the body, subject line, and links. Engagement is what past recipients did with your mail. Fix one layer with another broken and the result is still spam.
SPF lists which servers are allowed to send on behalf of your domain. DKIM cryptographically signs the message so the recipient can verify it was not altered. DMARC tells receivers what to do when SPF or DKIM fail and reports back on who is sending as you. Without all three aligned, major providers will not place you in the primary inbox.
Receiving providers maintain a running score of your sending behavior: how often recipients open, reply, delete without reading, mark as spam, or move you to junk. A new domain has no reputation and must warm up slowly. A reputation built over years can be destroyed in a week by one bad campaign. Reputation is the single largest input to inbox placement.
Classic spam phrases, excessive capital letters, exclamation stacking, URL shorteners, and image-only messages all push a message toward the spam folder. Content filters are less important than reputation on modern providers, but a reputation-neutral message with a classic trigger phrase can still be filtered. Write like a human writing to one person.
When recipients open, reply, star, or move your message out of spam, the provider learns you are wanted mail. When they delete without reading or mark as spam, the filter learns the opposite. Engagement is the layer most senders underweight, and the one that quietly determines whether tomorrow's send lands.
Authentication is not optional in modern email. The major providers rolled out mandatory sender requirements that require bulk senders to publish SPF, DKIM, and DMARC records and to align them with the From domain. A message that fails authentication does not go to spam, it often never gets delivered at all. The three records are published once as DNS entries, but the alignment and monitoring work is ongoing.
A TXT record on your domain that lists the IP addresses and services permitted to send mail on behalf of that domain. When a receiver gets a message, it checks whether the sending IP is on the SPF list. If not, the message fails SPF. One of the most common failure modes is forgetting to add a new sending service to the record after the stack changes.
The sending service signs each outgoing message with a private key. The matching public key is published in your DNS. The receiver verifies the signature, which proves the message really came from your domain and was not altered in transit. DKIM must be aligned with the visible From domain, not the hidden envelope sender, to count toward inbox trust.
A DMARC record declares what receivers should do if SPF or DKIM fail: none (just report), quarantine (send to spam), or reject (bounce). It also tells receivers where to send aggregate reports so you can see who is sending as you. Start at none to collect data, then move to quarantine once legitimate senders are aligned.
A message can pass SPF or DKIM against a different domain than the one in the From header. That is called passing without alignment, and it does not count toward DMARC. Alignment means the authenticated domain matches the visible From domain. Most deliverability issues trace back to a service that is signed but not aligned.
Brand Indicators for Message Identification is an emerging standard that shows a verified brand logo next to the sender name in supporting clients. BIMI requires DMARC at quarantine or reject enforcement, plus a verified mark certificate. It is a trust signal, not a delivery requirement, but strong authentication is a prerequisite.
DMARC aggregate reports are XML files sent daily by receivers to the address in your record. They show who is sending as your domain, which messages pass, and which fail. Without a reporting tool to parse them, the files are unreadable. Weekly review catches new unauthorized senders and misconfigured legitimate services before they damage reputation.
Reputation is the compounding interest of your sending program. A domain with months of good behavior earns the benefit of the doubt. A domain with no history is treated as suspicious by default. The practical work is a slow volume ramp from a cold start and the discipline to keep the ramp consistent even when business pressure wants to send a hundred thousand at once.
A new sending domain should begin with a few dozen messages per day to highly engaged recipients, then roughly double daily for two to four weeks until it reaches target volume. The engaged early audience teaches the provider that mail from this domain is wanted. Skipping the ramp is the single most common cause of a brand new domain landing in spam from day one.
If you move onto a dedicated IP, that IP has no reputation either. The IP warmup runs in parallel with any domain warmup and follows the same shape: start low, grow steadily, send to engaged recipients first. Shared IPs skip this because the pool already has history, but a bad neighbor on a shared pool can drag your mail down with theirs.
A sender that goes from one hundred messages a day to one hundred thousand on launch day looks like a compromised account to a receiving provider. Keep daily volume within a reasonable band of the trailing average. If a big campaign is coming, schedule the ramp in advance over the preceding days rather than sending the full load at once.
Hard bounces, spam traps, and role addresses (info@, sales@, admin@) damage reputation disproportionately. Clean the list before every send: remove hard bounces immediately, remove soft bounces after a few retries, and suppress addresses that have not engaged in six to twelve months. A smaller clean list outperforms a larger dirty list every time.
Spam traps are addresses placed on the web or recycled from abandoned accounts to detect senders who scrape or do not maintain their lists. Hitting even one pristine trap can tank reputation. The defense is simple: never buy or scrape lists, confirm new subscribers, and clean out inactive addresses before they become recycled traps.
Several public blocklists aggregate reports of suspicious sending IPs and domains. Landing on one can block mail across many receivers at once. Monitor your sending IP and domain against the major lists, respond quickly if listed, and understand that most delistings require fixing the underlying behavior first.
Cold outbound and privacy features changed what the open rate actually measures. The reports your email infrastructure gives you are still useful, but reading them literally will mislead you. Here is how modern deliverability metrics behave and what to look at instead when the familiar numbers stop telling the truth.
A cold outbound sequence sends to recipients who did not opt in. Expect lower opens, higher deletes, and a higher spam-complaint rate than opt-in marketing. The way to send cold mail without wrecking reputation is to send small volumes from separate dedicated subdomains, personalize heavily, and treat every reply as the signal that keeps the program alive.
Transactional mail (receipts, password resets), marketing mail (newsletters, campaigns), and cold outbound should each send from a separate subdomain of the root. That way a bad cold sequence cannot drag down the password-reset deliverability, and the finance team's billing mail is not competing with the launch campaign for inbox placement.
Mail Privacy Protection, enabled by default on the largest consumer client, pre-fetches tracking pixels so the provider sees an open whether the recipient actually read the message or not. Open rates look higher than they really are. Treat open rate as a weak signal and lean on reply rate, click rate, and reply-plus-click combined as the honest engagement metrics.
A click requires a human choosing to click. Click rate is less inflated than open rate and more honest about whether the audience is paying attention. Watch click-to-open as a secondary metric, remembering that opens are inflated so the ratio looks lower than it used to. A healthy marketing list clicks a few percent of what it opens, and the direction over time matters more than the absolute number.
Spam complaints are the hardest signal a recipient can send: this mail should not exist. Keep the complaint rate well under one in a thousand sends. A sudden spike means the content, cadence, or audience changed in a way the recipients did not want. Pause the send, investigate, and do not resume until the cause is understood.
A reply is a human writing back. Providers watch reply rate because it is the clearest indicator of real engagement. Program outbound to invite replies, make it easy to answer in one sentence, and track reply rate as the primary health metric on cold sequences. A reply rate climbing week over week beats any pixel number on the dashboard.
A CRM does not replace your email infrastructure. The CRM talks to the infrastructure. The job of a CRM in deliverability is to keep the sending list clean, to catch bounces and complaints, to detect replies, and to prevent the same person from receiving the same message twice from different automations. When those jobs are wired correctly, the infrastructure gets to focus on what only it can do.
Every unsubscribe, every hard bounce, every spam complaint, and every manual opt-out should land in one global suppression list the CRM honors on every send across every campaign, workflow, and sequence. A per-campaign suppression leaks: a contact who unsubscribed from one newsletter should not get the next product launch from the same company.
Hard bounces (permanent, address does not exist) should be removed from active sending immediately on the first occurrence. Soft bounces (temporary, mailbox full or server down) can retry a few times before being treated as permanent. The CRM should receive bounce webhooks from the infrastructure, record the bounce type on the contact, and update suppression automatically.
When a cold sequence or nurture flow is running and the recipient replies, the next step should not fire. The CRM listens for inbound mail on the sales inbox, matches it to the right contact and sequence, and pauses the automation so a human can take the conversation forward. Nothing damages trust faster than a scheduled follow-up that lands after a reply.
The CRM records where the consent came from (form, import, API, chat), when it was captured, and what the recipient agreed to receive. That evidence matters for CAN-SPAM, for recipient trust requests, and for internal audits. A contact without a traceable opt-in should default to a stricter sending policy, not a looser one.
Deliverability dies when one person is on five lists and gets five messages in one week from the same company. Frequency capping at the contact level, not the campaign level, caps total sends per recipient per time window. Marketing, product, lifecycle, and sales touches all count against the same cap. The CRM is the only place with that cross-channel view.
The highest-leverage deliverability move is sending to fewer, better-matched recipients. Segmentation based on CRM data (engagement recency, lifecycle stage, product usage, past purchase) targets the people most likely to open, reply, and click. Smaller sends to high-intent segments build reputation faster than blast sends to the whole list.
Strkr pairs the CRM with marketing, sequences, and suppression in one tool, so one global do-not-send list applies across every campaign, workflow, and sales touch. Reply detection pauses sequences automatically, and bounce webhooks keep the active list clean on their own.
Inbox placement above ninety-five percent is strong for opt-in marketing. Transactional mail should land near one hundred percent. Cold outbound deliverability varies widely by vertical and target. Delivery rate (the server accepted it) and deliverability rate (the inbox received it) are different numbers, and the one that matters is inbox placement, not server acceptance.
The common causes, in order of frequency: authentication is incomplete or not aligned (SPF, DKIM, DMARC), the sending domain or IP has weak or damaged reputation, the content contains known spam triggers, the recipient list has decayed and includes traps or disengaged addresses, or the sending volume ramped faster than reputation could support. Fix in that order.
A conservative warmup runs two to four weeks from the first send to full target volume. Start with a few dozen daily sends to the most engaged recipients, grow steadily, and keep the ratio of positive engagement (opens, clicks, replies) high throughout. Faster ramps work occasionally, but the risk of starting with a bad reputation on day one is not worth the time saved.
Shared IPs make sense for small to mid volumes because the pool already has established reputation, provided the pool is well managed. Dedicated IPs make sense once monthly volume is high enough to maintain the IP's own reputation (often a few hundred thousand sends per month at minimum). Dedicated below that threshold often performs worse than shared because the IP never earns a reliable reputation.
It still matters directionally but not literally. Mail Privacy Protection pre-fetches tracking pixels, so opens are inflated for consumer mailboxes. Use open rate to compare campaigns against each other within the same audience, but do not trust absolute numbers. Lean on click rate, reply rate, and spam complaint rate for the honest signals that still move inbox placement.
Continuously for hard bounces (immediately on bounce), monthly for soft bounces that keep failing, and quarterly for engagement-based suppression (people who have not opened or clicked in six to twelve months). A smaller engaged list beats a larger stale list for both deliverability and conversion. The compounded loss from one spam-trap hit outweighs any gain from keeping dead addresses on file.
Delivery rate measures what percentage of your sends were accepted by the receiving server rather than bounced. Deliverability rate (also called inbox placement) measures what percentage actually reached the primary inbox versus spam, promotions, or other filtered folders. A ninety-nine percent delivery rate with a sixty percent inbox placement means forty percent of your mail landed somewhere nobody looks.
A CRM supports deliverability by maintaining one global suppression list, handling bounces and complaints automatically through webhooks from the sending infrastructure, pausing sequences on reply, enforcing frequency caps per contact across channels, and enabling segmentation that targets engaged recipients first. The CRM does not replace the infrastructure, it keeps the list and the behavior clean so the infrastructure can do its job.
No sales call, no migration consultant, no four-month implementation. Enter your card, get 14 days of the full Pro tier, cancel any time before day 14 with zero charge. Spin up a workspace, import your CSV, and have something useful before lunch.
