Bulk Mailer | Self-hosted bulk email with LDAP import

Recipients from anywhere

Type them in, paste a block (Jane Doe is understood), upload a CSV with the delimiter and columns detected for you, or import from a directory. Unknown CSV columns survive as extra template variables.

LDAP and Active Directory

Named connection profiles, configurable attribute mapping, paged search for large directories, and group imports by DN including nested groups. A list can be kept in sync with the search that filled it.

How list sync works

Templates that cannot run away with you

Per-recipient placeholders rendered by a sandboxed Jinja environment. A missing value renders empty rather than failing the run, and a template cannot reach into the application.

A dry run that proves it

Renders and validates every message for every recipient and delivers nothing. Template mistakes surface in the log before anyone receives anything.

Why this is the step to not skip

Sending you can watch

One reused SMTP connection, a throttle in messages per minute, live progress, pause, resume, cancel, and retry-only-the-failures. Progress lives in the database, so a restart resumes where it stopped.

Unsubscribes handled

A one-click link plus List-Unsubscribe headers. Unsubscribed addresses are skipped automatically by every later campaign - you cannot forget.

Running in one command

bash

docker run -d -p 8000:8000 \
  -e SECRET_KEY=$(openssl rand -base64 36) \
  -e ADMIN_PASSWORD=choose-one \
  -v mailer-data:/data \
  ghcr.io/timothestoifl24/bulk-mailer:latest

Open http://127.0.0.1:8000 and sign in as admin. The full walkthrough, including a Compose stack with PostgreSQL, is in Setup.

Before a large run

This tool will happily send to every address a directory returns. It has no opinion about whether it should.

Sending responsibly

Check the throttle against your mail server's rate limit. Do a dry run. Send a test to yourself. Make sure the recipients actually expect the message.

The unsubscribe link is in the default template for a reason — keep it.

Where to go next


Guide	A first campaign, start to finish
Screenshots	Every screen, before you install anything
Setup	Docker, Compose, or from source
Advanced config	PostgreSQL, LDAP sign-in, list sync, deployment
Upgrading	Versioning, schema changes, what to check
FAQ	The questions that come up
Contributing	Development setup, tests, releases

Guide

A first campaign, start to finish

Screenshots

Every screen, before you install anything

Setup

Docker, Compose, or from source

Advanced config

PostgreSQL, LDAP sign-in, list sync, deployment

Upgrading

Versioning, schema changes, what to check

FAQ

The questions that come up