How deliverability works
Every message you send is judged twice. First the receiving mail server decides whether to accept it at all, which produces your delivery rate. Then, having accepted it, the provider decides where to file it — main inbox, a promotions tab, or the spam folder. Deliverability covers both decisions, and the second one is where most email quietly disappears.
Providers make that call from three kinds of signal. Identity: do your email authentication records prove the message really came from your domain. History: how have recipients treated your mail before, measured through opens, replies, deletions without reading, and complaints. Content: does the message look like the mail people asked for, or like something bulk and unfamiliar.
Those signals attach to your sending domain and sending infrastructure, not to a single campaign. One bad send does not usually sink you, but a pattern does, and recovering takes far longer than damaging it did.
Why deliverability matters
It sits underneath every other email number you report. An open rate is a share of what was delivered, so a message filtered into spam never shows up as a failure — it shows up as a smaller audience that seemed less interested. That makes poor deliverability look like poor creative, and teams end up rewriting subject lines when the real problem is a missing DNS record.
It also decides whether the mail you cannot afford to lose gets through. Order confirmations, password resets and enquiry replies travel the same road as promotions, and a domain that has been marked down for bulk sending drags those with it.
Common mistakes with deliverability
Buying or importing a list is the most damaging, and it is still common. Addresses collected without permission produce complaints and can include spam traps, which are treated as proof that you did not obtain consent.
After that comes sending from a domain with no authentication in place, mailing everyone regardless of whether they have opened anything in years, and hiding the unsubscribe link. A hidden unsubscribe does not reduce departures; it converts them into complaints, and a complaint is far more expensive than an unsubscribe.
The last is assuming the sending platform handles it. A reputable provider gives you working infrastructure and useful reports. It cannot fix who you send to or how often, and those are the parts that decide the outcome.
How to act on it
Start with the technical foundation, because it is finite work with a clear end: publish SPF, DKIM and DMARC for the domain you send from, and use a dedicated sending subdomain so bulk mail is judged separately from ordinary correspondence. Verify the records rather than assuming the platform wrote them correctly.
Then work on behaviour. Send to people who asked, at a frequency you can sustain, and remove addresses that have stopped engaging before a provider does it for you. Watch the complaint rate and the delivery rate together, split by mailbox provider, since problems almost always show at one provider first. For a Nepali list where most subscribers read on a phone over a patchy connection, a light, fast-loading message that carries its point in text is also easier for filters to trust.
