Hi,
My next challenge is to script the setup of a bunch of nonmembers who have a moderation action of accept (or maybe defer) whilst the list itself has a nonmember action of hold.
This is due to a relatively heavy use of nested lists, and have a fair number of people who might possibly send to all lists, and are important enough they wouldn't want to be manually allowed each time even if it only once.
When using the mailmanclient python bindings I have worked out I can add nonmembers with something like:
mailing_list.add_role('nonmember', 'nonmember@yourdomain.com', display_name='Non Member')
However I can't see anything in the mailmanclient docs which suggest it is possible to configure a member_moderation_action or moderation_action field for that member.
I assume I'll need to fall back to using the REST API directly, and most likely something along these lines:
1/ Obtain the member ID for an email address of someone who already been added as a nonmember.
2/ Patch an endpoint which looks something like: /members/{member_id}
I'm not able to use the mailman binary (e.g mailman shell) on the mailman-core host itself as I would like to query an existing database of people and reach out to a mailman endpoint from the database host rather than opening that host up to further network access.
I figured it might be a good stage in which to ask for a little help and pointers before I continue, perhaps there is something I have missed for a better way to approach this.
Thanks.
Regards, Perry