- Stephen J. Turnbull (turnbull.stephen.fw@u.tsukuba.ac.jp) [210530 09:19]:
Mark Sapiro writes:
On 5/29/21 7:31 PM, Stephen J. Turnbull wrote:
Membership adapter is a Mailman 2 feature that allowed use of an external membership database (such as a corporate LDAP system). I thought it was ported to Mailman 3 but maybe not.
Actually, it's not quite that simple. Mailman 2.1 defines a MemberAdaptor class, [...]. The Mailman 3 analog of this is the IMember interface defined in mailman/interfaces/member.py and implemented in mailman/model/member.py
OK, but for Andi it is "simple" in the sense that he doesn't have an existing MemberAdapter, so the plan is "Implement the IMember interface".
Not sure if this is the right approach, or if it wouldn't be more appropriate to "just" replace the dependency on allauth in postorius, and do all the magic in the frontend only (because that's where people actually subscribe). Whoever subscribes by mail needs some admin action, or some cron job, or is unsupported - for my case the main interface is the web interface, not the email commands.
That of course would imply that e.g. cleaning up mailing lists happens by a cron job with rest, but why not?
Andi