DSpam README - Revision history

Ledhed: /* ALIASES */

2009-07-27T23:27:12Z

‎ALIASES

Ledhed: /* DSPAM TOOLS */

2009-07-27T22:29:41Z

‎DSPAM TOOLS

Ledhed: /* DSPAM TOOLS */

2009-07-27T22:28:09Z

‎DSPAM TOOLS

Ledhed: /* DSPAM TOOLS */

2009-07-27T22:27:15Z

‎DSPAM TOOLS

Ledhed: /* DSPAM TOOLS */

2009-07-27T22:26:29Z

‎DSPAM TOOLS

Ledhed: /* TROUBLESHOOTING */

2009-07-27T21:26:50Z

‎TROUBLESHOOTING

Ledhed: /* TROUBLESHOOTING */

2009-07-27T21:26:38Z

‎TROUBLESHOOTING

Ledhed: /* INTEGRATION SWITCHES */

2009-07-27T21:23:20Z

‎INTEGRATION SWITCHES

Ledhed: /* BUGS, PORTS, AND THE LIKE */

2009-07-27T21:20:51Z

‎BUGS, PORTS, AND THE LIKE

Ledhed: /* BUGS, PORTS, AND THE LIKE */

2009-07-27T21:19:25Z

‎BUGS, PORTS, AND THE LIKE

@@ Line 565: / Line 565: @@
 Because DSPAM learns each user's specific email behavior, it's necessary to identify the user in order to program their specific filtering database. This can be done in one of three ways:
-<br>
-====== The Simple Way ======
 If you are using the MySQL or PgSQL storage drivers, the original numeric user id can be embedded in the signature, requiring only one central spam alias to be necessary for the entire system. To configure this, uncomment the appropriate UIDInSignature option in dspam.conf:
@@ Line 584: / Line 585: @@
 The 'root' user represents any active dspam user. It is necessary to supply a username on the commandline or DSPAM will bail on an error, however the user will be changed internally once the signature is read.
-<br>
-====== The Kind-of-Simple Way ======
 If you're not using one of the above storage drivers, the next easiest way to configure aliases is to have DSPAM parse the 'To:' header of the message and use a catch-all subdomain to direct all mail into DSPAM for retraining. You can then instruct your users to email addresses like 'spam-bob@relearn.domain.tld'. The ParseToHeaders option (available in dspam.conf) will parse the To: header of forwarded messages and set the username to either 'bob' or 'bob@relearn.domain.tld', depending on how it is configured. DSPAM can also set the training mode to either "learn spam" or "learn notspam" depending on whether the user specified a spam- or notspam- address in the To: header.
@@ Line 599: / Line 601: @@
   ChangeModeOnParse on
-<br>
-====== The Old Way (A.K.A. The Hard Way) ======
 If neither of the easy ways are possible, you're stuck with doing it the hard way. This means you'll need a separate spam alias (and notspam alias, if users are tagging mail) for each user. To do this, you will need to create an email address for each user, so that DSPAM can analyze and learn for that specific user.  For example:

@@ Line 873: / Line 873: @@
   dspam_clean
 Performs nightly housecleaning by deleting old or useless data from user data.  dspam_clean performs the following operations:
 . Using the -s flag, dspam_clean will continue to perform stale signature purging.  If an age is specified, for example -s14, the age defined as the default will be overridden. Specifying an age of 0 will delete all signatures for the users processed.
@@ Line 882: / Line 883: @@
   - Tokens which have only one spam hit
   - Tokens which have only one innocent hit
-−
 Ages may be overridden by specifying a format such as -u30,15,10,10 where each number represents the respective age.  Specifying an age of zero will delete all unused tokens in the category. Defaults are set in dspam.conf.

@@ Line 907: / Line 907: @@
 ''NOTE:''<br>
 You may wish to only run certain cleaning modes depending on the type of storage driver you are using.  For example, the MySQL storage driver includes a script which performs signature and unused token operations, leaving only probability operations as useful.  If you are using a SQL-based storage driver, it is strongly recommended that you use the maintenance scripts wherever possible for optimum efficiency.
   dspam_stats
