Direct answer

If your newsletter keeps landing in the spam folder, the fix is almost always a stack of small problems, not one dramatic mistake. Inbox providers look at three things, in roughly this order: can they trust who sent the message, does your list want it, and has your sending pattern looked healthy lately? Work through them in that order and you stop guessing.

This checklist is built for independent newsletter writers running solo or with a small team. It assumes you are sending from a newsletter platform (such as Beehiiv, Substack, Ghost, Buttondown, MailerLite, ConvertKit or MailPoet) and you own the domain you send from, or you are planning to. The same workflow applies if you later migrate to a different platform.

The diagnosis order

Inbox placement is decided by the receiving server in milliseconds, but the reasoning falls into a stable sequence:

  1. Authentication: Are SPF, DKIM and DMARC set up for your sending domain?
  2. Identity: Does the From name and From address look like a real person or publication, not a random string?
  3. List health: Are the people on your list still engaged, and did they actually opt in?
  4. Content signals: Does the message itself look spammy in body, links and formatting?
  5. Reputation: How has your domain and IP behaved over the last weeks and months?

If you only address layer 5 (reputation), you are treating a symptom. Layers 1 to 4 are where independent writers usually win back their inbox placement fastest.

The deliverability checklist

Use this as a weekly or per-issue pass. Copy it into your publishing workflow. Each item below is a small, independent action, so you can fix them one at a time.

1. Authentication setup (SPF, DKIM, DMARC)

These three DNS records tell receiving servers that you, and not an impersonator, sent the message. In February 2024, Gmail and Yahoo began requiring DKIM and DMARC for bulk senders (generally 5,000 or more messages per day), and other providers already expected authentication before that. Major platforms like MailPoet and ActiveCampaign actively recommend all senders set up DKIM and DMARC regardless of volume.

  • SPF: A TXT record that lists which servers are allowed to send email for your domain. Your newsletter platform gives you the value to paste into your DNS host (Cloudflare, Porkbun, Namecheap, your registrar, etc.). One SPF record per domain, under ten DNS lookups total when you combine tools.
  • DKIM: A second TXT record (or CNAME in some setups) that adds a cryptographic signature to every outgoing message. The receiving server checks the signature against your DNS to confirm the message was not tampered with. Modern best practice is a 2048-bit key where your platform supports it.
  • DMARC: A TXT record at _dmarc.yourdomain.com that tells receivers what to do with messages that fail SPF or DKIM, and where to send aggregate reports. Start with p=none while you learn, then move to p=quarantine and finally p=reject once you are confident legitimate mail passes.

Quick ownership rule: if you own the domain, you own these records. If your newsletter is sending from yourname.platform.com, you do not control them, and that limits your ceiling on deliverability.

2. Sender identity basics

Inbox providers reward emails that look like they come from a stable, identifiable source.

  • Use a real From name, not a slogan or emoji string.
  • Send from an address at a domain you own (for example hello@yourdomain.com), not from a generic platform subdomain if you can avoid it.
  • Reply-to should be a real mailbox someone checks, ideally the same domain.
  • Add an unsubscribe link in every send, including one-off campaigns. Most platforms handle this automatically.

3. List hygiene habits

A clean list protects your reputation more than any other single habit. Independent writers tend to grow lists quickly through guest posts, collaborations or social launches, then never prune. Recipients who never open become a slow drag on your sender score.

  • Run a re-engagement campaign two to four times a year: ask inactive subscribers to confirm they still want the newsletter, then suppress anyone who does not respond after one or two reminders.
  • Remove hard bounces immediately. They are a clear signal to receiving servers.
  • Watch soft bounces that repeat for the same address; treat them as soft-hard and remove after a few sends.
  • Avoid buying or scraping lists. Even a small percentage of spam-complaint addresses can sink a domain.
  • Tag your sign-up source so you know which channels produce engaged readers.

4. Content and design signals

Content signals are softer than authentication, but they still matter. The goal is to look like a normal publication, not a 2014 bulk emailer.

  • Keep the text-to-image ratio reasonable. One image per section is fine; a wall of tracking pixels is not.
  • Write your own subject line. Avoid all caps, multiple exclamation marks and spam-trigger words like “FREE!!” or “Act now.”
  • Personalize the From name and the first line where your platform supports it.
  • Use a clear, single primary call to action. Five competing links confuse both readers and filters.
  • Avoid URL shorteners in newsletters. Receiving servers prefer the actual destination.
  • Keep HTML clean. Heavy use of tables, hidden text, or background images is a classic spam-classic signal.
  • Send from a stable IP reputation pool when possible. Some platforms offer a dedicated IP at higher tiers; for most independent writers a shared pool from a reputable platform is fine.

