Simple solution:

move the lsv_amin executable that mail is handed to to a new location

replace with the following script:

----------
#!/usr/bin/perl
use Mail::Audit;
my $mail = Mail::Audit->new();
foreach $line ($mail->body()) {
        foreach $unwound (@$line) {
                if ($unwound =~ /(cmd1|cmd2|cmd3|...)\s/i) {
                        $DUMPIT=1;
                        }
                }
        }
$spool = shift @ARGV;
$tos = join ' ', (@ARGV);
if ($DUMPIT == 1) {
        $mail->ignore;
        } else {
        $mail->pipe("/path/to/real/lsv_amin  $spool $tos");
        }
exit;
------------

Now prohibited commands go to /dev/null

Rich Greenberg wrote:
> On: Tue, Dec 12, 2006 at 11:42:05PM -0600,Winship Wrote:
>
> } My understanding was that, from several versions back, LISTSERV was
> } supposed to be sensitive to commands missent to the list address,
> } automatically bouncing same back to the poster.  Just what commands is
> } it sensitive to?  And from whom?
> } 
> } Why does it not block a "SCAN listname ...."  command accidentally sent to
> } the list by the listowner?
> } 
> } For that matter, why doesn't it block items which have
> } "LISTNAME: approval required ........" in the Subject: ?  (Yes, I've been
> } known to send those approval items accidentally to the list, and they sail
> } right through.)
>
> With the availability of the content filtering, perhaps Lsoft assumed
> you would roll your own.
>
>   

-- 
Christopher Wilson
Information Systems Coordinator
ISS Enterprise Systems
The George Washington University
202-994-3878
[log in to unmask]