The particular piece of mail could be the trouble - it may, for instance, be very large, or malformed. So far as I am aware there is no "LISTSERV Way" to address this issue by command or via the web interface. Locate the item in the LISTSERV Spool directory and move it elsewhere - it is likely to be the oldest file present - then issue FREE again and observe the results. Once the item is identified, it can be viewed with a text editor. After you learn what it contains you can decide what to do next - discard it, ask the author to try again, etc. On 6/14/2011 7:41 PM, Bruce Keppler wrote: > I don't think so - the list has only been running for a short time and logged the activity for about two weeks then it went silent. I checked the ListServ logs and found the following entry each time I tried to free the list: > > 14 Jun 2011 15:33:48 To [log in to unmask]: The THELIST list has been freed, 21 files have been released. > 14 Jun 2011 15:33:48 Processing file 8626 from [log in to unmask] > 14 Jun 2011 15:33:48 -> Removing unwanted MIME message parts... > 14 Jun 2011 15:33:48 Processing mail from [log in to unmask] for THELIST > 14 Jun 2011 15:33:48 Digest size limit exceeded, sending special issue... > 14 Jun 2011 15:33:48 Reindexing THELIST LOG1106B... > Load_index: V=0 T=0 size=320k > 14 Jun 2011 15:33:48 To [log in to unmask]: An error occurred while logging mail to the archives of the THELIST (...) > > There is nothing in the Digest Maximum Size field for this list. Every instance where I tried to free the list is exactly identical (except the time stamp). Is there perhaps something wrong with the mail from [log in to unmask] > > > Thanks, > > Bruce ############################ To unsubscribe from the LSTSRV-L list: write to: mailto:[log in to unmask] or click the following link: http://peach.ease.lsoft.com/scripts/wa.exe?SUBED1=LSTSRV-L&A=1