Date: 2004-10-27T10:14:42
Editor: DavidForrest <drf5n+spamassassin@freeshell.org>
Wiki: SpamAssassin Wiki
Page: HowToDebug
URL: http://wiki.apache.org/spamassassin/HowToDebug
no comment
Change Log:
------------------------------------------------------------------------------
@@ -3,3 +3,5 @@
* 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.
+----
+CategoryFaq
Editor: DavidForrest <drf5n+spamassassin@freeshell.org>
Wiki: SpamAssassin Wiki
Page: HowToDebug
URL: http://wiki.apache.org/spamassassin/HowToDebug
no comment
Change Log:
------------------------------------------------------------------------------
@@ -3,3 +3,5 @@
* 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.
+----
+CategoryFaq