Smart. Focused. Email.
Fast, cross-platform email designed to filter out the noise - so you can focus on what's important.
Definition
💡 Email deliverability is about whether the emails you send actually reach someone's inbox, instead of landing in spam or not arriving at all. It's not about whether you hit send. It's about what happens after. Deliverability isn't one setting you flip. It's the combined result of your domain's authentication, your sending reputation, and how people respond to your emails over time.
Who needs to worry about this
Most people never think about deliverability, and honestly, most people don't need to. If you're emailing from a regular Gmail or Outlook address, the provider handles the reputation and authentication side for you.
This one's really for a narrower group: founders, consultants, and small teams sending outreach or client communication from a custom email domain (yourname@yourcompany.com). The moment you're sending from your own domain, you've inherited responsibility for proving to Gmail, Outlook, and everyone else that your mail is legitimate. Get it wrong, and a perfectly reasonable follow-up to a prospect unfortunately lands in their spam folder. You'll never know it happened. They'll just never reply.
That's the real cost here. Not a bounce you can see, a silence you can't explain.
What determines whether an email lands in your inbox
Four things, working together.
Authentication. DKIM cryptographically signs your outgoing mail so receiving servers can confirm it actually came from your domain. DMARC tells those servers what to do if that signature doesn't check out. Without both configured, providers have to guess whether your mail is legitimate, and their default guess leans skeptical.
Sender reputation. Your domain and sending IP build up a track record over time, based on spam complaints, bounce rates (the non-delivery reports you get when a message fails outright), and engagement. A brand-new domain sending its first bulk campaign looks suspicious by default, the same way a new credit history gets a lower limit.
Recipient engagement. If people open and reply to your emails, that's a signal you're wanted. If they delete without opening, or worse, mark you as spam, that signal compounds against you fast.
Content and structure. The same spam filter logic that flags junk mail also nudges legitimate senders. Excessive links, spammy phrasing, or a mismatched sending domain can drag a real email into the spam folder right alongside actual junk.
There's also a threat that makes all four of these matter more: email spoofing. When someone fakes your domain to send phishing attempts, it's your reputation that takes the hit, not just theirs. Proper authentication is what lets receiving servers tell the difference.
Checking (and fixing) your deliverability
If you're sending to Gmail addresses at any real volume, Google's Postmaster Tools is the closest thing to a direct line into how Gmail sees your domain. It shows spam rate, reputation, and authentication status, straight from Gmail's own data, not an estimate.
For a broader domain check, MXToolbox's email health tool runs your domain against dozens of blacklists and confirms whether your DNS, SPF, DKIM, and DMARC records are actually set up the way you think they are. A reverse DNS lookup is one of the specific checks worth running here, since a mismatched reverse record is a common, invisible reason mail gets flagged.
None of this lives inside your email client. Deliverability is a domain and sending-infrastructure problem, tied to how your SMTP server and DNS records are configured, not something Gmail, Outlook, or Spark settings can fix for you. If you're using a marketing platform to send from your domain, most of them walk you through the DNS setup during onboarding.
Where deliverability problems usually start
Why did my email suddenly start going to spam when it never did before?
Usually a reputation shift: a spike in complaints, a jump in bounce rates, or a sudden change in sending volume. Providers watch for anomalies, not just static rules.
Do I need DKIM and DMARC if I only send a few emails a day?
Even low volume benefits from having them configured correctly, since missing authentication is one of the fastest ways to look suspicious to a filter, regardless of how much mail you send.
Can one bad email campaign hurt my deliverability long-term?
Yes, if it generates enough spam complaints or bounces. Reputation builds slowly and can drop quickly, which is why testing with a smaller list before a big send is worth the extra step.
Is deliverability the sender's problem or the recipient's?
Entirely the sender's. If you're the one receiving fewer emails than expected, that's more likely a spam filter or inbox organization question, not a deliverability one.