This post may contain affiliate links. If you buy through one, we may earn a commission at no extra cost to you. See our Affiliate Disclosure for details.
A message that lands in spam doesn't bounce. Nothing fails, no error comes back, and the send report still shows a clean 100% delivered — because delivered only means the receiving server accepted the message, not that a person will ever see it.
So the open rate sags. And the natural response is to rewrite the subject line, then rewrite it again, when the subject line was never what happened.
Email deliverability is the set of signals mailbox providers use to decide whether your mail reaches the inbox, the spam folder, or nothing at all. For a one-person list, three things account for most of it: authentication (SPF and DKIM on your sending domain, plus a published DMARC record), complaint and engagement history from real subscribers, and list hygiene — continuing to send only to addresses that still open your mail. Google and Yahoo have required authentication, working one-click unsubscribe, and low complaint rates from bulk senders since February 2024, and Microsoft applied comparable rules to high-volume Outlook.com senders in 2025. Your email platform handles part of this for you. The DNS records and the state of your list are yours, and they are where most solo newsletters are actually losing.
The three questions a mailbox provider asks about you
Filtering gets described as a black box, and the model is genuinely opaque in its details. The shape of it is not.
Every inbound message runs through roughly three checks. Is this really from the domain it claims? Do the people receiving this mail appear to want it? And does this sender behave the way a legitimate sender behaves — steady volume, real replies, few complaints?
Only the first has a definitive answer. The other two are reputation, accumulated slowly and lost quickly, and they are scored against your sending domain and IP rather than against any individual campaign. That's the part that catches people out. A single message doesn't get filtered on its own merits; it gets filtered on the history of everything you sent before it.
Which is also the good news. Reputation that was built can be rebuilt, and the inputs are boring and controllable.
SPF, DKIM, and the DMARC record most solo senders never publish
This is the technical part, it is a one-time job, and it's the one most likely to be sitting half-finished right now.
Three DNS records do the work:
| Record | The question it answers | Who actually sets it up |
|---|---|---|
| SPF | Which servers are permitted to send mail for this domain? | You, in your DNS — your platform supplies the value |
| DKIM | Was the message signed by the domain, and unaltered in transit? | Platform generates the key, you publish it in DNS |
| DMARC | What should a receiver do when SPF or DKIM fail, and where do reports go? | You, in your DNS — nobody does this one by default |
SPF and DKIM usually get done, because email platforms walk you through them during setup and nag until they're green.
DMARC is the one that gets skipped, because nothing visibly breaks without it. Since the 2024 bulk-sender rules, that changed: Google's email sender guidelines require bulk senders to publish a DMARC policy on the sending domain, and Yahoo's sender requirements mirror them closely. A starting record with p=none satisfies the requirement while telling receivers to change nothing — it just switches on the reporting so you can see who is sending mail as you. DMARC.org's overview explains the policy levels in plain terms, and moving from none to quarantine later is a decision you make with report data in hand, not on day one.
One correction worth making while you're in there: the thresholds and requirements published on those pages have been stable since February 2024, but they are living documents that get revised. Read them directly rather than trusting anyone's summary of them, including this one.
Three records, published once, that decide whether a receiver believes the mail is yours. Photo by cottonbro studio via Pexels.
Your list is louder than your subject line
Authentication gets you considered. Engagement is what gets you delivered.
Google asks bulk senders to keep the spam complaint rate reported in Postmaster Tools below 0.3%, and to aim well under that. Run the arithmetic on a small list and the number stops feeling abstract: 0.3% of a 2,000-address send is six people hitting report spam. Six. That is a bad morning, not a crisis, and it is enough to move your domain into a worse bucket for weeks.
The usual causes are unglamorous.
Addresses collected years ago from a form nobody remembers filling in. A list imported from an old CRM alongside contacts who never subscribed to anything. Subscribers who opened enthusiastically for two months in 2024 and haven't since — still counted in your list size, still dragging your engagement average down, still occasionally annoyed enough to click the spam button instead of unsubscribe.
The fix is a sunset policy, and it feels worse than it is: after a set period with no opens or clicks, stop mailing that segment. Try one plain re-engagement message, then let them go. A smaller list that gets opened outperforms a larger one that gets ignored, and this is one of the few places in marketing where deleting your own numbers is the correct move. If you're already grouping people by behavior, the mechanics overlap with what an email list segmentation setup does anyway — you're building the same engagement segments, then using them to suppress rather than to target.
Never buy a list. That one isn't a judgment call about taste; purchased addresses generate complaints and spam-trap hits at rates that no amount of good sending recovers from.
Does the platform handle this for you?
Partly, and it's worth being precise about where the line falls, because assuming the platform covers everything is how records stay unpublished for a year.
Established senders — Mailchimp, GetResponse, ConvertKit/Kit and their peers — manage the shared sending IPs, process bounces automatically, suppress hard-bounced addresses, and insert the List-Unsubscribe headers that make one-click unsubscribe work. That header is a standard, defined in RFC 8058, and it's now a requirement rather than a courtesy for bulk senders. It also has a useful side effect: an easy unsubscribe button is the thing that stops a mildly irritated subscriber from reaching for report spam instead.
What no platform does for you:
- Publish your DNS records. It generates the values; you paste them at your registrar.
- Decide who stays on the list. Suppression of unengaged contacts is a setting you configure, not a default.
- Control how often you send, or whether the content matches what people signed up for.
- Fix a domain reputation you damaged before you arrived — reputation follows the domain, not the platform.
That last point matters if you're switching tools to escape a deliverability problem. A new platform gives you new IPs, not a new domain history, and the numbers frequently look identical on the other side. Choosing between platforms is a real decision, but it's a broader email automation question about workflows and cost — not a lever for inbox placement.
Delivered means the server took the message. It says nothing about where the message went. Photo via Pexels.
The numbers you're allowed to see
You can't see your inbox placement rate. Nobody outside the mailbox providers can. But two free tools show you more than most solo senders realize exists.
Google Postmaster Tools reports domain reputation, spam rate, authentication pass rates, and delivery errors for mail you send to Gmail addresses — which, for most one-person lists, is the majority of the list. Verifying your domain takes one DNS record. The catch is volume: Postmaster suppresses data below a certain daily threshold, so a list of a few hundred will often show empty charts. Empty is not a failure, it's just a dashboard built for larger senders.
Microsoft's Smart Network Data Services does something similar for Outlook and Hotmail traffic, though it reports by IP — useful mainly if you send from your own dedicated IP rather than a shared pool.
And your DMARC record, once published with a reporting address, produces aggregate reports from receivers describing who sent mail claiming to be your domain. They arrive as raw XML, which is unreadable by design; free parsers exist, and it's worth looking at them once a quarter rather than never.
Timing barely registers next to any of this. If you're already deep in send-time optimization, that's a fine thing to tune — after your authentication passes and your list is clean. Perfect timing into a spam folder is still a spam folder.
Send one seed test before your next campaign
Here's the single check to run today, and it takes about four minutes.
Send your next campaign — the real one, not a test draft — to one Gmail address you own, before scheduling it to the list. Open it in Gmail on desktop, click the three dots next to reply, and choose Show original.
The top of that screen lists SPF, DKIM, and DMARC with a result beside each. You want three PASS lines. Anything else — a fail, or a DMARC line that isn't there at all — is your next hour of work, and it's DNS work, not copywriting.
Then note which tab it landed in. Primary, Promotions, or Spam is real information about one message to one address, which is not a deliverability audit, but it is more than you had before you looked.
저는 한국에서 직원 없이 혼자서 두 개의 소규모 사업체를 운영하고 있습니다. 견적, 회계, 마케팅, 웹사이트 관리까지 모두 제가 직접 하고 있습니다. 개발자는 아니지만, 이 사이트의 자동화 시스템은 AI 코딩 도우미를 활용하여 밤늦게까지 오랜 시간 공들여 구축했고, 모든 콘텐츠 관리 및 게시도 제가 직접 담당하고 있습니다.