Somewhere right now, a perfectly good email is dying in a spam folder. Nobody sent it maliciously. Nobody wrote it badly. So what went wrong?
Email deliverability is the least glamorous part of email, and also the part that decides whether any of the other parts mattered. You can design the world's best onboarding sequence and the most fabulous promotion campaign and it will accomplish exactly nothing if it doesn't actually make it to your recipients' inboxes.
Mailbox providers are bouncers, not judges
Ask why an email went to spam and you'll often hear a list of content fixes. Too many links. The word "free" in the subject line. The wrong image-to-text ratio. So people rewrite the copy, rebuild the template, and still, that new-and-improved message lands in the same spam folder.
Content isn't nothing. Including a blocklisted link can hurt you, and an overselling subject line earns you complaints. But for most legitimate senders it's the smallest lever you have available.
Gmail, Outlook, and Yahoo aren't really evaluating whether your email is good. They're evaluating whether people who receive mail from you tend to be happy about it.
That's the main story. Almost every metric providers look at is just a different way of measuring "are recipients happy about this."
The bouncer doesn't read your poetry. The bouncer checks whether you've caused problems here before.
Email authentication: the ticket at the inbox door
Before a mailbox provider can decide how it feels about you, it has to know who you are. Authentication is the ID check at the door. It is built upon three standards, each closing a different gap:
- SPF defines a list of servers that are permitted to send for your domain.
- DKIM cryptographically signs your messages to prevent tampering.
- DMARC ties the two together, telling receivers what to do when something doesn't line up.
None of this makes your mail good, and none of it will save a bad reputation. It makes your mail identifiable, which is the prerequisite for being judged on anything else. Get it right once, and then go worry about the thing it lets you build: reputation.
Reputation: your permanent record
Reputation attaches to two things: the domain you send from, and the IP you send over.
Domain reputation follows your sending domain. It's durable, it's portable, and it's the one that really counts the most. Burn it and you can't escape by switching infrastructure, because the domain came with you. Subdomains inherit some reputation from the parent, which is why sending marketing blasts from mail.yourcompany.com instead of yourcompany.com is a kindness to your own invoices and password resets.
IP reputation follows the machine doing the sending. A dedicated IP sounds like the premium option, but it only means something if you feed it high, steady volume and your sending hygiene is impeccable. A well-run shared pool gives you the opposite: a reputation that already exists, and enough volume that one member's slip up gets absorbed rather than amplified. The catch is the "well-run" part, because a pool is only as good as the provider deciding who gets into it.
Bounce rates: please stop emailing ghosts
There are two types of bounces:
- A hard bounce means the address doesn't exist.
- A soft bounce means something temporary went wrong, like a full mailbox or a server having a moment.
Hard bounces are a signal that matters greatly for deliverability, because a list full of dead addresses is a strong hint that you didn't collect those addresses carefully. Keep hard bounces under 2%, and pay close attention to trends over time. A bounce rate creeping up usually means an aging list rather than a sudden catastrophe, which is worse, because nobody notices slow.
The non-negotiable rule: never send to a hard-bounced address again. Ever. Doing it repeatedly is how you go from "sloppy" to "suspicious", and if inbox providers put you in the "suspicious" bucket, that's a surefire way to land in the spam folder.
Spam complaints: the 0.1% rule
A spam complaint is the strongest signal that recipients are not happy to receive your email. The receiver literally pressed a button that says "I don't want this".
Because of this, spam complaints are weighted heavily. Google's guidance is to stay under 0.1% and never exceed 0.3%. Those numbers look like plenty of headroom until you do the math: at 0.3%, three complaints per thousand sends is enough to put you in trouble.
Here's what people underestimate: plenty of those complaints don't come from people who think you're a criminal. They come from people who couldn't find the unsubscribe link and picked the biggest button available. Make unsubscribing trivially easy and your complaint rate drops, which sounds backwards and isn't.
Engagement: the metric that quietly runs everything
Whether and how your recipients engage with your emails is another strong signal inbox providers consider, and it can go both ways: Opens, clicks, replies, forwards, moving a message out of spam — all positive. Deleting without reading, ignoring for weeks, marking as spam — all negative. Where your message lands depends on how that recipient, and people who behave like them, have treated your mail before.
Improving engagement rates is a targeting and a content problem: send to people who actually asked, at the frequency they were led to expect, with something in it worth the interruption. Make sure the person who only ever wanted the receipts isn't also getting the campaigns.
The practical consequence is that sending less often improves deliverability. Your least engaged segment is actively costing you reputation with your most engaged one. Pruning dormant, unengaged subscribers feels like throwing away list size, when it's really throwing away a liability.
Volume trends: surprises are bad
Mailbox providers enjoy changes about as much as your fiddle fig tree. They notice patterns and get suspicious if anything changes. A domain that sends 500 emails a day for six months and then sends 400,000 on a Tuesday looks exactly like a compromised account. Which is why it gets treated like one.
New domains and IPs need warming: start small, send to your most engaged recipients first, and ramp gradually over several weeks. Keep your ongoing volume reasonably steady. If you have a genuine seasonal spike coming, ramp into it rather than blasting it all at once.
The hard part isn't knowing this
None of what's above is complicated, the difficulty is that it never stops. Every list, every send, every month, while you also have a product to build and customers to answer, and the consequences of letting it slide show up weeks after the send that caused them.
It compounds if you send on behalf of other people. Your careful, well-behaved tenants share infrastructure with the one who just uploaded a list they bought in 2019. Their complaint rate becomes everyone's complaint rate. Their blocklisting becomes everyone's delivery delay. You find out about it when your support queue fills with people asking why their receipts stopped arriving.
The tempting fix is to give everyone their own infrastructure, and it mostly doesn't work. Dedicated IPs need steady volume that individual tenants rarely have, and a thousand separate reputations is a thousand separate warmups to babysit. The fix that does work is less glamorous: know which tenant caused the problem, and stop that one before the damage spreads. This is what we built Helo to do.
Optimize your email delivery with Helo
Everything separated by Channel. A Channel is one sending source, and Helo lets you run as many as you need under a single account. Each one carries both transactional and broadcast mail, and we track deliverability metrics for each mail type separately within each channel. When something goes wrong, only the offending mail type on the offending channel is suspended. The marketing blast that earned the complaint spike stops. The password resets and the receipts do not. Every other channel remains unaffected.
Domain management, simplified. Add a domain and Helo hands you the records to paste into DNS: DKIM keys generated for that domain, and a Return-Path that puts the envelope sender on your side and inherits our SPF authorization, so DMARC has an aligned identifier to pass on. Our verification and monitoring process will keep checking your records are in place, and will alert you whenever something is amiss. Domains can be attached to Channels in whatever combination suits you. Learn more about domain management in Helo.
Unsubscribes, handled end to end. Broadcasts go out with a one-click List-Unsubscribe header and a visible link in the body, and Helo hosts the endpoints behind both. Nobody on the customer's side builds an opt-out page, catches the POST, or has to remember that Gmail and Yahoo expect opt-outs to be honoured within two days. It's the cheapest complaint-rate reduction on this list, and a burden you don't need to think about.
Bounce and complaint suppression, enforced automatically. Hard bounces, spam complaints and unsubscribes go onto a suppression list, and Helo won't send to them again, with no additional effort required on your part. Learn more about bounces in Helo.
Guardrails for the tenant who's about to do something regrettable. Helo watches for volume anomalies, so the Channel that has sent two thousand a day all year and suddenly queues four hundred thousand gets questioned before it goes out rather than after. We also scan message content for spam risks, catching the things that get mail blocked outright: a link to a blocklisted domain, a phishing attempt, a message that pattern-matches a campaign someone else already burned. The end result is stopping the problem at send time, not explaining it at incident time.
One view of everything you send. Bounce rates and complaint rates are graphed per Channel and mail type, over time, so a drift shows up as a slope rather than as a surprise six months later. In-app banners flag the things that need attention now rather than waiting for you to go looking. And the same numbers are available through the stats API, whether you want them in your own dashboards or want to show each of your customers their own.
Where does that leave you?
Deliverability isn't a dark art, it's just a lot of small disciplines (and discipline) applied consistently: authenticate properly, keep your lists clean, make unsubscribing easy, respect engagement signals, and don't surprise anyone with your volume. Choosing a provider that takes this as seriously as we do goes a long way.
If you're ready to take control of your sending, at any scale, we'd love to work with you. If you'd rather talk it through first, get in touch. We're more than happy to go into any of this in greater detail.
Happy sending!