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




-----Original Message-----
From: LISTSERV site administrators' forum [mailto:[log in to unmask]] On Behalf Of Rich Greenberg
Sent: Tuesday, June 14, 2011 4:34 PM
To: [log in to unmask]
Subject: Re: List refusing to be freed

On: Tue, Jun 14, 2011 at 10:51:34PM +0000,Bruce Keppler Wrote:

} I have a list that is apparently being held by the system.  Users who attempt to post get the following:
}
} The distribution of your message dated Fri, 10 Jun 2011 17:38:37 -0700 with } subject "This is the subject" has  been postponed because } the THELIST list is held. No  action is required from you. Your message } will be reprocessed automatically once the list owner releases the list.
}
} I issue the command FREE THELIST and it tells me 21 files have been released.  Shortly thereafter I receive this email (as list admin):
}
}
} An error  occurred while logging mail  to the archives of  the THELIST list. An  incomplete copy of the  message might be present  in the archive file. The list is being held to prevent further occurrences of this error.
}
} Please take corrective action and  issue a "FREE THELIST" command when you want the message to be reprocessed.
}
} Obviously, freeing the list again only solicits the same reply.  I've checked the permissions on the archive folder and they appear to be the same as the other lists I'm running that don't experience this problem.  This list and archive has worked and does have messages displayed.  I've run ProcMon on the machine but it didn't turn up any file ACCESS DENIED errors.
}
} Any ideas what I can do to troubleshoot this problem?

Is the archive data space full?  Perhaps you could do an INDEX and purge the oldest portion (download it first if you want to save it).

--
Rich Greenberg  Sarasota, FL, USA richgr atsign panix.com  + 1 941 378 2097
Eastern time.  N6LRT  I speak for myself & my dogs only.    VM'er since CP-67
Canines: Val, Red, Shasta, Zero & Casey (At the bridge)        Owner:Chinook-L
Canines: Red & Cinnar (Siberians)  Retired at the beach  Asst Owner:Sibernet-L

############################

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

############################

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