spamassassin -D --lint

[Email Lists <li...@abbacomm.net>]

When running

spamassassin -D --lint > spamconfdebug.txt 2>&1

what obvious things will jump out at someone if there is a problem?

There is quite a bit of output stuff to go through regardless and im
wondering if there are any standard texts we should grep for in the
outputfile

Thanks

 - rh

--
Robert - Abba Communications
   Computer & Internet Services
 (509) 624-7159 - www.abbacomm.net
 

Re: spamassassin -D --lint

[David B Funk <db...@engineering.uiowa.edu>]

On Mon, 9 Oct 2006, Email Lists wrote:

>
> When running
>
> spamassassin -D --lint > spamconfdebug.txt 2>&1
>
> what obvious things will jump out at someone if there is a problem?
>
> There is quite a bit of output stuff to go through regardless and im
> wondering if there are any standard texts we should grep for in the
> outputfile
>
> Thanks

First run:
  spamassassin --lint

That invocation should produce -no- output, any is an error that
needs to be investigated. Look at the '-D --lint' to get more
info about the error.

Whenever I add new rules I run the plain '--lint' to check for
obvious errors, then run:
  spamassassin -D --lint 2>&1 | tail

to look at the final score from the standard test message. If it's
not the same as a run without the new rules, I check into it.
(a new rule may be misfiring and running up the score)


-- 
Dave Funk                                  University of Iowa
<dbfunk (at) engineering.uiowa.edu>        College of Engineering
319/335-5751   FAX: 319/384-0549           1256 Seamans Center
Sys_admin/Postmaster/cell_admin            Iowa City, IA 52242-1527
#include <std_disclaimer.h>
Better is not better, 'standard' is better. B{