Modern single-binary mailing list manager
  • Go 79.3%
  • TypeScript 19.4%
  • CSS 0.5%
  • Python 0.4%
  • Dockerfile 0.2%
  • Other 0.1%
Find a file
Repository files (latest commit first)
Filename Latest commit message Latest commit date
tgiachi c5f158b664 feat(admin): held messages tab
- Add held queue table with approve and confirmed discard
- Explain how messages get held when posting is not moderated
- Refresh the tab badge and the archive after approving
- Add byte and date formatting helpers
2026-11-09 15:36:47 +01:00
admin feat(admin): held messages tab 2026-11-09 15:36:47 +01:00
docs feat: serve the public web from the daemon and document the archive 2026-11-09 15:22:50 +01:00
internal feat(adminui): embed the admin SPA and serve it next to the API 2026-11-09 15:29:12 +01:00
.gitignore feat(adminui): embed the admin SPA and serve it next to the API 2026-11-09 15:29:12 +01:00
Dockerfile feat: daemon entrypoint, YAML config and Dockerfile 2026-11-09 14:55:38 +01:00
go.mod feat(archive): parse messages into archivable entries 2026-11-09 15:18:23 +01:00
go.sum feat(archive): parse messages into archivable entries 2026-11-09 15:18:23 +01:00
parsimony.example.yaml feat: serve the public web from the daemon and document the archive 2026-11-09 15:22:50 +01:00
README.md feat: serve the public web from the daemon and document the archive 2026-11-09 15:22:50 +01:00

parsimony

A modern, single-binary mailing list manager: an evolution of Mailman.

  • Postfix delivers to parsimony over LMTP; parsimony relays through SMTP.
  • Discussion lists with member-only posting, List-* headers, one-click unsubscribe and DMARC-safe From rewriting.
  • Self-service subscribe and unsubscribe by email with double opt-in: send to list+join@domain or list+leave@domain, then reply to the confirmation.
  • Moderated lists: posts wait in a queue that the API can approve or discard.
  • VERP bounces: every recipient gets a signed return address; 3 hard bounces disable a member.
  • Archive with full-text search (SQLite FTS5) and threading. Each list has an archive_policy: private (default, API only), public (web pages) or off. Public pages hide email addresses.
  • Per-recipient one-click unsubscribe links (RFC 8058) with signed tokens.
  • SQLite storage, one YAML config file.
  • Admin REST API under /api/v1 (see docs/openapi.yaml).

Run

cp parsimony.example.yaml parsimony.yaml
PARSIMONY_API_TOKEN=<token> go run ./cmd/parsimony -config parsimony.yaml

The API is disabled when PARSIMONY_API_TOKEN is not set.

Three listeners, each configurable:

Listener Default Purpose
lmtp 127.0.0.1:2424 mail from Postfix
api 127.0.0.1:8080 admin REST API, bearer token
web 127.0.0.1:8081 public archive and unsubscribe pages ("" disables)

Put the web listener behind a reverse proxy with TLS and set base_url to its public URL: the unsubscribe links in every message use it. Keep the api listener private.

curl -H "Authorization: Bearer $PARSIMONY_API_TOKEN" -d '{"name":"dev","domain":"example.org","title":"Dev"}' localhost:8080/api/v1/lists

Postfix

Deliver the list domains to parsimony over LMTP and keep the + extensions intact, for example:

transport_maps = hash:/etc/postfix/transport
# /etc/postfix/transport
lists.example.org  lmtp:inet:127.0.0.1:2424