You can't define dynamic FACs that way under non-VM.  You have to define
who can get and put the file in the GET and PUT FACs directly for each
file.  For instance,
 
my.file my.file ALL [log in to unmask],[log in to unmask],OWNER(MYLIST-L)
 
and the catalog entry would look like this when INDEXed:
 
*                                       rec             last - change
* filename      filetype        GET PUT -fm lrecl nrecs date     time
* --------      --------        --- --- --- ----- ----- -------- --------
  MY            FILE            ALL MSC V     162    26 96/10/24 11:01:19
 
The "MSC" FAC indicates that the file has a special FAC that can't be
described by the standard FAC codes.  In this case it would be a file
that could be PUT by me, Eric, or the owner(s) of MYLIST-L.
 
As long as all of this is on a single line, btw, I don't think LISTSERV
cares how long the line is (unless there's a 255-character limit I'm
not aware of).  I've got some on PEACH that are pretty long :)
 
Technically it should be simple to create lists that you could then use
like custom FACs.  For instance, you could create a BED-FAC list with a
header like this:
 
* BED FAC list
* Confidential= Yes
* Subscription= Closed
* Review= Owners
* Owner= [log in to unmask] (David Bedell - U. of Bridgeport)
* Owner= [log in to unmask] (Robert Ponterio - FLTEACH)
* Owner= [log in to unmask] (Jean LeLoup - FLTEACH Owner)
 
and then define your files like this:
 
flteach.catalog   flteach.catalog ALL OWNER(BED-FAC)
flteach.welcome   flteach.welcome ALL OWNER(BED-FAC)
flteach.farewell  flteach.farewell ALL OWNER(BED-FAC)
 
(Naturally you'd want to put the full paths in; you didn't indicate what
they were, so I couldn't do that:)  If you did it this way, it would be
simple to update the FAC list; just add or delete list owners from BED-FAC.
 
Nathan