Differences between revisions 3 and 4
Revision 3 as of 2006-10-31 19:56:32
Size: 1045
Editor: ChrisPrice
Revision 4 as of 2009-09-20 23:17:21
Size: 1045
Editor: localhost
Comment: converted to 1.6 markup
No differences found!

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.

  • Sometimes its necessary to output the SpamAssassin debug information to a file. This can be done by redirecting stdout to a file and then redirecting stderr to the same location. Run 'spamassassin -D --lint > test.log 2>&1'.


HowToDebug (last edited 2009-09-20 23:17:21 by localhost)