You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@spamassassin.apache.org by co...@spamassassin.apache.org on 2004/09/28 21:18:12 UTC

[SpamAssassin Wiki] New: HowToDebug

   Date: 2004-09-28T12:18:12
   Editor: MichaelParker <pa...@pobox.com>
   Wiki: SpamAssassin Wiki
   Page: HowToDebug
   URL: http://wiki.apache.org/spamassassin/HowToDebug

   no comment

New Page:

Here are some simple steps in debugging your SpamAssassin installation:

 * Run ''''spamassassin --lint'''', especially if you just added anything to your *.cf files or a user_prefs file.  Often times you might have something slightly wrong and either a) SpamAssassin stops parsing the file or b) it's just plain wrong and causing the error.

 * Run with ''''-D''''.  The debug output from spamassassin, sa-learn, spamd is sometimes very verbose, but it also gives you a large amount of data that can be very helpful.  Often times debug is the only place to see what exactly is causing your error.  When running ''spamd'' with ''-D'' you will see some initial startup activity, you can ignore this, it is just scanning a test message to help do the initial load of the perl modules.