Dependency Graph
related to 
child of 
duplicate of View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0019845 | phpList 3 application | Software Releases | public | 25-03-19 11:04 | 05-11-19 11:29 |
| Reporter | suela | Assigned To | |||
| Priority | normal | Severity | minor | Reproducibility | have not tried |
| Status | resolved | Resolution | open | ||
| Product Version | 3.4.0 | ||||
| Target Version | 3.4.8 | Fixed in Version | 3.4.8 | ||
| Summary | 0019845: php mailer upgrade research | ||||
| Description | Check what issues may arise from the upgrade. Major changes and the ones most likely to affect us. | ||||
| Tags | No tags attached. | ||||
| related to | 0019295 | resolved | Upgrade PHP Mailer to 6.0.5 |
|
|
Regarding the version that it's being used now, it is no longer being supported for feature updates, but at least it receives security updates in this branch: https://github.com/PHPMailer/PHPMailer/tree/5.2-stable . |
|
|
I have been looking at using phpmailer 6 and there are fewer code changes than I expected. But using phpmailer 6 will have a few important restrictions phpmailer now requires php 5.5+ phpmailer and the phplist code changes are not backward-compatible with phpmailer 5 If phpmailer 6 is included in phplist then the first would require clear communication about the upgrade. The second point is relevant because currently people can use a version of phpmailer different to that included in phplist by specifying it with the PHPMAILER_PATH constant. I will push my changes then make a pull request for discussion. |
|
|
That's brilliant, thanks. We can run some tests and then move forward. |
|
|
See https://github.com/phpList/phplist3/pull/608 |
