As a test project this past semester we initiated a program where students registered in our Distance Ed. Classes would subscribe to their class listserv list. These students were located all over Canada. This project was such a success that they (Distance Ed. Dept.) would like to keep the program going. I'm wondering if this is being done at other sites and if so, I have some questions of the listserv maintainers/postmasters at these sites. So far we have 11 listserv lists. I'm not a lazy person, but I work two jobs already and now I find that I have to edit the headers of all these lists once classes are over. The numbers are sure to rise by the Fall semester. My questions. 1. What would be the most appropriate header to change that would require the least amount of effort to enable? I could set "Confidential= Yes" to all of them I suppose...but we would still get local folks sub'ing out of curiosity. Certainly the "owner=" header would have to be set to 'none' if it is a supported option. (I seem to recall that it may not be supported for version 1.8b) 2. Is there an alternative that someone else has come up with to replacing the headers? (Like a script of some kind? :-)) I supose I could put these lists all in their own directory and run a script to replace the "Subscription=" to "closed". Making the Distance Ed Dept. responsible isn't an option as this program was set up with the agreement that the postmaster would enable/disable class lists for this program. Umm...*blush* this was my suggestion since I wanted the program to fly..and it would have gone nowhere otherwise. So, now I'm looking for an easy way to manage it. My stats: Listserv, version 1.8b running on IRIX version 5.2 (Mmm.. that means it is a unix machine.) Any suggestions/ideas/solutions most welcome. If I don't find a solution and end up writing a script, I will certainly share it....but it would probably be a REXX program for unix....and thus only portable to VM or sites that have REXX. Your time is much appreciated! Thanks! Sincerely, Trish -- Trish Forrest, Computing Services, University of Windsor