View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0020230 | phpList 3 application | Campaign Send Process | public | 09-07-20 17:59 | 14-12-20 12:22 |
| Reporter | duncanc | Assigned To | |||
| Priority | normal | Severity | minor | Reproducibility | have not tried |
| Status | resolved | Resolution | fixed | ||
| Product Version | 3.5.5-RC1 | ||||
| Target Version | 3.5.6 | ||||
| Summary | 0020230: Add Reply-To address to campaign emails | ||||
| Description | phplist already has code to store a "reply to" email address and add it to the outgoing campaign email. But the admin user interface doesn't provide a way to enter it. I have tried adding a "reply to" input field to the Compose tab and that seems to work correctly. A Reply-To header is included in the sent email. Looking at the git history, it has been like this since phplist started to use git. @michiel do you remember the background to this? Any reason why a reply to address shouldn't be used for campaign emails? | ||||
| Tags | No tags attached. | ||||
|
|
I don't remember exactly why I decided to drop it. I do remember I initially had it planned. The main issue for hosted is that we'd need to ensure that the Reply-To is a validated email address as well, otherwise you'd open up for abuse like "Reply-To: support@paypal.com" So, I think we can add it to the download version, without problems, but for the hosted version, I'd want some "list of approved addresses" management system or something. That is most likely the reason I dropped it, it seemed too convoluted to build all that. So, if this is added with a flag, it'll be fine, and we just disable that for Hosted for the time being. |
|
|
See https://github.com/phpList/phplist3/pull/690 |
|
|
This was resolved with https://github.com/phpList/phplist3/pull/690 |
