
HOWTO
<DISCLAIMER>This is a work in progress. Feel free to post your comments and recommend changes. To somewhat simplify things for new users, I've been considering creating a preconfigured hMS/ASSP package. At any rate, here it goes. Hope you enjoy the ride...</DISCLAIMER>
Download and install ActivePerl, version 5.6.1.638 -- in my experience, version 5.8.7.813 was unstable and kept on crashing. Grab the MSI package - registration is not required. During its install, select all defaults.
From Start>Programs>ActiveState Active Perl..., launch the "Perl Package Manager" and execute the following command:
Code: Select all
install http://www.roth.net/perl/packages/win32-daemon.ppd
Create the following directories:
Code: Select all
C:\ASSP\errors
C:\ASSP\errors\spam
C:\ASSP\errors\notspam
C:\ASSP\notspam
C:\ASSP\spam
Code: Select all
C:\ASSP\spamdb.bak
C:\ASSP\eicar.db
Code: Select all
Eicar-Test-Signature=58354f2150254041505b345c505a58353428505e2937434329377d2445494341522d5354414e444152442d414e544956495255532d544553542d46494c452124482b482a
Open C:\ASSP\assp.pl in your favorite text editor and change the line:
Code: Select all
[AsAService,'As a Service',0,checkbox,'0','(\S*)',undef,
Code: Select all
[AsAService,'As a Service',0,checkbox,'1','(\S*)',undef,
Code: Select all
perl addservice.pl -i C:\ASSP\assp.pl C:\ASSP
Code: Select all
perl addservice.pl -s
Configure away! Here are some directives I would recommend changing:
Network Setup
SMTP destination: 127.0.0.1:125 (Note: change hMailServer's SMTP service to listen on port 125 prior to commiting this change)
(Leave everything else at their defaults, or deselected/blank)
Listen Port: 25
SPAM Control
Add Spam Probability Header?: [Selected]
Add Spam Header?: [Selected]
Use Subject as Maillog Names: [Selected]
(Leave everything else at their defaults, or deselected/blank)
Whitelist Options
(Leave everything at their defaults, or deselected/blank)
Relaying
Local Domains: yourdomain.com|yourotherdomain.com
(Leave everything else at their defaults, or deselected/blank)
Validate Recipients
No-Valid-User Reply: 250 OK - Recipient <EMAILADDRESS>
Validate recipient addresses to conform with RFC 822: [Deselect, or install Email::Valid]
Do LDAP lookup for valid recipients: [Deselect]
{All other LDAP Options} [BLANK OUT]
SPF Options
(Leave everything at thei r defaults, or deselected/blank)
RBL Options
(Leave everything at their defaults, or deselected/blank)
Virus Control
List of Anti-virus Signature Database Files: main.db,daily.db,eicar.db
(Leave everything else at their defaults, or deselected/blank)
Spam Bombs & Scripting
(Leave everything else at their defaults, or deselected/blank)
TestMode Options
(Put everything into Test Mode)
Prepend Spam Subject: [SPAM]
Email Interface
Report Spam Address: spam
Report not-Spam Address: notspam
Add to Whitelist Address: whitelist
From Address for Email: ASSP <postmaster@yourdomain.com>
File Paths
PID File: [BLANK OUT]
(Leave everything else at their defaults, or deselected/blank)
Logging
Roll the Logfile How Often?: 1
(Leave everything else at their defaults, or deselected/blank)
Security
Web Admin Password: <CHANGE PASSWORD>
(Leave everything else at their defaults, or deselected/blank)
Other Settings
(Leave everything else at their defaults, or deselected/blank)
The next step is to collect at least a few thousand SPAM and non-SPAM messages. This will occur automatically and all messages will initially be placed into C:\ASSP\spam. You will need to manually move all misclassified non-SPAM messages into C:\ASSP\notspam. Once you have accumulated a good sample of both good and bad messages, run the 'rebuildspamdb.pl' script. The more often you do this during the testing stage, the more accurate it will become.
Eventually you should schedule the 'rebuildspamdb.pl' to run automatically once or twice every day, preferably at a time when your mail server is less active -- the script will consume many CPU cycles, and depending on how fast your system is and the amount of messages it has to analyze, this could take many minutes. Also, it would be a good idea to schedule freshclam.bat to look for updates regularly (no more often than once every hour is highly advised). You can accomplish both of these as scheduled tasks -- for freshclam's scheduled task, go into the advanced settings, have the task repeat (no more than once) every hour, and set the duration to 23 hours and 59 minutes.
Once you're confident that ASSP is well-tuned, your last step is to take it out of "Test Mode" and introduce it to your users. More information about this can be found in ASSP's online documentation, which would be good to review during the testing period.