You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Debug Channels

The various SpamAssassin scripts have a debug option (-D) which can optionally take a list of channels which will restrict what information is displayed. People have asked which channels are available. However, the channels are dynamic based on the code that is running. When looking at the debug output, the first word (pre-colon) is the logging level (dbg, info, warn, error,) and the second word (pre-colon) is the channel. ie:

[20784] dbg: message: main message type: text/plain
[20784] dbg: bayes: DB journal sync: last sync: 1148309062
[20784] dbg: check: is spam? score=-0.156 required=5
[20784] dbg: check: tests=BAYES_00,MISSING_SUBJECT,NO_RECEIVED,NO_RELAYS,TO_CC_NONE

has the channels message, bayes, and check. While the channels are dynamic in nature, below is the standard ones that are in use (this is not a complete list).


spamassassin and spamd channels

accessdb
ail
archive-iterator
auto-whitelist
bayes
check
config
dcc
dk
dns
eval
generic
hashcash
ident
ignore
info
ldap
learn
locker
log
logger
markup
message
metadata
netcache
plugin
prefork
pyzor
razor2
received-header
replacetags
reporter
rules
spamd
spf
textcat
uri
uridnsbl
util

generated via:

$ egrep -hr '(info|dbg)\(' spamassassin.raw spamd lib | perl -nle 'next unless /^\s*(?:info|dbg)\(.([^:]+):/; print $1' | sort -u

sa-update channels

channel
diag
dns
generic
gpg
http
sha1

generated via:

egrep -hr '(info|dbg)\(' sa-update.raw | perl -nle 'next unless /^\s*(?:info|dbg)\(.([^:]+):/; print $1' | sort -u
  • No labels