view release on metacpan or  search on metacpan

INSTALL  view on Meta::CPAN

            ./sc_BLcheck.pl -d path/to/config.file
            ./sc_BLcheck.pl -v path/to/config.file

      The -d switch allows you to see what the 
      script will do without any db updates 
      taking place. The -v switch will print
      the scripts actions to the screen. 
      -v -v does it more verbosely.
      The -d switch implies a single -v.

    In the ./config directory

      cp sc_BLackList.conf.sample sc_BLackList.conf

    The sc_BLackList.conf file is heavily commented and pre-loaded with
    several working DNSBLS entries. You may wish to delete some of these or
    add one of your favorite ones.

   activating sc_BLpreen.pl

    sc_BLpreen.pl periodically validates the entries found in the blcontrib
    database and removes those which the original DNSBLS no longer
    blacklists or those for which the DNSBLS can not be contacted for a time
    specified in the config file for that DNSBLS.

    Login as the spamcannibal user and put an entry in your crontab
    something like this:

      # check valid blcontrib every few days
      21 0 */4 * * ./scripts/sc_BLpreen.pl ./config/sc_BlackList.conf

    Since this is a background job, a better entry might be:

      21 0 */4 * * /usr/bin/nice -n 20 ./scripts/sc_BLpreen.pl ./config/sc_BlackList.conf

      Syntax: ./sc_BLpreen.pl path/to/config.file
        or
            ./sc_BLpreen.pl -d path/to/config.file
            ./sc_BLpreen.pl -v path/to/config.file

      The -d switch allows you to see what the 
      script will do without any db updates 
      taking place. The -v switch will print
      the scripts actions to the screen. 
      -v -v does it more verbosely.
      The -d switch implies a single -v.

   activating sc_cleanup.pl

    sc_cleanup.pl periodically runs through the databases and *optionally*
    expires very old records and checks that there are not multiple entries
    in the database for the same IP address or an entry that is present in
    one database that is missing a corresponding entry in a companion
    database.

    For example:

      A spam messages arrives and makes it through the system to your in
      box. Subsequently, sc_BLcheck.pl finds the IP address of the spam host
      in a remote DNSBL and adds records to the tarpit and blcontrib
      databases. You find the spam on your desktop and add it to the tarpit
      and evidence databases via the sc_mailfilter.pl robot script. Now
      there is an extra record in blcontrib that is unused.

    There are many more possible ways for such inconsistencies to occur and
    sc_cleanup.pl removes these records automatically.

    Login as the spamcannibal user and put an entry in your crontab
    something like this:

      # check valid blcontrib every few days
      21 0 */4 * * ./scripts/sc_cleanup.pl

    Since this is a background job, a better entry might be:

      21 0 */4 * * /usr/bin/nice -n 20 ./sc_cleanup.pl

      Syntax: scripts/sc_cleanup.pl -q
        or
            scripts/sc_cleanup.pl -d
            scripts/sc_cleanup.pl -v
        or
            scripts/sc_cleanup.pl [options] -x nnn

    The -q switch is for normal, quiet operation. The -d switch allows you
    to see what the script will do without any db updates taking place. The
    -v switch will print the scripts actions to the screen. The -d switch
    implies a -v.

    The -x switch expires records more than 'nnn' days old and removes them
    from the database.

  Setting up the DNS blacklist daemon

    The first part of the installation guide assumes that the host has no
    other DNS daemon running. Section 2 covers running a DNSBL along with a
    conventional DNS. In either case, an NS record must be added to the zone
    file for the blacklist domain.

    Login as the spamcannibal user.

      cd ./config
      cp dnsbls.conf.sample dnsbls.conf

    Edit dnsbls.conf for your site. The file is heavily commented and should
    be self explanatory. Your comments and additions to this documment are
    welcomed.

    Most of the configuration items do not need changing. What MUST be
    specified for which the defaults usually must be changed are the
    following:

            zonename
            contact
            ns
            127.0.0.2

   standalone DNSBL service

    For stand alone service, nothing more is necessary except execution of
    the start script.