A release candidate for phpList 3.5.6 is now available for testing.
This release includes:
A Reply-To header to for your campaigns
This addition is controlled by a config setting and it is not enabled by default.
You can check more details on the pull request.
The same formatting rules as in the from address would apply and the help text has been updated to state that --see here.
Enhancements to campaign forwarding
When forwarding a campaign email the original from address with be used instead of the subscriber address to avoid delivery problems when using services that require the From address to be verified. Additionally, on the Forward form, the subscriber has to enter their name (mandatory form), which is used for the From and Reply-To addresses.
See details on the pull request.
Improvements on how the automatic updater handles plugins
This change makes sure that the default suite of plugins included in phpList will also be updated during the automatic update, instead of just being restored from the previous installation version. See details on the changes here.
Changed listing of campaigns in “Statistics Overview” page to use “Sent Date” as a criteria for
ordering – see the pull request.
All these changes were initiated and implemented by @duncanc, helping make phpList better one release at a time :).
A big THANK YOU on behalf of all phpList users!
If you have experienced issues with previous installations please install this update and see if those issues are resolved.
Download the Release Candidate here (see also ‘Upgrading’).
Upgrade from releases older than phpList 3.3.7-RC1 following the usual upgrade process
Use the Automatic Updater if you are running phpList 3.3.7 or later.
Use your phpList as normal, and report any new problems that you find.
Activating the REST API
If you haven’t checked the REST API yet, you can see the dedicated chapter in the manual to help you get started with it: API and Integrations
Report any issues you find with phpList3 to the phpList Bugtracker, selecting “3.5.6-RC1” as the Product Version.
Use the usual bug fixing process if you know how to fix it.
Please read the contribution guide on how to contribute and how to run the unit tests and style checks locally.