* On 6/6/25 15:00, Christian Schneider wrote:
So I read about the rest api of mailman3 and thought, I might give it a go... On the other hand the rest api should not be exposed externally (localhost-only) as said here: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/ADUT5TX6ESU5463XLMBPP527VOULAIZF/#ADUT5TX6ESU5463XLMBPP527VOULAIZF Running an nginx reverse proxy (and a firewall for the complete subnet) I am able to give dedicated access to the api but nevertheless I have no good feeling going this way...So my question is: What would be the best way to trigger creation of lists using a second system?
Keep the service running on localhost only and use (local) port forwarding via SSH from a trusted machine to access it, I'd wager. You can use a special user that is not allowed to spawn a full shell or execute commands for this.
Mihai
OpenPGP_signature.asc
Description: OpenPGP digital signature
_______________________________________________ Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-le...@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/UAO3BIFYCZRGQIRHCJO6EXRRWUHPYBVD/ This message sent to arch...@mail-archive.com
