View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 5955 | Composr | core | public | 2024-09-19 20:55 | 2024-09-19 23:48 |
| Reporter | PDStig | Assigned To | PDStig | ||
| Priority | high | Severity | minor | ||
| Status | resolved | Resolution | fixed | ||
| Product Version | 11.beta2 | ||||
| Summary | 5955: Many fixes and improvements to List-Unsubscribe | ||||
| Description | There were many glaring issues with List-Unsubscribe. This hotfix fixes / changes the following: 1) List-Unsubscribe target config should have been a line, not a tick. 2) Added '1' as an option to List-Unsubscribe target (which is the new default); if set to '1', the target will be the new data/unsubscribe.php endpoint. 3) Added data/unsubscribe.php; mail clients are starting to require use of the http/https POST method of List-Unsubscribe and rejecting mailto. This endpoint (with the provided correct nonce and checksum) will add an e-mail address to the new unsubscribed_emails table. The mail dispatch will filter out e-mails that exist in this table regardless of priority. 4) Mail dispatch was not properly adding the List-Unsubscribe headers. This is fixed (but not fully tested yet; see notes as I will post when they have been fully tested). Swift Mailer was also not setting them at all. 5) Added List-Unsubscribe post config option (also a line). If the target is a URL, this can be POST data to send to the URL. email_address is always passed automatically by the software. 6) Added can_email_address function for checking if we can e-mail a specific address. This will also now check unsubscribed_emails in addition to mail bounces. 7) can_email_member is now a wrapper for can_email_address. 8) Added a warning on a member profile's edit settings screen if can_email_member returns false. It instructs the member that they are not receiving e-mails from the site and possible reasons why (no e-mail set, unsubscribed through their mail client, or received a bounce-back in the last 8 weeks) along with what to do. Reminder this is not fully tested yet. It will undergo testing for v11 beta3. | ||||
| Tags | Roadmap: v11, Type: Legal compliance / Privacy | ||||
| Attach Tags | |||||
| Attached Files | |||||
| Time estimation (hours) | |||||
| Sponsorship open | |||||
|
|
Fixed in Git commit 1cc5657240 (https://gitlab.com/composr-foundation/composr/commit/1cc5657240 - link will become active once code pushed to GitLab) |
|
|
A hotfix (a TAR of files to upload) has been uploaded to this issue. Only apply this hotfix if you absolutely need it and cannot wait until the next release of Composr (releases are more reliable and strictly tested). As of Composr version 11, the recommended way to apply a hotfix is by following the same steps as an upgrade (https://baseurl/upgrader.php, use the hotfix on the step “Transfer across new/updated files”). The upgrader will automatically skip files belonging to addons you do not have installed or that are newer on disk than in the hotfix. Otherwise, you can manually extract and replace these files (do not replace if your on-disk file is newer than the one in the hotfix). Always take backups of your site or at least files you are replacing before applying a hotfix. Not sure how to extract TAR files to your Windows computer? Try 7-zip (http://www.7-zip.org/). |
|
|
I had to modify data/unsubscribe.php to show a form if accessed directly without POST data: https://gitlab.com/composr-foundation/composr/-/commit/4d45e83997f860061e5b58a048d5dee682729b6e |
