The mailing list for listmasters using Sympa

[Paul Haldane <address@concealed>]

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).

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?

Paul

--
Paul Haldane
Unix Systems Team,
Information Systems and Services, University of Newcastle upon Tyne