I've been thinking about doing something like what you're asking about to
deal with lists created each semester for courses.  I haven't really found a
simple solution, though.  The Change-Log feature (Change-Log= Yes) helps,
but the files take up quite a bit of space for very active lists.  It would
be really handy if Listserv could keep a "last post" date accessible via a
SHOW command for easier checking.  I currently keep an archive of list
requests which sometimes contain a termination date and use that information
to periodically clean up my lists.  I hope you find a solution.

C. David Young
Central Systems Support
University Of Texas At Arlington
mailto:[log in to unmask]
Voice: (817) 272-3666
Fax: (817) 272-5796


> -----Original Message-----
> From: Kathy Montgomery [SMTP:]
> Sent: Wednesday, September 15, 1999 6:06 PM
> To:   [log in to unmask]
> Subject:      List expiration?
>
> Has anyone here successfully implemented a system of list
> expiration/renewal at their site?  I don't mean *subscription*
> renewal.... for example, if a user requests a list on my server, I want
> to be able to track the age of the list and then know after, say, 6
> months, get rid of it.  I find this desirable because professors often
> request lists for their classes, which, of course, usually last only a
> semester.
>
> I have thought of using a database to track the lists I create, then
> generate reports to know which lists I can erase.  However, perhaps
> there an easier, "LISTSERV" way to do it.  If some such method is in the
> docs, please point me there. :)
>
> - Kathy Montgomery
> LISTSERV Manager
> University at Albany