Newsletter software: what a small list actually needs

Newsletter software all looks the same at the demo stage: an editor, a list, a send button, and a chart afterwards. The differences appear when the list grows past the free tier, when a send lands in spam, and when you decide to leave and discover what the export actually contains.

For a small list — a few hundred to a few thousand people — the useful comparison is short.

The four things that matter

• Deliverability practice. Does the provider require domain authentication with SPF, DKIM and DMARC, and does it police its own senders? A platform that lets anyone blast an unverified list is sharing its reputation with you.
• Billing shape. Almost everyone charges by subscriber count, and most keep counting unsubscribed and bounced addresses until you clean them. Ask what counts before you compare prices.
• Consent handling. Signup with proof of when and where consent was given, a visible unsubscribe, and automatic suppression of anyone who opts out.
• Export quality. Contacts with consent dates, unsubscribes and engagement history — in CSV. Without unsubscribes, your exported list is legally unusable.

The number that decides your bill is not your subscriber count today — it is the count in twelve months, including the addresses you never clean. A list hygiene habit is worth more than a discount: remove hard bounces immediately, and people who have not opened anything in a year.

What you can skip early

Visual automation builders, lead scoring, multivariate testing and predictive send-time optimisation are priced for teams sending millions. With a small list they mostly produce configuration work: a welcome sequence of two emails and a plain monthly send will outperform an elaborate flow that nobody has the volume to tune.

The same goes for design. A newsletter that looks like a personal email tends to be read; a heavily designed template tends to be scanned and, in some clients, mangled. Start plain, add structure only where it genuinely helps.

Running the first sends

1. Authenticate the sending domain — SPF, DKIM and DMARC published and verified — before importing anyone.
2. Use a subdomain for the newsletter if you also send receipts or password resets from the same domain, so a bad campaign cannot affect the mail that must arrive.
3. Import only addresses that consented, with the source and date recorded. An inherited spreadsheet is a liability.
4. Warm up: send to the most engaged few hundred first and grow volume over days rather than mailing everyone from a cold domain.
5. Put the unsubscribe link where people can see it, not in six-point grey. Recipients who cannot unsubscribe press the spam button instead.
6. Read complaints and unsubscribes before opens. They tell you whether the message was welcome; opens increasingly do not.

Worth being clear about a boundary here: Ettex Mail is not a bulk sending platform, and a newsletter to thousands of subscribers belongs in a dedicated one. What Ettex Mail covers is the mail your business runs on — mailboxes on your own domain sending signed mail over real SMTP with DKIM, a unified inbox with smart categories, team addresses like hello@, filters and rules, per-address signatures, snooze and follow-ups, scheduled send, reusable reply templates with sixteen transactional layouts, and instant search across accounts. Replies to your newsletter land there, which is where the actual conversations start.

Mistakes that cost a list

• Importing a purchased or scraped list. The complaints damage your domain long after the list is deleted.
• Sending the first campaign to everyone from a brand-new domain.
• Letting bounced addresses accumulate because they are counted as subscribers you pay for anyway.
• Sending marketing and transactional mail from the same subdomain.
• Choosing a platform whose export omits unsubscribes, which quietly traps you.

Choosing the tool is the easy half. Whether the messages arrive at all depends on email deliverability — the domain records, the sending history and how quickly you remove people who never open. A perfectly built newsletter from an unauthenticated domain lands in spam and reports the same open rate as one nobody wanted.

Two things underneath the tool decide the result. Email deliverability determines whether the message arrives at all, and spf dkim dmarc are the domain records that decide it — a well-built newsletter from an unauthenticated domain lands in spam.

For a small list, newsletter software is a deliverability and consent tool with an editor attached. Get those right, keep the list clean, and the feature list barely matters.