Please support Mailman Groups module

Probably should say specifically what I need:

* A documented function I can call to subscribe/unsubscribe.
This is because we provide a Group-to-MalingList synchronisation concept - joining the group subscribes you to the list. Leaving the group should unsubscribe you. No code changes required (other than providing a wrapper function, maybe), more a matter of defining the interface.

* For User mailman register to call a function I provide to determine if the user should have access to the list. If not then don't display it as available to subscribe. This requires some code changes, not a lot.

I'd be happy to provide a patch for both of these, just want to know if in principle you'd be willing integrate and support them (I mean support in terms of long term compatibility, not answering support questions!)

Further info - this is from an email from me to the client who is sponsoring this development:

Right now, to gain access to a Group-related Mailing List, the user must be both a member of the Group AND assigned to a role which has access to that List (configured in the Access Control page). This is functional, but has two significant drawbacks:

* It's an administrative chore, because every time you create a new Mailing List you will need to give access to the relevant Role AND set the List-Group relationship.

* If you have 100 Mailing Lists then you will have a huge page for your Access Control page, since every single List appears there. Definitely not a fully-scaleable solution.

It seems to me that there should be an OR relationship - a user should be able to access a List if EITHER a member of the related Group OR given access via Access Control. Do you see what I mean, and do you agree? This would mean that in general, Group-related lists would not appear in the Access Control page.

I can't change the way it works right now, this is just for my discussion with the "User mailman register" developer - I'd need minor changes to that module in order to support the above functionality

Thanks for the reply. I'm about to go on holiday myself until September too so won't be doing anything more on this until then.

_user_mailman_register_subscribe should be sufficient

... after some time looking through your code I successfully used _user_mailman_register_subscribe_update function to subscribe (haven't got unsubscribe functionality implemented yet.) The _user_mailman_register seems to do some kind of re-sync of existing subscriptions, and among other things loads and parses all lists. I was concerned about unneccessary loading (with large numbers of lists.) I'm not clear as to why _user_mailman_register_subscribe does all that processing, and it didn't seem to be useful for a new subscription. Maybe I'm missing something - should I be _user_mailman_register_subscribe instead of the _update version?

Anyway, just wanted to get the ball rolling - I'll be back in touch in September - have a great holiday (as I aim to do!)

Just in case you've not spotted it: http://drupal.org/project/mailman_api