Developers of Sympa

[Mark K <address@concealed>]

On Wed, 16 Jan 2008 16:32:30 -0500
Joe Vieira <address@concealed> wrote:

> 
> 
> >That's interesting since I would think it more common to do the
> >opposite (feed sympa from LDAP).  Not to pry, but why do you want
> >sympa driving LDAP?  What else will you use those LDAP groups for?
> 
> I actually want both,
> so if we write directly to ldap, i would like sympa to use that and
> then if we make a change using the sympa interface, i would like that
> to be reflected in ldap.  i.e if we add a user to a mailing list, i
> want that pushed back into ldap.
> 
> it's all about keeping everything in sync from all directions, does
> that make sense?
> 
> Joe
> 
It does make sense.  You can easily do ldap->sympa using include2.  You
could write something new to sync things sympa->ldap but both ways
would be something again entirely.

Basically, you want it to act as include2 does now, but to allow
mods that are sent back to LDAP.  The modify method from Net::LDAP
ought to do the trick. The list config would need a dn with write
access.

Aside from some extra config info, just copy how include2 works but
add the ability to modify the contents of the include with a direct
call to LDAP (or any other db type of thing).


Maybe our European brethren will have some more concrete info when they
wake up tomorrow :)

-- 
Mark K