User Tools

Site Tools


spamassassin:stopping_spam

This is an old revision of the document!


SpamAssassin - Stopping Spam

Install Mail::Audit

SpamAssassin needs the Mail::Audit module for Perl. Install Mail::Audit (via CPAN)

perl -MCPAN -e shell
cpan> install Mail::Audit
cpan> quit

Install Spam Assassin Modules

Install SpamAssassin from CPAN, which will also install all other required modules too.

perl -MCPAN -e shell
cpan> install Mail::SpamAssassin

It maybe will ask you for some needed modules that aren't installed yet - Answer yes and Perl will fetch and install them, too.

cpan> quit

First look if the install succeded by running:

which spamassassin
/usr/local/bin/spamassassin

If you don't get a right answer something failed… or your PATH-variable isn't set right…

Now lets scan a no spam mail with

spamassassin -t <sample-nonspam.txt |less

Look for a line like this in the output:

X-Spam-Status: No, hits=0 required=5 tests=

Okay fine - now try a bad spam message:

spamassassin -t <sample-spam.txt |less

which should produce some lines like that:

X-Spam-Status: Yes, hits=12 required=5 tests=NO_REAL_NAME,UNDISC_RECIPS,INVALID_DATE,MSGID_HAS_NO_AT,REMOVE_SUBJ,RCVD_IN_OSIRUSOFT_COM
X-Spam-Flag: YES

Okay everything seems working… that was the easy part :-)

The wrapper script

For use with Exim here is a small Perl script which implements the Mail::Audit and the Mail:SpamAssassin module. It will do the actual scanning and will feed a good message back to the Exim MTA with the protocol “spam-scanned”. Install the attached spamcheck.pl to /usr/local/bin.

#!/usr/bin/perl
# This is an small wrapper script around Mail::SpamAssassin for the use
# with the exim MTA.
# Modified to eliminate the buggy Mail::Audit use.
# This modification also eliminates the need to re-submit the message
# to Exim for delivery to the mail spool. Requires localuser director
# to use the spamcheck transport so it knows where to append to.
# It is released under the Terms of GNU General Public License (GPL) so
# use at your own risk!
 
use Mail::SpamAssassin;
use Mail::SpamAssassin::NoMailAudit;
 
$savespam = 1;                      #1/0 should spam be saved centrally?
$spamfile = '/var/mail/spam';       #If you said 1 above - where to put
                                    #that nasty spam? Be sure this mailbox
                                    #is writable by the user who runs this
                                    #script (e.g. mail)
#These are given as command line arguments by exim:
$sender = shift(@ARGV);
$sender = '<>' if $sender eq '';
$recpt = '';
while (@ARGV){
  $recpt = $recpt.' '.shift(@ARGV);
}
 
####### Main script ###########################################################
 
$mail = Mail::SpamAssassin::NoMailAudit->new();
 
$spamtest = Mail::SpamAssassin->new();
$status = $spamtest->check ($mail);
 
#Add the X-Spam Headers:
$status->rewrite_mail ();
#Auto Report to Vipul's Razor:
$status->handle_auto_report ();
 
if ($status->is_spam ()) {
  if ($savespam) {
    $mail->accept($spamfile); # Deliver to spamfile
  } else {
    $mail->accept();          # Deliver to user's mailbox
  }
} else {
  $mail->accept();            # to default incoming mailbox
}

NOTE: Ensure the path to exim is correct and if you want to store detected spam in a mailbox - be sure this mailbox exists and is writeable by the user 'mail'. If not simply create one like this:

touch /var/spool/spam
chmod 660 /var/spool/spam
chown mail:mail /var/spool/spam 

References

spamassassin/stopping_spam.1478045571.txt.gz · Last modified: 2020/07/15 09:30 (external edit)

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki