Hi Ben,
Ben Rudder wrote:
We are running a closed site for a trade union project, with multiple
groups and roles
We are on Plone 2.1 and our developers could find no product robust
enough to handle email lists from within Plone for each of the groups
and/or roles
At the moment, we have Mailman running on a separate server, with no
capability to authenticate mail list users against their Plone attributes
>
We can avoid some of the potential risks of getting
inappropriate/unauthorised users on each of the lists by placing links
to Mailman sign-up pages in locations in the Plone site requiring
appropriate permissions, and will be moderating both posts and
subscriptions.
But we would prefer that the list membership was able to automatically
cross-reference against Plone membership attributes to avoid too much
manual work for administrators if membership grows.
Our developers have suggested some days of research to establish
development costs, and then the development itself.
We have expressed an interest in finding a solution for the Plone
community, especially if there is enough interest to find a cosponsor.
A little off topic because we have no ressources to cosponser
integration. But we, a very small umemployed ngo, had the same problems
some time ago. I skimmed trough the sources of Mailman 2 and did some
research about approaches to extend Mailman 2. Hacking Mailman 2 is
undesireable and was out of question to us, so we opted for the manual
approach.
Our biggest win since then was migrating to Sympa.
(http://www.sympa.org). It's a mailinglist server written in Perl.
If you do some research you should consider migrating to and integrating
Sympa. And it would be a far more flexible solution for the community.
We chose it because
- it's mature and is constandly being developed
- has a serverwide userdb
- can authenticate against different sources (cas, shibboleth and ldap)
- has an advances permission and rule system (authentication scenarios)
- templates for different list types (List Families)
- true virtual hosts were you can use the same listname in different
hosts.
- a SOAP interface
- RSS-Feeds
- good documentation
cons for us where:
- setup and integration into postfix with virtual domains can be a
little tricker
- flexible bounce-management (and in general more options) that we had
to consider
- UI could be more intuitive
- perl
- less known and a smaller userbase
..carsten
_______________________________________________
NGO mailing list
[email protected]
http://lists.plone.org/mailman/listinfo/ngo
