This page is intended to capture experiences users have with using Grouper and email lists. Feel free to add questions, rows, etc. All columns are optional.
Institution | % of email lists | Email list product | Architecture if Grouper | If grouper, do users | If grouper, when you |
---|---|---|---|---|---|
Penn | None, hope to at some point. | Listserv | |||
Duke | 1% | Sympa | From LDAP | Custom UI which uses | |
UChicago | Some | Sympa | From LDAP | Yes, Grouper's Lite UI | |
Bristol | None | Sympa | Could use a web service | ||
LIGO | ~10 currently, aiming for ~100 | Sympa | LDAP provisioned by ldappc-ng | custom Javascript UIs that | Need to have a clean interface |
MUSC | 0%. Currently working on a use case. | Exchange | AD provisioned by ldappc-ng | grouperLoader for inclusion rule, then administer allow and deny | |
Newcastle | ~5, in discussions with mailing list administrator | Sympa | Currently export data from Grouper | The mailing lists we currently provision are based on pre-populated groups based on | |
Memphis | Just about all. | Exchange | LDAP: AD and RedHat DS | We have a custom lite UI for human-managed groups. Course groups and organizational groups are processed by quartz jobs. | |
Carnegie Melon | Very few so far | Exchange (prod) Mailman (in dev) | AD provisioned via custom provisioner. LDAP provisioned via custom provisioner | Using custom (perl) loader that generates SQL tabled consumed by Grouper SQL loader to generate base lists from SoR data. Includes and Excludes managed via Grouper UI. Use cases currently limited to internal lists managed by technical teams. Exchange and Mailman are targeting two different use cases currently, mail team is continuing to evaluate options to determine best fit. |