The mailing list for listmasters using Sympa

[Olivier Salaün - CRU <address@concealed>]

Hi Paul,

Paul Haldane wrote:

I've been looking at edit_list.conf as I needed to understand why different people saw different sets of list admin options.
I believe there are a couple of typos in the current CVS version of edit_list.conf ...

shared_doc.quota        owner.privileged_owner        read
web_archive.quota        owner.privileged_owner        read

The dot after "owner" should be a comma in both cases (we're very sensitive to this after staring at a scenario file that wasn't working because we'd done a similar thing).

You're right ; I've fixed this in our CVS tree.

Are there strong reasons for only allowing listmasters (as opposed to privileged_owners) the ability to access/change a list's data_source settings?  I can see that we're likely to have a requirement for some other groups in the University to be able to administer lists (including the ability to populate the lists from their databases) but we wouldn't want to make them listmasters for all of our lists.  Could we get round this by creating additional list robots, putting each group's lists on a separate robot and making them listmasters?

The default seems quite reasonable and I can't think of any listmaster who could afford to allow all list owners to import data from external databases.

As far as I understand your needs, you could define a list family (only available in sympa 5). The only limitation in the current version is that lists belonging to a family can only be instanciated on the command line. We wish to merge the family concept with the create list web feature ASAP.

Otherwise, you can define edit_list.conf files at each list level (only with Sympa 5.x).

-- 
Olivier Salaün
Comité Réseau des Universités
-------------------------------------------
Validation signature / Trusting  signature: --> http://igc.cru.fr/trust.html
------------------------------------------- 

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature