Superdesk is an open-source, web-based, headless CMS for news organisations and publishers. It offers powerful workflow features for end-to-end news creation, production, curation and distribution. Our flagship news management system integrates easily with legacy systems as well as third-party applications.
Live Blog is open source live blogging software that allows you to cover live events and breaking news with a curated timeline including text, images, audio and video from your reporters and social media channels.
I can not yet judge whether it is suitable for my newsletter / mailing needs, but wanted to propagate it here, as it seems fascinating for our community.
I don’t know if it’s difficult to build a module from it and if someone would like to sacrifice time for it. Likewise, I probably can’t do it myself.
I have again browsed through the list of Nethserver modules.
Thereby, I came across Sympa. That’s why I will consider it for the time being.
A central question will be, how I can use in Doibarr managed member list of the association in Sympa. But that will be a separate question in a new thread.
Most likely I misinterpreted or did not understand the function of Sympa. Apparently, the platform is not intended for creating, managing and sending newsletters.
Rather, it seems to be a tool for exchanging information with subscribers by sending mails to a mailing list. I had already forgotten that I had used such a tool in the last century. But I had no correct association with the term mailing list anymore.
Furthermore, the documentation is so rudimentary or poorly structured and difficult to access that the research effort and subsequent administration effort is astronomical.
It seems like it needs a dedicated and specific application server due to the specific requirements stack. IF a module could be made, I guess the management and support of the whole stack is still a daily management task.
I share your concern about requirements, at least for “simply” managing mailing lists.
I can understand DBMS, python, MTAs, but I’m asking myself what are needeed for Tomcat andJDK (instead of a simpler JRE).
It could wel be that the main question is a mix of technical and operational desires.
My suggestion would be to talk to the business and see what expertise/skills is available to design a mailing flow (end to end) what processes and responders are involved and get a good idea what kid is walking into the candy store.
Only then scout for technical solutions that fit the bill and can support and maintain it in a sustainable way with available staff that will adhere to business objectives.
May I summarize?
With a lot of mailing list services available in internet, without the risk of make the mailserver be considered as spam source, a mailing list manager might not be value added option as in-house (or hosted) module.