Developers of Sympa

[LALOT Dominique <address@concealed>]

At 11:59 01/10/01 +0200, vous avez écrit:

> Hello,
>
> First, I am happy you are pleased with the ldap version. I will try
> to
>  answer your questions:
>
> > >  1. Shall we still use an SQL database?.
>
>  Of course you must, actually the SQL database is required, indeed
> it
> contains the user's preferences and his subscriptions. The LDAP
> directory is only used for Authentication, it does not disturb the
> basic
> running of Sympa.
>
> > > 3. If some people want to join a list, do we need to put them
> in our ldap database
> > > with the right search filter corresponding to the list?.
> > > Or is there a mixed way combining ldap and sql?.
>  
>  As I said before the initial behavior of Sympa is still available.
> So,if
> someone wants to subscribe to a list he/she does not nessary belong the
> LDAP
> database.
> Let me describe you how the authentication runs :
>         you can
> authenticate yourself via an email, first Sympa will look for
> it in its SQL database, if you are not, Sympa looks for the user
> in the LDAP database.
>         if you are
> authenticated via an uid of course Sympa looks for in the
> LDAP database.
>
> So, if a new user wants to subscribe to a list, if he/she does not belong
> to
> the LDAP database, he/she will be recorded in User_table and will
> authenticate with his/her email and the password given by Sympa.
>
>  Keep in mid that you can mention in auth.conf many directories,
> that will
>  allows you to authenticate people belonging to different LDAP
>  directories.
>
> > > 2. How are the bounces handled?.
> >     no more?.
> > >   via an official OID we can add in our 
> schema?.
> > >    I immagine to put a ldap sympa user limited
> to write those OID.

OK.. Immagine that we have thousands of users in a ldap database, you
will add most of them, each time there will be an error in the
subscriber_table ?. With what, the email or the UID?.
 From my point of view, if you are managing entries from an ldap list,
you should store all the informations in the ldap tree. So when there is
a bounce, write that information in the entry.
Using that way, you can have an ldap only mailing list server. There is
little need ( and some difficulty to manage and install ) to have both
LDAP and a RDBM 

I think you should propose an LDAP only solution, where sympa has the
right to work on a proper branch and add his informations. There is just
a few writes and lot's of search/read and ldap is OK for that.

Just some ideas for developpement. 

Dominique

_______________________________________________________________________

Mr. Dominique Lalot                           (33) 04 42 91 34 24

Ingenieur Systemes et Reseaux                  Email: address@concealed

Faculte de Sciences Economiques                14 Av Jules Ferry

13621 Aix en Provence                          France

Correspondant Ciscam                http://ciscam.univ-aix.fr

_______________________________________________________________________