I suggest a switch to use simplenews instead of the broadcast feature.
- archive of sent mailings as nodes
- node formatting, cck fields, templating etc on mailings.
- newsletters can also be sent to non-signed up users as promotions.
- simplenews allows us to automatically sign up participants (see simplenews roles module), but still allow them to opt out (with the newer code in HEAD)
- reuse of existing modules is more robust
- we benefit from subsequent features added to simplenews and modules in that larger ecosystem. eg, regular newsletters, scheduled newsletters, etc.
Comments
Comment #1
dwwFeel free to install simplenews on your site, but I don't want to add a dependency on simplenews just to be able to send broadcast messages to everyone who signed up for a node.
If there was something required to *allow* sites to *optionally* use simplenews for this, I'd be willing to look at a patch, but I'm definitely not going to make it a requirement for this functionality.
Comment #2
joachim commentedWhat I'm suggesting would be to remove the tight binding between signup and the broadcast system.
Instead, broadcast could live as a separate module in the signup package, and we could also provide a module that connects to simplenews (either in the same package or another contrib package).
Comment #3
dwwOkay, sure. Then what you want is blocked on #290305: Split out email functionality into separate submodule(s).