`man spamassasin' has this to say about the -D flag:
-D [area=n,...], --debug [area=n,...]
Produce diagnostic output. The level of diagnostic output can be
set for each area separately; area is the area of the code to
instrument, and n is a positive or negative number indicating the
debug level or bitmask for that area of code. For example, to pro-
duce diagnostic output on all rules that hit, use:
spamassassin -D rulesrun=255
I see nothing in the man pages that indicates what the list of `areas'
might be.
I'd say someone missed a good chance to include that info in above
section.
Grepping on `area' in man spamassassin, man spamd, perldoc
Mail::SpamAssassin, perldoc Mail::SpamAssassin::Conf doesn't turn up
anthing helpfull.
Where can I find these areas listed or described? Or at least how can
I get output on all areas?
I'm also curious why this isn't just a simple numbering system rather
than something stained thru a bitmask. Not complaining just wondered
why it is like it is.
-D [area=n,...], --debug [area=n,...]
Produce diagnostic output. The level of diagnostic output can be
set for each area separately; area is the area of the code to
instrument, and n is a positive or negative number indicating the
debug level or bitmask for that area of code. For example, to pro-
duce diagnostic output on all rules that hit, use:
spamassassin -D rulesrun=255
I see nothing in the man pages that indicates what the list of `areas'
might be.
I'd say someone missed a good chance to include that info in above
section.
Grepping on `area' in man spamassassin, man spamd, perldoc
Mail::SpamAssassin, perldoc Mail::SpamAssassin::Conf doesn't turn up
anthing helpfull.
Where can I find these areas listed or described? Or at least how can
I get output on all areas?
I'm also curious why this isn't just a simple numbering system rather
than something stained thru a bitmask. Not complaining just wondered
why it is like it is.