On Mon, Jul 8, 2019, at 3:12 PM, dancab@caltech.edu wrote:
I'm working on a container based Mailman3 solution for my university. We have a help desk tool which needs to access the API remotely for creating and deleting Mailman lists. The API will be restricted to a private network, behind a firewall, etc.
What is the simplest way to expose the API to an external host?
I do want to stress the fact that we wouldn't advise exposing the API to internet since there is a very basic authentication in the API an the API is an administrative API.
At the moment, I seem to have this partially working via an Apache virtual host configuration which simply proxies via
api.example.edu:80 to localhost:8001 on the container.I'm able to remotely use the mailmanclient module for the client.lists, client.system and client.members commands. However running client.domains generates an API connection error. So it seems unstable.
Does it *always* happen when you run client.domains? Did you get
an error traceback?
Any thoughts or suggestions?
Thanks.
Dan Caballero Systems Administrator Academic Computing Solutions IMSS - Caltech https://imss.caltech.edu
Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
-- thanks, Abhilash Raj (maxking)