5. Reputation management

Sender reputation is the long memory of your sending domain and IP. You build it slowly and lose it quickly.

  • Warm up new domains. Do not start a brand-new domain by sending 10,000 emails on day one.
  • Be consistent. Pick a cadence (weekly, biweekly) and roughly stick to it.
  • Watch complaint rates. Anything over roughly 0.3 percent (three complaints per thousand sends) is a yellow flag, and over 0.5 percent is a red flag in the industry.
  • Monitor blacklists occasionally. A single listing is not fatal, but recurring listings mean a list or content problem.

Testing tools you can use before you send

You do not need to guess. There is a free tier for almost every check that matters.

  • DNS record lookups: MXToolbox, EasyDMARC, dmarcdkim.com and the SPF/DKIM record checkers from EasyDMARC let you paste your domain and see whether your SPF, DKIM and DMARC records exist and parse correctly.
  • Inbox placement testing: Mail Tester (mail-tester.com), GlockApps and similar services send a copy of your campaign to a panel of seed inboxes across Gmail, Outlook and Yahoo, then show you a spam score and content flags. Send a real draft, not a fake one, so the test reflects your actual template.
  • Blacklist checks: MXToolbox’s blacklist lookup, MultiRBL and others check your sending IP and domain against common blocklists.
  • DMARC reporting: Once your DMARC record points to a reporting address (an rua tag), you start receiving XML reports showing who is sending mail claiming to be from your domain. Services like EasyDMARC, Postmark’s DMARC tools and dedicated dashboards help you read them without parsing XML by hand.

Treat these tools as a habit, not a one-off. Run them after any major change: switching newsletter platforms, adding a new sending tool, or recovering from a deliverability dip.

What travels when you change platforms

Migration is the moment a lot of deliverability setups quietly break. Here is what you actually keep versus what you have to redo.

  • Your domain and DNS records travel with you. SPF, DKIM and DMARC belong to the domain, not the platform. If you stay on the same domain, your records stay valid; you only need to update them if your new platform asks for different values.
  • Your subscriber list travels, in a CSV export from your old platform. What does not travel automatically is engagement history, custom fields and tags. Re-import only what you actively use.
  • Your reputation is partially portable. Reputation is tied to the domain and the IP, not the platform brand. If you keep the same domain and the new platform sends from clean IP pools, you keep most of what you built. If you switch domains as well, you start close to zero and have to warm up again.
  • Your templates and design typically need a rebuild. Most platforms do not import the exact HTML, so plan a half-day for a visual pass after migration.

A practical migration order: set up DNS on the new platform first, send a small test campaign to your own addresses across Gmail, Outlook and Yahoo, then move the full list, then run the testing tools above against a real campaign.

Frequently asked questions

Do I need all three of SPF, DKIM and DMARC? Yes, in practice. SPF and DKIM prove the message is authentic; DMARC ties them to your visible From address and tells receivers what to do when something fails. Without DMARC, you are leaving the decision entirely to each inbox provider.

Is a p=none DMARC record doing anything? It is doing monitoring only. It does not block spoofed mail on its own. The value is that you start receiving reports, which tell you whether your legitimate mail is passing and who else is trying to send as you. Then you move to p=quarantine and eventually p=reject once you trust the data.

Can I skip this if I am sending from a platform subdomain? You can, and many independent writers do at first. The trade-off is that you do not control your authentication ceiling, and migrating off that platform later is harder. Buying a domain and setting up three DNS records is a one-afternoon project that pays back for years.

How long does it take to recover after a spam-placement incident? It depends on the cause. Fixing authentication and cleaning a list usually shows results within a few sends. Rebuilding a damaged domain reputation from scratch can take weeks of consistent, clean sending. If the domain itself is the problem, retiring it and starting fresh on a new domain with warm-up is sometimes faster than repairing it.

What is the single highest-leverage habit for independent writers? List hygiene. A smaller, engaged list on a properly authenticated domain will outperform a large, dormant list every time, in inbox placement and in actual revenue.

A short weekly routine

If you only have thirty minutes a week, do this:

  1. Glance at your bounce and complaint rates from the last send.
  2. Send a test campaign to one Gmail, one Outlook and one Yahoo address you control, and check that all three arrive in the inbox.
  3. Run your domain through a free SPF/DKIM/DMARC checker once a month, or any time you add a new sending tool.
  4. Schedule the next re-engagement pass before you forget.

That is the entire workflow. None of it is technical beyond pasting a few DNS records. The discipline, not the complexity, is what gets independent newsletters out of the spam folder.

Sources