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
sourced from
Grouper

Email list product

Architecture if Grouper
(LDAP, SQL, etc)

If grouper, do users
use the Grouper screens
to manage lists?  If not
how does it work?

If grouper, when you
migrated to Grouper,
any lessons learned?

Penn

None, hope to at some point.
We do have a daemon in dev that syncs
from Grouper to listserv via the email
interface to listserv, and XMPP from
Grouper, not sure if we will launch it.

Listserv




Duke

1%

Sympa

From LDAP

Custom UI which uses
Grouper WS


UChicago

Some

Sympa

From LDAP

Yes, Grouper's Lite UI


Bristol

None

Sympa

Could use a web service
that outputs email addresses
with one per line



LIGO

~10 currently, aiming for ~100

Sympa

LDAP provisioned by ldappc-ng

custom Javascript UIs that
drive Grouper REST ws

Need to have a clean interface
to allow users to manage multiple
acceptable "send from"
email addresses. We populate
mailAlternateAddress in LDAP and 
have Sympa check that.

MUSC

0%.  Currently working on a use case. 

Exchange

AD provisioned by ldappc-ng

grouperLoader for inclusion rule, then administer allow and deny 
We envison setting up a mailing list group type with the attributes needed to publish to AD.


Newcastle

~5, in discussions with mailing list administrator
to increase the amount of lists provisioned from
Grouper

Sympa

Currently export data from Grouper
to create a text file which we push
onto the sympa server using a data
integration tool (Talend). May look at
doing this via AD though.

The mailing lists we currently provision are based on pre-populated groups based on
HR/Student data so no end user interaction currently. In future, we would look to incorporate
the lite UI as part of the mailing list service.


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 MelonVery 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.