@@ Line 916: / Line 917: @@
   dspam_genaliases
 Reads the /etc/passwd file and outputs a dspam aliases table which can be included in the master aliases table.  You may try Art Sackett's generate_dspam_aliases tool at http://www.artsackett.com/freebies/generate_dspam_aliases/ if you need some better functionality.  This will eventually be merged in as a replacement for the existing tool.
-−
   dspam_merge
 Merges multiple users' dictionaries together into one user's dictionary (does not affect the merge users).  This can be used to create a seeded dictionary for a new user, or to copy a single user's dictionary to a new file.  This is great for building global dictionaries, but crunches a lot of time and disk.

@@ Line 904: / Line 904: @@
 Run dspam_clean with all default options, all clean modes enabled, on all users on the system:
   dspam_clean -s -p -u
 ''NOTE:''<br>
 You may wish to only run certain cleaning modes depending on the type of storage driver you are using.  For example, the MySQL storage driver includes a script which performs signature and unused token operations, leaving only probability operations as useful.  If you are using a SQL-based storage driver, it is strongly recommended that you use the maintenance scripts wherever possible for optimum efficiency.
-dspam_stats
+ dspam_stats
 Displays the spam statistics for one or all users on the system.
 Syntax: dspam_stats [username]
@@ Line 915: / Line 914: @@
-dspam_genaliases
+ dspam_genaliases
 Reads the /etc/passwd file and outputs a dspam aliases table which can be included in the master aliases table.  You may try Art Sackett's generate_dspam_aliases tool at http://www.artsackett.com/freebies/generate_dspam_aliases/ if you need some better functionality.  This will eventually be merged in as a replacement for the existing tool.
-dspam_merge
+ dspam_merge
 Merges multiple users' dictionaries together into one user's dictionary (does not affect the merge users).  This can be used to create a seeded dictionary for a new user, or to copy a single user's dictionary to a new file.  This is great for building global dictionaries, but crunches a lot of time and disk.

@@ Line 920: / Line 920: @@
 dspam_merge
 Merges multiple users' dictionaries together into one user's dictionary (does not affect the merge users).  This can be used to create a seeded dictionary for a new user, or to copy a single user's dictionary to a new file.  This is great for building global dictionaries, but crunches a lot of time and disk.
 === AGENT COMMANDLINE ARGUMENTS ===

@@ Line 844: / Line 844: @@
 ''Solution:''
 DSPAM's default training mode is TEFT. On top of this, the purging defaults are very lax. You might consider switching to TOE (Train-on-Error) mode training if you require a minimal database. If you are willing to sacrifice accuracy for disk space, disabling the 'chain' tokenizer from dspam.conf will prevent the use of multi-word (chained) tokens, which will also cut your database size considerably. You may also consider more frequent calls to dspam_clean -p to purge neutral data, which comprises a majorrity of most databases.
 For more help, please see the DSPAM FAQ at http://dspam.sourceforge.net.

@@ Line 339: / Line 339: @@
   --with-storage-driver=DRIVER[,DRIVER2[...,DRIVERN]]
-Specify your storage driver selection(s).  A storage driver is a driver written specifically for DSPAM to store tokens, signature data, andperform other proprietary operations.  The default driver is hash_drv. The following drivers have been provided:
+Specify your storage driver selection(s).  A storage driver is a driver written specifically for DSPAM to store tokens, signature data, and perform other proprietary operations.  The default driver is hash_drv. The following drivers have been provided:
   mysql_drv:   MySQL Drivers
@@ Line 372: / Line 372: @@
 <br>
 ===== DRIVER SPECIFIC CONFIGURE SWITCHES =====

@@ Line 1,663: / Line 1,663: @@
 In order to keep DSPAM unencumbered by intellectual property abuses, all external contributors to the project are asked to release any rights to the submission. This keeps the DSPAM project a healthy, unencumbered GPL project. Please accompany your patch, code, or other submission with the following statement. By submitting a patch to the project, you agree to be bound by the terms of this statement whether it is specifically included in the submission or not, however we still require that it be attached to the submission:
-  The author or authors of this submission hereby release any and all copyright interest in this code, documentation, or other materials included to the DSPAM project and its primary governors. We intend this relinquishment of copyright interest in perpetuity of all present and future rights to said submission under copyright law.
+  The author or authors of this submission hereby release any and all
 <br>