With release 1.5c of LISTSERV the "Send=" keyword syntax has been expanded as
follows:
 
Send= Editor | Public | Postmaster | item1,item2,item3...
      ----------------------------   --------------------
             group 1 options             group 2 options
 
Group 1 and group 2 options are mutually exclusive. Only one group 1 option can
be specified while any number of group 2 options is acceptable.
 
item= Owner | Private | (listname) | Owner(listname) | Service |
      Service(listname)
 
Example (let's say the list name is COMM-L)
 
  Send= Private,(COMM2-L),(COMM3-L)
 
--> Anybody subscribed  to COMM-L,  COMM2-L or  COMM3-L can  mail to  the list.
 
  Send= Owner,Owner(COMM2-L),(BIGWIG-L)
 
--> Any member  of BIGWIG-L, as  well as the owners  of COMM-L or  COMM2-L, can
    send to the list.
 
Send= Owner,Service
 
--> All the owners of COMM-L and all the people in the service area of the list
    can send to it.
 
  This new syntax can be used for the  "Owner=" keyword as well, that is if you
want a given 'staff' to own all the  COMMx-L list on your server, but you don't
want to  have to edit ALL  the lists when one  of the members of  this staff is
changed, you can defined a list STAFF-L  with all the members of that staff and
set all the  COMMx-L lists to "Owner= (STAFF-L) Computing  services staff". The
STAFF-L would be owned by a  "Master" staff person who's responsible for adding
or removing people from the list, while members can't add new members. Alterna-
tively you  might prefer to  define the staff people  as owners of  the STAFF-L
and set "Owner= Owner(STAFF-L)" (this would be more complicated to maintain but
more efficient  technically -- owners are  kept in GLOBALV storage).  Of course
"Service" is not a valid argument for the "Owner=" keyword.
 
  I hope this solves your committee lists problem.
 
Regards,
         Eric