How to Self-Host Listmonk Newsletter and Email Marketing on Ubuntu VPS

Introduction to Listmonk Architecture

Listmonk is a standalone, blazing-fast newsletter and mailing list manager built entirely in Go (Golang) and React. Its architecture relies extensively on PostgreSQL to store millions of subscribers, utilizing advanced indexing and JSONB fields for dynamic templating. It handles massive concurrent email delivery natively via SMTP relay bridging.

Modern system administration requires robust, scalable open-source tooling. Deploying Listmonk fundamentally shifts control away from expensive SaaS platforms and places it directly into the hands of the infrastructure engineer. This comprehensive tutorial will rigorously guide you through deploying Listmonk on an Ubuntu Linux Virtual Private Server, ensuring a production-ready, hardened environment.

Hardware Sizing & Prerequisite Checklist

Before initializing the deployment, your infrastructure must meet strict baseline requirements. Failing to provision adequate hardware will invariably result in critical service degradation or kernel out-of-memory (OOM) panics.

• Compute & Memory: Minimum 2 vCPU cores, 2GB RAM, 20GB NVMe SSD, Ubuntu 22.04 LTS, Docker, and a reputable external SMTP provider (AWS SES, Mailgun, SendGrid) to guarantee inbox deliverability.
• Operating System: A freshly installed Ubuntu Linux VPS (preferably 22.04 LTS or 24.04 LTS).
• Networking: A statically assigned IPv4 address and a registered domain name (e.g., yourdomain.com) with A records pointing to your server’s IP.
• Software Dependencies: `curl`, `wget`, `git`, and `ufw` firewall pre-installed.

Step-by-Step Linux Installation & Configuration

The contemporary standard for application deployment relies heavily on containerization. Utilizing Docker and Docker Compose ensures complete environmental parity and isolates the application layer from the underlying host OS.

Execute the following commands to install the Docker engine directly from the official repository:

sudo apt update && sudo apt upgrade -y
sudo apt install ca-certificates curl gnupg lsb-release -y
sudo mkdir -m 0755 -p /etc/apt/keyrings
curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo gpg --dearmor -o /etc/apt/keyrings/docker.gpg
echo "deb [arch=$(dpkg --print-architecture) signed-by=/etc/apt/keyrings/docker.gpg] https://download.docker.com/linux/ubuntu $(lsb_release -cs) stable" | sudo tee /etc/apt/sources.list.d/docker.list > /dev/null
sudo apt update
sudo apt install docker-ce docker-ce-cli containerd.io docker-buildx-plugin docker-compose-plugin -y
sudo systemctl enable docker --now

Listmonk requires an explicit configuration file. Generate `config.toml` supplying the database connection string and administrator credentials. Run `docker compose run –rm app ./listmonk –install` to execute initial Postgres schema setup. After successful installation, boot the stack using `docker compose up -d`.

Production Docker Compose Configuration

version: '3.7'
services:
  app:
    image: listmonk/listmonk:latest
    ports:
      - "127.0.0.1:9000:9000"
    environment:
      - TZ=UTC
    networks:
      - listmonk
    depends_on:
      - db
    command: ["sh", "-c", "yes | ./listmonk --install --config demo && ./listmonk --config demo"]
    volumes:
      - ./config.toml:/listmonk/config.toml
  db:
    image: postgres:14
    ports:
      - "5432:5432"
    environment:
      - POSTGRES_PASSWORD=listmonk
      - POSTGRES_USER=listmonk
      - POSTGRES_DB=listmonk
    networks:
      - listmonk
    volumes:
      - db-data:/var/lib/postgresql/data
networks:
  listmonk:
volumes:
  db-data:

Nginx Reverse Proxy & TLS Configuration

Directly exposing application ports to the public internet violates zero-trust architectural principles. An Nginx reverse proxy handles load balancing, HTTP header manipulation, and essential TLS termination.

sudo apt install nginx -y

Create the following configuration block at `/etc/nginx/sites-available/listmonk`:

server {
    listen 80;
    server_name newsletters.yourdomain.com;
    
    location / {
        proxy_pass http://127.0.0.1:9000;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
    }
}

Performance Tuning & Benchmark Comparison Table

Listmonk’s Go backend can route thousands of emails per minute. Navigate to the admin settings and configure your concurrent connection limits based strictly on your SMTP provider’s rate limits (e.g., AWS SES typically defaults to 14 emails/second).

To demonstrate the efficacy of this deployment, we compare the self-hosted metrics against standard industry baselines:

