Great idea. I'll try that. ..Chris.. At 03:34 PM 2/19/2003 -0500, you wrote: >One idea is to set your subscribers to NOMAIL, then free up the >list. WIth this setting >mail will be posted to the list but not to subscribers. Then, you can >edit the archives to >remove the corrupted entries, reset your subscribers to receive mail, and >resume >delivery to the list. > >Otherwise, unless you are also a site administrator and have permissions >to remove >mail from the LISTSERV spool there isn't really anything you can do. If >you are not a >site administrator you will probably need to contact someone that you can >work with to >remove the jobs. > >Richard Keller > > > I've already looked through the archives but didn't find an answer > > that jumped out at me so I'm asking here. > > > > I have a weather-related list which automatically posts certain > > tropical storm-related bulletins sent from the NWS to the list. A > > communications problem resulted in a bunch of garbled messages being > > sent and LISTSERV's SPAM filter didn't recognize the problem (since > > each message was technically unique). What did happen is that the > > posting limit was reached and the list is currently held. Since old > > weather data is not important to people and since garbled weather data > > is of even less importance, I want to flush the queue before releasing > > the list. Is there an easy way that I, as a list owner, can do this? > > There's no point in releasing tons of garbage mail --only to flood > > people's mailboxes with what amounts to SPAM. > > > > Thanks. > > > > ..Chris..