Run Sympa for mailing lists and bulk posts
Meet Sympa's Perl, SQL, MTA, and web requirements, configure a list domain, and manage subscriptions, moderation, and archives through its API.
Reviewed
Sympa is a mailing-list manager: members post to a shared address, and Sympa redistributes the message while managing subscriptions, moderation, and archives. Choose it for discussion lists and institutional communities. It is not a newsletter editor, and its output is not a campaign edition with a visual template and subscriber analytics.
This distinction decides the architecture. Sympa owns list membership and message redistribution, but it requires a separate mail transfer agent (MTA) to deliver mail. It also requires Perl, an SQL database, and an HTTP server. The Sympa requirements and installation manual are the primary references.
Prerequisites
- A POSIX-based Unix-like host. Sympa does not support Microsoft Windows.
- Perl 5.16 or later; recent Perl 5 is recommended.
- MySQL/MariaDB, PostgreSQL, Oracle, or SQLite. A dedicated database server is recommended even though it can share one.
- A working MTA: Sendmail, Postfix, Exim, or OpenSMTPD are reported working. Sympa does not replace the MTA.
- An HTTP server such as Apache, lighttpd, or nginx for the web interface.
- At least one mail domain with appropriate DNS records, including MX, and inbound/outbound SMTP connectivity.
The project is licensed under GPLv2-or-later; the source notice states the grant.
Install the pieces in order
The documented installation sequence is dependency modules, initial configuration, database, logging, MTA, HTTP server, then service startup. Binary distributions may prepare part of the configuration for you; check before repeating it.
With Sympa 6.2.70 or later, generate the initial configuration with:
sympa config create
For earlier releases, or for a deliberately minimal file, the manual shows a sympa.conf containing at least:
domain mail.example.org
listmaster your@e-mail.addr.ess,other@email.addr.ess
domain is the primary list domain. listmaster is a real person’s address and must not forward to an address managed by Sympa. Then create the database schema, configure the MTA to hand list mail to Sympa, and configure the web server.
Start and check the service with your init system:
systemctl start sympa.service
systemctl status sympa.service
Open https://web.example.org/sympa, use the first-login flow, and request the listmaster password. A running process is not enough: send a message to a test list and confirm redistribution, archive creation, and a moderation decision.
Model list privileges before integrating
Sympa’s API is not a generic send key. Its SOAP/HTTP API exposes operations such as reviewing membership, subscribing, adding members, and creating lists. Authorization follows the same scenario rules as the mail and web interfaces.
That means an application integrating with Sympa must model who may administer which list, not merely authenticate to the service. A backend that can create a list is not automatically permitted to post to it or to read its archive. Map the roles explicitly and test denied operations, not only successful ones.
Operate the list service
Monitor four separate things:
- MTA queue health. Sympa hands messages to the MTA; a stuck MTA queue is not a Sympa bug, and restarting Sympa will not clear it.
- Database health. Membership, archives metadata, and scenarios depend on it.
- Spool and archive storage. Plan capacity and backup. A database backup without the spools does not restore queued messages.
- Moderation state. A list waiting for approval looks idle but is not broken. Give moderators an escalation path.
Sympa does not provide campaign scheduling, audience segmentation for marketing, or per-edition analytics. If you need those, keep Sympa for discussion and use a separate campaign application for editions.
Where MailKite fits
MailKite, which we build, is a hosted inbound-email and sending API. It can receive mail as a signed webhook and send replies, but it is not a mailing-list manager and does not provide Sympa’s subscription scenarios or archives. Its terms prohibit unsolicited bulk or commercial mail, sending without consent, and sending after opt-out.
A common split is Sympa for member-to-list redistribution and MailKite for application mail or reply handling. That is two systems with two identity models; do not assume a message accepted by one is suppressed in the other. See receive email with a webhook for the webhook path and MailKite receiving docs for the payload contract.
Next steps
- Read the bulk email guide for the application/transport split.
- Compare campaign tools in the open-source bulk email comparison.
- If you need a newsletter layer instead of a discussion list, start with programmatic newsletters.
Sources reviewed 2026-11-07: Sympa requirements, installation, initial configuration, starting the service, and the SOAP/HTTP API.