Nice idea, but one big snag - our end-user environment is all Windows (9x, working on rollout of Win2k), our primary servers are Novell NetWare, our email system is GroupWise, and the LISTSERV is on NT.  Neither I nor anyone else around here has a clue about anything *nix based.

>>> [log in to unmask] 04/02/01 10:37AM >>>
On Mon, 02 Apr 2001 10:18:46 EDT, Kevin Parris <[log in to unmask]>  said:

> Please consider moving the text of the Spamming Alert notice
> messages into a template so I can chop it out, since after I've seen
> the first twenty dozen of them all I really need any more is the
> "original alert" portion.  Or alternatively, implement a new
> configuration keyword something like "SpamAlertNotice= full |
> brief".  Thank you.

This looks like a job for procmail:

:0
*^Subject:.*spamming alert.*
{
  :0 :list-spams/$LOCKEXT
  *^From:.*listserv@listserv
  |sed -e '/^A *network/,/^----/d' | rcvstore +list-spams

  :0
  /dev/null
}

(The double test was for when we had 3 listserv servers, so only one
would actually be saved).  Basically, if it's from our listserv server,
and the subject contains 'spamming alert', it strips out the boilerplate
before saving it.

Even has the nice side-effect of *not* doing the stripping if it's a
person posting to a local list (as that message doesn't start off with
"A network..")

--
                                Valdis Kletnieks
                                Operating Systems Analyst
                                Virginia Tech