| Metric | Mailchimp | Listmonk (Self-Hosted) |
|---|---|---|
| Subscriber Limit | Tiered Pricing | Unlimited (DB Bound) |
| Sending Speed | Managed | 100,000+ emails/hour |
| Core Architecture | Proprietary | Golang + PostgreSQL |

Security Hardening: UFW, SSL, and Permissions

Enforce strong authentication on the Listmonk admin panel. Ensure your domain is fully verified with SPF, DKIM, and DMARC DNS records; failure to configure these will result in your self-hosted emails immediately landing in spam folders.

Deploy the Uncomplicated Firewall (UFW) to enforce a strict default-deny policy, explicitly allowing only essential traffic protocols:

sudo ufw default deny incoming
sudo ufw default allow outgoing
sudo ufw allow 22/tcp
sudo ufw allow 80/tcp
sudo ufw allow 443/tcp
sudo ufw enable

Secure the endpoint with Let’s Encrypt TLS certificates:

sudo apt install certbot python3-certbot-nginx -y
sudo certbot --nginx -d yourdomain.com --agree-tos --redirect -m [email protected]

Real-World Troubleshooting FAQ

Why are my emails landing in the spam folder?

Self-hosting the software does not bypass email reputation. You must use a reputable SMTP relay (like SendGrid or AWS SES) and strictly configure SPF, DKIM, and DMARC DNS records on your domain.

Can I import subscribers from Mailchimp?

Yes, Listmonk features a highly robust CSV importer. Map your CSV columns to Listmonk’s JSON attributes and allocate them directly to specific segments or lists.

How does Listmonk handle unsubscribes and bounces?

Listmonk injects automatic tracking pixels and one-click unsubscribe links. For bounces, it interfaces with your SMTP provider via webhooks (e.g., AWS SNS) to automatically prune hard-bounced addresses from your database.

---

Advanced Kernel & Network Optimization (Deep Dive)

Beyond the fundamental installation, extracting maximum performance from your Linux VPS requires delving into kernel-level TCP/IP stack tuning and file descriptor management. Applications that handle substantial concurrent connections, webhooks, or asynchronous database transactions inevitably encounter bottlenecks at the operating system layer if left at default configurations.

The Linux kernel’s default parameters prioritize broad compatibility over peak throughput. To optimize your deployment, you must adjust the `sysctl.conf` configurations. The `net.core.somaxconn` parameter dictates the maximum number of queued connections allowed on a single socket. Increasing this mitigates dropped SYN packets during burst traffic. Similarly, adjusting the `net.ipv4.tcp_max_syn_backlog` ensures the kernel memory buffers can accommodate massive simultaneous handshakes.

sudo sysctl -w net.core.somaxconn=65535
sudo sysctl -w net.ipv4.tcp_max_syn_backlog=16384
sudo sysctl -w net.ipv4.tcp_keepalive_time=300

Furthermore, standard file descriptor limits (`ulimit`) are often severely constrained for database and search operations. Modern applications maintain numerous persistent database connections and log file streams. Modifying `/etc/security/limits.conf` to increase the soft and hard limits for the `root` and `docker` system users dramatically enhances stability, preventing the infamous ‘Too many open files’ fatal exception during high-load scenarios.

Finally, disk I/O performance directly dictates the responsiveness of persistent volumes mapping to Postgres, Redis, or application cache layers. Switching the I/O scheduler to `mq-deadline` or `none` on NVMe storage bypasses unnecessary rotational latency optimizations, feeding data directly to the hardware controller. By combining aggressive network queuing, expansive file handler limits, and streamlined disk I/O protocols, your deployment is guaranteed to achieve enterprise-grade resilience and sub-millisecond local network response times.

In addition to kernel tuning, implementing a comprehensive monitoring strategy is paramount. Prometheus and Grafana should be deployed alongside your primary applications to scrape metrics endpoint data. Monitoring CPU wait times (iowait), memory paging rates, and Docker container CPU throttling provides actionable intelligence before system failure occurs. For logging, the ELK stack (Elasticsearch, Logstash, Kibana) or a lightweight alternative like Promtail and Loki can ingest Nginx access logs and application stderr/stdout streams, enabling rapid anomaly detection and forensic analysis during security incidents.

By rigorously applying these foundational Linux engineering principles, your self-hosted infrastructure will routinely outperform managed SaaS equivalents while maintaining absolute data sovereignty and minimizing recurring operational expenses.