Using SparkPost with PHPList
- Add a Sending Domain to SparkPost
- Create an API Key with “Send via SMTP” permission
- In your PHPList installation, open config/config.php
- Add the following configuration
$phpmailer_smtpuser = 'SMTP_Injection';
$phpmailer_smtppassword = '<API_KEY>';
- In your PHPList Campaign, use correct From Line. For example, if your Sending Domain is xyz.com, you can set From Line to @xyz.com.
- Send a test email to confirm the configuration is correct.
- SparkPost will decline emails if the domain name in the From Line does not match one of your verified sending domains.
<API_KEY>with the actual API Key that you’ve created in earlier step. It must have the ‘Send via SMTP’ permission.
- In case outbound traffic is not allowed through port 587 from your server (blocked by firewall), you can use the alternate port 2525 if that is open.
SparkPost does not send bounce report for emails it failed to send. So PHPList’s bounce processing is not applicable to SparkPost.
However, “hard bounce” recipients or people who complain about your mail will be automatically added to your account’s suppression list and SparkPost will suppress any attempt to deliver to them in the future. Suppression will be added for the same type of emails. For example, a transactional email received “hard bounce” will only be suppressed for transactional emails only. Non-transactional emails will still go through unless they are suppressed separately.
You can track bounces, complaints and other types of non-delivery from your SparkPost Account and through its webhooks and message events APIs. If you’d like to update your PHPList database directly using bounces and complaints from SparkPost, a 3rd party webhook endpoint has been published which enables handling webhook events.
This tutorial is prepared and tested against PHPList v3.3.1