Run a Newsletter From Your Self-Hosted Blog

A newsletter is the most durable connection you can build with readers. Search rankings shift and social feeds re-rank overnight, but an email list is a direct line that no algorithm sits between. The question is who actually holds that line. On hosted platforms, you write the words but the platform owns the relationship. This guide explains why a self-hosted blog newsletter changes that, how Inkwell now runs the whole loop from signup to send, and the part that is still your job.

Renting versus owning your list

Substack, Mailchimp, and their peers are genuinely convenient. They handle deliverability, give you a polished editor, and get a beginner sending in minutes. That convenience is real and worth acknowledging.

But on a hosted platform your subscribers live in someone else's database under someone else's terms. Pricing tiers change, export can be awkward, and a policy decision you did not make can reach your audience before you do. Owning your content rather than renting it applies to your list just as much as your posts. The email addresses people trusted you with should sit in infrastructure you control.

What owning the list gives you

• Custody of the list. Subscriber records live in your own SQL Server database, under your backups and your access rules.
• Your own sender identity. Confirmation and unsubscribe mail goes through SMTP credentials you choose.
• No per-subscriber tax. Growing the list costs nothing beyond your own hosting and whatever your SMTP provider charges to send.
• Privacy by default. No third party sits between you and the people who subscribed.

Building the list

A public subscribe form collects addresses with double opt-in: a new subscriber gets a confirmation link by email and is only added once they click it. Confirmed subscribers appear in an admin subscriber list, and a member directory lets you segment people with labels. All of that mail goes through the SMTP server you configure, and if SMTP is not configured the platform says so rather than pretending to send.

Writing and sending an issue

Since v1.0.8, Inkwell also sends the newsletter itself, from Admin, Newsletter:

• Write the issue. A subject, preview text, an introduction in Markdown, and up to six of your posts shown as cards with image, summary and link.
• Check it first. Preview the email and send a test to yourself. Sending asks you to confirm the number of recipients, and to type SEND for five or more.
• Delivery in the background. Copies go out in batches (50 a minute by default) through your SMTP server. A failed copy is retried, the reason appears in the send log, and Stop sending cancels whatever has not gone out.
• Unsubscribing that respects readers. Every copy has the subscriber's own unsubscribe link and one-click unsubscribe headers, so inbox providers can show their own Unsubscribe button. Opening the link asks before acting, so a mail scanner that follows links cannot unsubscribe anyone.

The strongest newsletters are the ones where the writer, not a platform, holds the list.

What it deliberately does not do

There are no tracking pixels and no rewritten links, so you will not get open or click rates. That is a choice in favour of your readers' privacy, and it keeps the newsletter consistent with a blog that runs no third-party tracker. Sending is available on single-site installs, not in multi-tenant cloud mode, and there is no paid-subscription feature, so charging readers still needs a separate payment service.

Deliverability is now your job

Owning the sender means owning its reputation. Before your first issue, set up SPF, DKIM and DMARC for the sending domain, or mail is likely to land in spam. Many publishers send through a transactional email provider for this reason; the batch size setting lets you stay inside your provider's rate limits.

Consent and double opt-in

Owning your list comes with owning the responsibility to build it honestly. Double opt-in protects your deliverability by keeping typo and bot addresses off your list, and it keeps you on the right side of consent expectations. Because subscriber data stays in your own database, signup is privacy-respecting from the first click.

Getting set up

Configure SMTP once and both signup and sending work. The SMTP settings in the documentation list every key, including the newsletter batch size. If you would rather hand the deployment and SMTP setup to someone else, our services can stand the platform up for you.

• #newsletter
• #publishing
• #email
• #self-hosting