New set of features based on LDAP.
|
sympa-3.3a-ldap.4 Download
- Ldap authentication via uid and emails stored in LDAP Directories.
- Named Filters : in the list's configuration you can grant privileges
to people stored in an LDAP Directory thanks to scenario.
- Multiple login for users with multiple emails is possible starting
from
pref or which pages. Those addresses are used as alternative
emails. Alternative addresses can also be extracted from the
initial LDAP user authentication.
- Unified subscriptions : using a unique email address
Changes :
- New conf file :
~sympa/etc/auth.conf (cf sample dir)
- Templates
-
help.tpl : the information concerning the change of password
does not appear in the case of LDAP authentication
lists.tpl : subscriptions corresponding to all your email
address in Sympa
pref.tpl : to add new alternative_email
- new directory :
~sympa/etc/search_filters
- new conf file : *.ldap
- Samples :
auth.conf,
sample.ldap,
sample.visibility,
sample.send
- One more cookie :
sympa_alt_email which is persistant
|
Sympa at last implement virtual robot !
|
sympa-3.3a-vhost.10 Download
Sympa virtual robots are like Apache virtual hosting : a single
daemon sympa.pl and a single cgi server wwsympa.fcgi now
can serve multiple domains with their own set of list, templates
and scenarii.
All configuration parameters can be define for each robot except
Sympa installation parameters such as binary and spool location,
SMTP engine, antivirus plugging etc.
A robot is named by its domain, and has its own setup directory
~sympa/etc/somedomain.org . This directory contains
a robot.conf file that defines the virtual robot parameters :
http_host title default_home lang listmaster max_size and colors.
~sympa/etc/dom.org/ contains lists of dom.org robot
Templates and scenarii will first be searched in
~sympa/etc/dom.org/wws_templates/, ~sympa/etc/dom.org/templates/,
~sympa/etc/dom.org/scenari/ directories before searching into
~sympa/etc .
Check sample dir.
[Florent Guilleux] Task manager:
Various task automatic processing. List master may use predefined
task models to automate recurrent processings such as regurlaly
reminding subscribers their belonging to a list or updating
certificate revocation lists. It is also possible to write one's
own task models to meet particular needs. Unique actions may also
be scheduled by this way.
Bookmarks management in the document repository (shared)
|