garloff / ucs2mailman3 Goto Github PK

I recently discovered that members of nested LDAP groups aren't synchronized to the corresponding mailing list.

How to reproduce:

1. Create LDAP group foo.
2. Add user alice to foo
3. Create LDAP group bar
4. Add user bob to bar
5. Add the group foo as member of bar.
6. Run ucs2mailman.py -d -n -a ADMIN@DOMAIN -t MLDOMAIN -u udm.users -g udm.groups

The mailing list corresponding to group bar will only consist of member bob.

Adding other mail addresses from members as non-members does not seem to allow them to post by default. Probably some extra setting is required. . .

The parameter '-R' specifies the recursion depth. Current default of 1 suggests that we include exactly one layer of nested groups. Reality is that at least one layer is included: As we just add members from nestedGroups to their ancestors, we may reference a group that already has been processed and thus end up including 2nd level as well.
This is somewhat unpredictable and thus not satisfactory.
Options:

• Default to a high recursion level, trying to always catch everyone referenced (unless you have crazily nested groups). The recursion limit becomes an implementation detail that makes the runtime bounded.
• Track nested members differently from direct members.