Developers of Sympa

[Joe Vieira <address@concealed>]

> If LDAP feeds mailing lists via include2 then that's how you know all
> the subscribers.  It's always the same as the LDAP group.  You don't
> need the mailing list to feed LDAP for that to happen.
>
>   
> In a case like that you would not allow subscription (subscribe.closed
> scenario) since all members would be included from LDAP.
>
>
>   
but in both of these scenarios you've assumed that the goal is not for 
users to be able to add themselves to that group...
example:
a.)student is auditing a class, or is just sitting in unofficially, or 
is perhaps a TA, and the professor wants them to get class mailings. 
that student would not have been added by our automated processes, but 
that does not mean they shouldn't get the mail. So the professor or 
someone with the ability to add them does so, i assume that would go in 
the local sympa database.
b.) then perhaps that student OFFICALLY registers in the course, they 
then get added to the ldap group, now they are added locally via sympa's 
database AND in LDAP, so they get two emails for every one that is sent? 
problem.

that's why keeping the information in sync is important in some cases. 
yes in SOME CASES adding someone to a group could be very bad, because 
it has other consequences, but not in ALL cases. thats why design is 
important.

yes sympa is not a database management tool, but that does not mean it 
is ONLY a data consumer, it can and does produce data, so it should keep 
that in sync...i mean it writes to it's own database. you don't have to 
add people to mailing lists using command line mysql ;-)

enough ranting tho... i was just curious if the dev doc thread i saw in 
the dev section of the website was active...and if people were actually 
working on it currently.... 
http://www.sympa.org/dev/exporting_groups_in_ldap?s=exporting%20ldap

Joe