
The current version of this guide is here:

   http://www.asspsmtp.org/wiki/Quick_Start_for_Win32


Quick Start for Win32

Installation

   1. Download and install the latest version of Active Perl (Version
   5.8.8.8 or newer). As you move through the installation wizard,
   make sure the option "Add Perl to the Path environment variable" is
   selected.

   2. Click on Start ? Programs ? Activestate Perl 5.x.x build ### ?
   Perl Package Manager.

   3. At the PPM (Perl Package Manger) command line, type "query *"
   and make a note of which of the following modules are not
   installed. (Note: Not all modules are mandatory, but it is
   recommended that you install all of the modules. If all modules are
   not installed, the Perl process may use 99% of the processor time).

          * compress-zlib
          * digest-md5-file
          * email-valid
          * file-readbackwards
          * mail-spf-query
          * mail-srs
          * net-dns
          * perl-ldap
          * time-hires
          * win32-daemon

   4. At the PPM command line, type install and then the module name
   (as listed above) to install new modules. By default, the install
   command will install the modules and all dependencies. The win32-
   daemon module must be installed using the following command:

      install http://www.roth.net/perl/packages/win32-daemon.ppd

   5. At the PPM command line, type the following to update all
   installed packages:

      upgrade -install -precious

   6. Now create the following directory structure:

          * c:\assp
          * c:\assp\notspam
          * c:\assp\spam
          * c:\assp\errors
          * c:\assp\errors\notspam
          * c:\assp\errors\spam

   7. Download the Anti-Spam SMTP Proxy (ASSP) distributable and
   extract the contents to the c:\assp base directory.

   8. Open the command line and navigate to the c:\assp directory, and
   Execute the following command:

      perl addservice.pl -i c:\assp\assp.pl c:\assp

   9. Click on Start ? Settings ? Control Panel ? Administrative Tools
   ? Component Services ? Services and start the ASSP service; set the
   ASSP service to start automatically.

  10. Open a web browser and point it to http://127.0.0.1:55555. At
  the login screen, the default password is nospam4me. The username is
  left blank.

  11. Expand the Security section of the menu, select the
  webAdminPassword option, and change the default password.

  12. You can also edit the file that blacklists IP addresses by
  clicking on the Edit File button located next to the Deny SMTP
  Connections From These IPs option.


Setup via the Web Interface

(under development)

Information for End-Users

The senders of emails that you will never respond to and/or have spam
qualities must be manually whitelisted.

    * Example 1: A department store sends you a sales catalog ? you
    won't respond to this email and it has spam qualities ? manually
    whitelist the sender.

    * Example 2: You receive a weekly email informing you of the
    upcoming weather forecast ? you won't respond to this email ?
    manually whitelist the sender.


Hand-outs

Empower your end-users by giving them useful user tips and
instructions that will help make dealing with spam easier for them.

Special Notes

Legitimate spam presents a unique situation. By default, the Bayesian
Non Spam option (located in the Logging section) is set to save into
the notspam directory all incoming emails that receive a Mail Ok
status (Note: in order for the mail to get saved in the notspam
directory, the notspam directory must also be specified as the path
for the Bayesian Non Spam directory in the Paths section). If you do
not specify the notspam directory as the Bayesian Non Spam directory
(located in the logging section), emails that receive a Mail Ok status
will not be saved.

Why is saving incoming emails that receive a Mail Ok status in the
notspam directory bad?

    * When rebuildspamdb.pl is run manually or by a scheduled task,
    the spam email that is in the notspam directory will be analyzed.
    The results of the analyzation will be added to the good content
    portion of the spamdb. Having spam content in the good content
    portion of the spamdb will cause spam emails to get a lower score
    when processed by the Bayesian filter. The more spam emails that
    get saved to the notspam directory, the more corrupt the corpus
    will become.

Where should incoming emails be saved?

    * First of all, emails from whitelisted users will be saved into
    the notspam directory. Earlier you were instructed to change the
    Bayesian Non Spam store location to 4. Specifying 4 as the logging
    path for Bayesian Non Spam will allow you to save incoming emails
    that receive a Mail Ok status to the directory you specify in the
    Bayesian Non Spam directory option (located in the Paths section).

What else can I do to keep the corpus from corrupting?

    * The option Keep Whitelisted Spam (located in Whitelist Options
    section) must be unchecked; this will remove emails of whitelisted
    senders that received a Spam status before the sender was
    whitelisted from the spam directory when rebuildspamdb.pl runs
    (this ensures that the corpus is corrected).


