LuKreme wrote:
> On 8-Dec-2006, at 13:35, Robert S wrote:
> > spamassassin --debug --lint 2>&1 | less
>
> I went with
>
> # spamassassin -D --lint 2>&1| grep -i dcc
> [85448] dbg: config: read file /usr/local/share/spamassassin/25_dcc.cf
> [85448] dbg: plugin: registered
> Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x8f63dcc)
> [85448] dbg: plugin: loading Mail::SpamAssassin::Plugin::DCC from @INC
> [85448] dbg: dcc: local tests only, disabling DCC
> [85448] dbg: plugin: registered Mail::SpamAssassin::Plugin::DCC=HASH
> (0x90d3b38)
> [85448] dbg: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH
> (0x8f63dcc) implements 'parsed_metadata'
> [85448] dbg: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH
> (0x8f63dcc) implements 'check_tick'
> [85448] dbg: plugin: Mail::SpamAssassin::Plugin::URIDNSBL=HASH
> (0x8f63dcc) implements 'check_post_dnsbl'
>
> no hits on DCC in maillog
'spamassassin --lint' will not run network tests (including DCC). To test
the network test, you need to feed SA a test message. Run one of your
emails back through SA in debug mode to see the DCC info:
spamassassin -D dcc < testmessage.txt
--
Bowie
