The Mailman Provisioning Plugin manages Mailman3 mailing lists using Registry data. (experimental) |
This Plugin currently requires specific patches against the Mailman3 codebase in order to function correctly. As such, it is considered Experimental. |
Registry CO Person Transaction | Mailman Action |
---|---|
Add | Synchronize the CO Person and their Mailman list subscriptions |
Edit | Synchronize the CO Person and their Mailman list subscriptions (this includes CO Group Membership changes) |
Enter Grace Period | No changes (unless attributes change as part of grace period) |
Expiration / Becomes Inactive | Unsubscribe the CO Person from Mailman lists |
Unexpire / Becomes Active | Synchronize the CO Person and their Mailman list subscriptions |
Delete | No changes (subscriptions will be removed due to loss of CO Group Memberships) |
Manual Provision | Synchronize the CO Person and their Mailman list subscriptions |
Registry CO Group Transaction | Mailman Action |
---|---|
Add | No changes |
Edit | No changes If a CO Group is suspended, all of the associated CO Group Members are effectively removed for purposes of subscription synchronization |
Delete | No changes |
Manual Provision | No changes |
Registry CO Email List Transaction | Mailman Action |
---|---|
Add | Create a corresponding Mailman list, and synchronize subscriptions |
Edit | Synchronize the corresponding Mailman list, including subscriptions If the status of the list is Suspended, the list will remain in place but all subscriptions will be removed Renaming a list is not supported |
Delete | Removes the corresponding Mailman list |
Manual Provision | Synchronize the corresponding Mailman list, including subscriptions |
localhost:8001
, so you will probably need to make some changes so that your Registry server can speak to it. (If you don't, you may need to specify 127.0.0.1 rather than localhost.) Possible approaches include reconfiguring the mailman REST web server to allow connections from your private network, or setting up a secure tunnel of some form. Be sure not to allow world access to the API.COmanage create a Mailman user for each provisioned CO Person, and then subscribes that user to the relevant Mailman lists. In order for this to work, the Plugin must determine a preferred address for each CO Person. The preferred address is determined by:
Verified status is currently ignored when selecting the preferred address.
Email addresses may be subscribed to a mailing list outside the control of COmanage Registry, for example by a Mailman administrator using the native Mailman web administration tool Postorius. When Unmanaged Email Mode is set to Remove (the default), the provisioner will remove any such unmanaged email addresses from the mailing list when the list is synchronized. Set Unmanaged Email Mode to Ignore to have the provisioner ignore unmanaged email addresses for a list when synchronizing the memberships.
|