On Tue, 22 Feb 2000, Alan S. Dobkin wrote: > Stan, > > I've seen this error occur when the LISTSERV process does not have > access (via the OS/filesystem) to the archive directory in question. Thanks, but access was definitely not a problem. Listserv was able to append messages onto the particular list's log file, but it still generated those error messages and placed the list on hold. I finally fixed the problem by tinkering with the list.