Help with Configuring Mailman3 for Multiple Mailing Lists on a Single Server
Hello Everyone,
I’m currently working on setting up Mailman3 on a server to manage several different mailing lists for a project. I’ve successfully installed Mailman3 and Postorius, and I can create and manage individual mailing lists through the Postorius web interface. However, I’ve encountered a couple of challenges that I need assistance with:
Multiple List Management: I’m trying to configure Mailman3 to handle multiple lists for different projects. While individual lists seem to work fine, I’m unsure about best practices for managing multiple lists on a single server. Specifically, how can I ensure each list has its own distinct set of configurations (e.g., moderation settings, privacy settings, and membership options), but still manage them efficiently from the same instance of Postorius?
Integrating with External Services: We plan on integrating Mailman with a few external services for better automation, including a CRM system and a custom registration platform. Does Mailman3 provide APIs or any documentation that can help with integrating mailing list functionality into other applications? If anyone has experience with these types of integrations, any advice or resources would be greatly appreciated.
I checked this: https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ https://www.igmguru.com/machine-learning-ai/generative-ai-training https://lists.mailman3.org/mailman3/lists/test2.mailman3.org/
Security and User Privacy: Since we’ll be dealing with sensitive data from subscribers, what security measures should we consider to ensure the privacy and safety of the mailing list subscribers? Any suggestions regarding encryption, access control, or secure email practices within the Mailman ecosystem would be helpful.
I’d greatly appreciate any insights or advice the community can offer. Thanks in advance for your time!
On 11/28/24 12:01 AM, peterrflores@hotmail.com wrote:
Multiple List Management: I’m trying to configure Mailman3 to handle multiple lists for different projects. While individual lists seem to work fine, I’m unsure about best practices for managing multiple lists on a single server. Specifically, how can I ensure each list has its own distinct set of configurations (e.g., moderation settings, privacy settings, and membership options), but still manage them efficiently from the same instance of Postorius?
This is how things work. See for example
https://mail.python.org/mailman3/?all-lists - each of those lists has
its own settings. There are also unadvertised lists on that server,
e.g. https://mail.python.org/mailman3/lists/capi-sig.python.org/
Integrating with External Services: We plan on integrating Mailman with a few external services for better automation, including a CRM system and a custom registration platform. Does Mailman3 provide APIs or any documentation that can help with integrating mailing list functionality into other applications? If anyone has experience with these types of integrations, any advice or resources would be greatly appreciated.
Mailman core provides a REST API for list management. See https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/r...
- this interface is only protected by a user name and password, so it is
normally only available via
localhostas wider access is not very secure.
Postorius uses this API via the python bindings described at https://docs.mailman3.org/projects/mailmanclient/en/latest/
Security and User Privacy: Since we’ll be dealing with sensitive data from subscribers, what security measures should we consider to ensure the privacy and safety of the mailing list subscribers? Any suggestions regarding encryption, access control, or secure email practices within the Mailman ecosystem would be helpful.
A list can be anonymous id desired which means the sender of a post is not identified in any headers of the distributed email.
HyperKitty archives can be private, i.e. accessible only to list members. The membership list can be restricted to only list owners/moderators or available to list members as well via list settings.
There is currently no support for encrypted email.
Full access to a list's settings and other info via Postorius is limited
to logged in users who are either a superuser or an owner of the list.
moderators have more limited access, list members may be allowed to see
the membership.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
参加者 (2)
-
Mark Sapiro -
peterrflores＠hotmail.com