Send bulk email with phpList
Install phpList on PHP and MySQL, disable test mode, configure SMTP, and process the campaign queue from cron instead of an open browser tab.
Reviewed
phpList is a long-running self-hosted campaign manager for PHP and MySQL. Choose it when you already operate that stack and want lists, personalization, scheduling, domain-based throttling, and bounce handling in one application. It is a campaign layer, not a delivery platform: the transport is SMTP or PHP’s local mail() function, and you still own reputation and feedback.
This guide follows the documented manual installation, fixes the two settings that most often produce a silent non-sending install, and moves queue processing to cron. The phpList manual is authoritative for the current 3.x release.
Prerequisites
- PHP and MySQL with a web server, or the project’s Docker image.
- Write access to the
listsdirectory and itsconfigsubdirectory. - SMTP credentials from a provider that permits your sending volume. Confirm the provider’s bulk-mail policy before importing a list.
- A sending domain with SPF, DKIM, and DMARC, and a test mailbox you control.
- Shell access for queue processing. Browser-only sending exists, but it is not a production queue.
Install and initialize the application
Download the release and upload the lists directory into your web root. Create a database and a database user, then edit lists/config/config.php with the four connection values:
$database_host = "127.0.0.1";
$database_name = "phplist";
$database_user = "phplist";
$database_password = "replace-me";
Only config.php is read at runtime. config_extended.php is a reference file; copy the settings you need into config.php rather than editing the extended file in place. Open https://your-domain.example/lists/admin/ and choose Initialize database. The installer creates the schema and the first administrator.
The manual installation guide describes the web path in detail. Use the current release from the project’s download page, not a command from an old tutorial.
Turn off test mode before expecting a send
The shipped configuration enables TEST, which displays intended sends without actually sending:
define("TEST", 1);
Change it to 0 when you are ready to send:
define("TEST", 0);
While test mode is on, subscribers cannot confirm themselves, because confirmation mail is suppressed. A list that appears to accept signups but never receives confirmation is often this setting, not a transport failure.
Configure SMTP deliberately
Without an SMTP host, phpList falls back to PHP’s mail() function. That path depends on the host’s local mail configuration and is a poor default for bulk sending. Configure an authenticated SMTP transport and a verified From address:
define('PHPMAILERHOST', 'smtp.your-provider.example');
$phpmailer_smtpuser = 'replace-me';
$phpmailer_smtppassword = 'replace-me';
define("PHPMAILERPORT", '587');
define("PHPMAILER_SECURE", 'tls');
Send a single campaign to your controlled mailbox and inspect the headers before importing an audience. A successful queue process is not the same as a delivered message.
Process the queue from cron
Pressing Start campaign submits the message to the queue. It does not complete delivery. Processing the queue in a browser stops when the tab closes or the computer sleeps, so use the command-line form for anything that matters:
/usr/bin/php /path/to/lists/admin/index.php \
-pprocessqueue \
-c/path/to/lists/config/config.php
Run that command from cron at the interval your provider allows. The manual recommends talking to your hosting provider about send rates and caps; phpList’s own send-speed setting does not override the provider’s limit. If the command path is wrong, the job can fail silently, so log its output and check the modification time of the log.
Operate lists, bounces, and upgrades
Configure bounce collection through POP or an mbox mailbox and process it regularly. Suppress hard bounces and complaints, and keep the unsubscribe workflow working through the hosted provider as well as phpList. Test the unsubscribe link from a real campaign, not a preview.
Back up the database and config.php together. Rehearse an upgrade on a restored copy. The plugin architecture is useful for extensions, but it is also a compatibility boundary: the official REST API plugin targets phpList 3, so check the plugin release against the phpList version you run before building an integration.
Where MailKite fits
MailKite, which we build, is a hosted sending and receiving API. It does not provide phpList’s list management or campaign editor. It supports broadcasts and personalized batches but prohibits unsolicited bulk or commercial mail, sending without consent, and sending after opt-out.
If you already have a PHP application and only need transport, the PHP bulk email guide shows a MailKite SDK path. Moving from phpList means exporting subscribers with their consent evidence, rechecking suppressions, and recreating templates; the queue state does not transfer.
Next steps
- Review the overall pipeline in the bulk email guide.
- Compare self-hosted campaign tools in the listmonk vs Keila guide.
- See the full list in the open-source bulk email comparison.
Sources reviewed 2026-11-07: phpList manual installation, sending methods, bounce management, and the phpList license.