Back to Blog
Test spamassassin6/16/2023 ![]() You can alter this setting in Server Admin for Mail in the filtering mechanism settings. Run 'spamassassin -D -lint > test.log 2>&1'. SpamAssassin () typically doesn't re-route any arriving spam by default IIRC, it marks mail as being spammy and passes it through. This can be done by redirecting stdout to a file and then redirecting stderr to the same location. You may also test specific X-Spam-Status headers via the SpamAssassin Status Decoder. Sometimes its necessary to output the SpamAssassin debug information to a file. SpamAssassin Test & Scoring Chart This is the current list of tests SpamAssassin performs on email with SpamAssassin Filtering enabled to determine if they're spam or not.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. Often times debug is the only place to see what exactly is causing your error. 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 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 'spamassassin -D -lint > test.log 2>&1 '. This can be done by redirecting stdout to a file and then redirecting stderr to the same location. Now you can quickly view your DomainKeys, DKIM, and SPF validity, and SpamAssassin score in one place. Run 'spamassassin -lint', especially if you just added anything to your *.cf files or a user_prefs file. Sometimes its necessary to output the SpamAssassin debug information to a file.Here are some simple steps in debugging your SpamAssassin installation:
0 Comments
Read More
Leave a Reply. |