Sympa Configuration
Sympa is storing its parameters in a sort of "file database" of it's own in /var/blah/sympa/<listname>/config The data files look like flat text configuration files with a weird organization... json or yaml would be so much clear and easy to manage. When we use the Sympa administration UI it fully rewrites the file (one per list) completely, changing the order in a way it alone knows.
Puppet set up
Puppet has been set up (intelligent way to manage this but really unconventional use... I think Sympa's guys would be shocked) to control these data files as if they were human defined config files. So each configuration change made through admin interface is reverted in a matter of 30 minutes by puppet. Which explains the frustration of all those who tried to play with this admin interface in Sympa. The hard part is that the tiniest change modifies nearly all the file, so diff is useless here... i had to print the file before and after and use a pencil to cross the unmodified parts to spot what changes were important. At the moment i have no brilliant idea, no idea at all would be more accurate, about how to manage this better.
Configuration Notes
In the puppet "Sympa" module there is now a variable named "critical", false by default. If we set it to true the list archive and subscription get restricted. So we will be able to reuse this easily for other lists if the need appears later.
When sender_subscriber=true (a.k.a. allow_subscriber=true) then all subscribers to the list are allowed to send to the list as well. However, what isn't obvious is that anyone with a @mageia.org may also send to the list, whether subscribed or not.
If automated e-mails are expected to be sent to a group, make sure the From: address is included in sender_email. This isn't necessary if sender_subscriber=true and the mail comes from @mageia.org.
