phpList 3 is a fully functional open source email marketing manager, written in PHP and released under the AGPL-3.0 licence, for creating, sending, integrating and analysing email campaigns and newsletters, aimed at organisations that want to run campaign infrastructure on their own server rather than hand it to a third party.

What it is

phpList 3 is a self-hosted email campaign and newsletter manager. It provides a responsive web-based administration interface alongside a command-line interface, and it covers the full campaign lifecycle: building lists, composing messages, scheduling and dispatching sends, processing bounces, and reporting on responses. It is built as a plugin-based architecture with multiple APIs, and it carries a marketing API surface that lets other systems integrate with the list and campaign data. Content personalisation customises every message to individual subscriber attributes and preferences, and segmentation supports targeting subsets of a list.

The concrete problem it solves is the operational load of large-scale email delivery. Message-queue management load-balances and throttles multiple sending accounts and campaigns, and tracks every delivery outcome, so a send of any size can be paced against host-imposed limits instead of being fired off in one burst. Domain-based throttling enforces host-specific policies through custom rules, and bounce handling applies policy and regex-based processing while archiving every bounce so it stays auditable. For teams that would otherwise run a hosted mailing provider, deploying phpList on their own server replaces that dependency while keeping the same campaign, list and analytics functions.

Key capabilities

• Responsive web-based and command-line interfaces for administration and sending.
• Message-queue management that load-balances and throttles multiple accounts and campaigns and records every delivery outcome.
• Real-time analytics on message responses and subscriber behaviour, plus marketing statistics reporting.
• Automated bounce management with policy and regex-based handling, with every bounce archived.
• Content personalisation and segmentation driven by subscriber attributes and preferences.
• Amazon SES support built in and optimised, alongside domain-based throttling rules.
• CSV and Excel subscriber import and export including attributes and preferences, email attachments, RSS feed reading on a per-user schedule, and "Send a Webpage" remote HTML polling, conversion and dispatch.

Who uses it and how

• Large senders running high-volume campaigns on their own infrastructure. phpList was used to send more than 25 billion campaign messages in 2018.
• International teams. The project reports use in 95 countries and availability in 20 languages.
• Teams that want managed hosting. phpList Hosted offers a free account, and data can be migrated between a self-hosted installation and the hosted service in either direction.
• Evaluators and developers. A demo installation is available and is wiped and refreshed every hour.
• Administrators who need campaign control. Campaigns can be scheduled, paused, resumed, repeated and requeued.

Getting started

Deploy it on your own server by copying the lists directory from the tar file into your webroot and opening http://yourdomain/lists/admin/, or sign up for a free hosted account at https://phplist.com. A demo is available at https://demo.phplist.org.

How it compares

No comparable tools or paid products are named in the facts provided for this entry, so phpList 3 stands alone in this registry rather than being placed against a set of alternatives. Its distinguishing points are the AGPL-3.0 licence and the choice between self-hosting and a hosted account from the same project, with data migration supported between the two.

When to use it — and when not to

A self-hoster must operate the MySQL database the upgrade instructions back up with mysqldump, keep lists/config/config.php and any edited lists/texts/english.inc or other language files across upgrades, configure the web server, and deny web access to the config directory, for which an example .htaccess for Apache is provided. Anyone unwilling to own that stack, or who needs a fully managed service out of the box, should not self-host. The trade-offs are real: large database upgrades can take a long time and must not be interrupted, the README's Requirements and Development Installation sections are empty placeholders, and 92 issues remain open.