|
Mime-Version: |
1.0 |
Sender: |
|
Subject: |
|
From: |
|
Date: |
Wed, 19 Feb 2003 16:06:24 -0500 |
In-Reply-To: |
<3E53A3ED.4766.202DE042@localhost> |
Content-Type: |
text/plain; charset="us-ascii"; format=flowed |
Reply-To: |
|
Alternative:
SEND= EDITOR,CONFIRM,HOLD
EDITOR= you
RELEASE list
Wait for avalanche ;-)
then reverse (set back to "normal")
/Pete
At 15:34 02/19/2003 Wednesday, Rich Keller 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).
|
|
|