Welcome to listmonk Discussions!

[knadh]

👋 Welcome!

We’re using Discussions as a place to connect with other members of our community. We hope that you:

• Ask questions you’re wondering about.
• Share ideas.
• Engage with other community members.
• Welcome others and are open-minded. Remember that this is a community we
  build together 💪.

To get started, comment below with an introduction of yourself and tell us about what you do with this community.

[FuncGuy]

Hi All, This is Tirumalesh here I have been working for the past 9 years and I have been looking forward to participating in the foss hackathon I am from a java background and also interested in contributing to golang projects that's why I am here.. Please guide me for getting started with contributions..Thanks

[rohansh-tty]

Hi, I am Rohan. I fiddle with Python, Go, and Typescript at work. I want to contribute to Listmonk as a part of the FOSS Hack. For starters, I can start working on API docs(which are mentioned as Work in Progress).
Thanks

[FuncGuy]

@knadh can you please guide which issues I can contribute so that I can get started

[knadh]

You can browse the open issues here: https://github.com/knadh/listmonk/issues/

Please take a look at the contribution guidelines here also: https://github.com/knadh/listmonk/blob/master/CONTRIBUTING.md

[bomhard]

Hi, this is Nikolaus. I am IT lead at IBE, an institute at Munich University. Our IT infrastructure is mostly foss, Debian Linux and completely self hosted. I'd like to offer a mailing list service both for internal use and possibly later for public usage as well. I found listmonk very nice, straigtforward and clear. However as far as I understand only administrators can create and send campaigns from the web interface. This is fairly limiting.

What I would need and didn't find any hint to is an option for a simple and access limited Interface to existing lists. This either could be an email account like [email protected] or preferably a web interface that permits just to select a campaign and send a new message to that - ideally integrated into Nextcloud.

Any hints where to start from?

Thanks and best
Nikolaus

--
Nikolaus von Bomhard
Computing Officer IBE
Data Protection Contact Person

The Institute for Medical Information Processing,
Biometry, and Epidemiology (IBE)
Ludwig-Maximilians-University Munich

Marchioninistrasse 15
5K U1 Raum 844
81377 Munich
+49 89 4400 74484

Data Protection Declaration:
https://bignode.ibe.med.uni-muenchen.de/dse/en.html
https://bignode.ibe.med.uni-muenchen.de/dse/ibe-dse-en.pdf

[knadh]

Hi @bomhard. listmonk is a one-way mailinglist/newsletter system. You should look at something like Mailman that allows many-to-many e-mail communication.

[bomhard]

Sad to hear that as it could probably fairly easy be a simplified multiuser system. Mailman is really huge and not allways first choice. In fact if there only was a second unprotected version of the dashboard with access only to existing campaigns, cloning and editing that would work. User authentication could be done with LDAP and Apache2 reverse proxy. If you think this is possible and maybe can give some initial hints then our staff could add that option.

[knadh]

Hi @bomhard. Multi-user auth has been long on the to-do. However, a multi-user mailing list is more complex than just having support for multi-user auth. Mailbox parsing, thread parsing, thread storage, broadcast, archival, groups etc. are where the complexities lie. Currently, there are no plans for this.

[bomhard]

Hi, you are right and I am aware of that. There is a huge difference between real maillist software like mailman and unidirectional newsletter software like yours. But this is not what I am looking for and probably many users do. As I wrote 'simplified multiuser system with unidirectional mode only:

Permitted users (controlled by the webserver, e.g. LDAP preauth) can access a simplified interface where they can clone and edit existing campaigns and send them to existing users. However using the simplified interface they cannot create or delete users, new campaigns or templates.

The admin can, using the existing password protected interface, do all the other tasks.

All needed to implement this would be a second limited interface running at e.g. 127.0.0.1:9000/users or alternatively a link on the admin login page to the open user page. Then it depends on the serveradmin if and how access to the user interface is limited. This doesn't need any of the features you mention but would be very interesting for intranet or semi-closed use. Think of some sports club. There could be one or two admins who have full permissions, and maybe 20 users with publishing permission controlled by htpasswd but hundreds who can subscribe. Kind of some to all newsletter.

[spammenotinoz]

Really just a thanks, this is an excellent project that I will only use 1/10th of the features.
Installed and up and running within minutes.