Spamassassin For Win32 Systems

E.g. with a custom script hooked into filters.in.tab. It scans the header for Spam Assasin's tags and, moves the message to the appropriate user's diectory. Then it stops the message's further travel by return code.

Yes, that is what I figured out myself.
But I haven´t got a clue on how to make such a script.
The readme does not help me with that.

You can use any programming language for "scripting". You just need to parse the command line arguments and set the proper return codes.

If you are not used to program, please set your request into the scripting corner here.

Not much of an update, but I like the feature and I guess those who don't know any Perl will appreciate not having to code even this one line of Perl :

I want to be able to instantly see which message is spam and which isn't. Changing the subject seemed like the best way to do this. I changed

into

This way every message that is marked as spam bij SA will have a subject that starts with [spam].

I am running with Windows 2003. No problems per say yet. I am currently in the process of rewriting the filter provided by Don Drake (thanks!!!) to be more optimized for Windows since we don't have the use of SPAMD and SPAMC yet.

SA_Filter_Opt.zip

I've attached the optimized filter as well as some performance results I have collected in the past day or two (I'll send them again after a full week) - basically the new filter is running 40% or so faster (so far) - primarily because it uses the SpamAssassin API directly instead of calling out via system(). When system() is called it launches the .BAT file in the perl directory, then it launches perl.exe again. In effect your process tree ends up looking like this (using tlist.exe):

XMail.exe (680)
  perl.exe (1340)
        cmd.exe (744)
            perl.exe (2112)
    perl.exe (964)
        cmd.exe (2144)
            perl.exe (2152)
    perl.exe (2048)
        cmd.exe (2056)
            perl.exe (2120)
... etc

Instead of like this as you would want:
XMail.exe (680)
    perl.exe (1340)
    perl.exe (964)
    perl.exe (2048)

The use of memory was killing my server even though I run with 512 MB of ram. A secondary advantage of using SpamAssassin in this way is you can make different decisions about what to do with spam by using the instance of the status returned by check_message() or check_message_text(). Another interesting option might be to generate domain SpamAssassin prefs on the fly (like turning the threshold down to 5 or something like that), and passing them in via the factory constructor.

Note that I am using an older version of XMail so you will have to adapt the code to the newer return codes. Let me know if there are further ways to optimize this code that you see....we need the assassin to slice faster

into

This way every message that is marked as spam bij SA will have a subject that starts with [spam].

If I understand what you are trying to do here - it can be accomplished in SA's local.cf by using these two lines:

subject_tag *****SPAM*****
rewrite_subject 1

I tried unpacking that zip-file, but got an error message both with WinRAR and the WinXP build-in unzipper that there were no files to unpack. Something wrong with the file?

I have reposted the zip file - I believe the old one was corrupted for some reason. I have also included a log file with a run using the original sa_filter.pl and the sa_filter_optimize.pl.

I collected stats for over a week of use, the final outcome was an approximate 30% increase in performance instead of 40% as previously reported - still well worth the change.

OptSpamAssassin.zip

Let me know if anyone has comments.

Thanks,
-aaron

Thanks!

I hope you don't mind, I've been playing with it myself. If you have any comments, let me know!
download...

Important notes:

1. You'll need to install Config::Fast. at the DOS-prompt:

If you know of a better way to read config files, let me know!

2. I didn't want to check spam on every e-mail address and I want to be able to set-up different ways of working for different accounts. This version will ONLY check mail if the file SAFilter.cf is present in the mail folder (where also user.tab resides). Mails for other accounts aren't checked. This file can be empty, but if you put for example
MinHitsForDelete 10
in it, mails with over 10 hits will be returned to the sender

3. At the start of the script, don't forget to change the paths to both XMailserver and Perl! Also change SA_VERSION_HEADER. This is the complete line from the header that SpamAssassin adds to every e-mail it has checked.

4. Exit codes are for XMailserver 1.16 and above. I only tested with XMailserver 1.17. With this version adding
"*" "*" "0.0.0.0/0" "0.0.0.0/0" "safilter.tab"
to filters.in.tab did the trick, also for e-mail that gets forwarded. I however seem to remember that in 1.16, forwarded e-mail was only filtered with filters.out.tab



Might be interesting if you want to further optimize your own script: I noticed that e-mail that gets forwarded to an other account within the same server is checked twice. So I first check if the SpamAssassin header is present. If it is, the mail isn't checked anymore.

Give it a try an let me know what you think of it!