Sorry, but that work-around doesn't work :) While you can indeed set any random address as Configuration-Owner, for it to actually work, the address has to be a listed owner of the list in question. As documented: "Please note carefully that any addresses specified in Configuration-Owner= must also be specified (either explicitly or as part of an access-level definition) in the Owner= setting for the list." Nathan At 10:35 AM 1/20/2010 -0500, you wrote: >I wonder if the "Configuration-Owner" keyword would work here as a kludge. It's supposed to allow you to define which of your Owners can make list header changes, but if "Configuration-Owner" doesn't need to be a subset of those defined in "Owner" and can be exclusive, then you might get your desired result listing them as "Configuration-Owner" but not as "Owner". > >Again not sure if it works like that because it's not quite the intent and I've never tested it, but I thought it would be worth mentioning in case it helps. > > http://www.lsoft.com/manuals/15.5/listkeyw.html#kConfigurationOwner > >-Jim > >-- >Jim Serwinowski [log in to unmask] >UB Listserv Administrator http://listserv.buffalo.edu > > >On Wed, 20 Jan 2010, Patrick Renkens wrote: > >>Date: Wed, 20 Jan 2010 12:07:58 +0100 >>From: Patrick Renkens <[log in to unmask]> >>Reply-To: LISTSERV site administrators' forum <[log in to unmask]> >>To: [log in to unmask] >>Subject: Prevent list-owners from adding subscribers >> >>Hi All, >> >>This might look like a weird question but I like to ask it anyway. >> >>Is there a way to prevent listwoners from adding additional subscribers, >>but still let them change other options? >> >>Kind regards, >>Patrick Renkens >> Centre for Information Services (UCI) >> Radboud University Nijmegen, Netherlands >> >>