On Sun, 4 Apr 1999 16:10:38 -0400, Listserv Admin <[log in to unmask]>
wrote:

>An error occurred while logging mail to the archives of the PAINPAL-L
>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 PAINPAL-L"  command when
>you want the message to be reprocessed.
>
>Well, I can try deleting the dbindex, dbnames, etc files and let Listserv
>rebuild them... I checked the logs and I noticed at midnight, the digest
>file didn't got out at all... maybe that is the problem.

This indicates a "stuck" condition, that usually is caused by someone
attempting to edit the current message log file.  The Logfile gets out of
sync with the digest, the digest cannot be issued and will continue to build
up, the list continues to be held, you free it, it holds again, etc.  This
is a circular trap and is one reason why we suggest you do NOT edit the
current log file.

The solution is to delete the digest (by setting Digest= No in the list
header, put the header, then reset the digest to what it was set at).  This
means digest subscribers miss that digest.  Sorry.