How do I know if DCC is running and working?

[Vernon Webb <ve...@comp-wiz.com>]

Subject says it all. How can I tell if DDC is running and working on my system?

Thanks

RE: How do I know if DCC is running and working?

[Vernon Webb <ve...@comp-wiz.com>]

I have nothing in either, so obviously something is not working. I thought after I 
installed it all I had to do was uncomment the line that says "loadplugin 
Mail::SpamAssassin::Plugin::DCC" in the "/etc/mail/spamassassin/v310.pre" file. Am I 
missing something? 

> grep DCC /var/log/maillog 
>   
> Or   
>   
> tcpdump port 6277 

RE: How do I know if DCC is running and working?

[Sietse van Zanen <si...@wizdom.nu>]

grep DCC /var/log/maillog

Or 

tcpdump port 6277

-Sietse



From: Vernon Webb
Sent: Thu 07-Dec-06 23:55
To: SpamAssassin
Subject: How do I know if DCC is running and working?


Subject says it all. How can I tell if DDC is running and working on my system?

Thanks

Re: How do I know if DCC is running and working?

[LuKreme <kr...@kreme.com>]

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

-- 
It's better to burn out than it is to rust
   -- Neil Young as quoted by Kurt Cobain

Re: How do I know if DCC is running and working?

[Robert S <ro...@gmail.com>]

Try

$ spamassassin --debug --lint

(or $ spamassassin --debug --lint 2>&1 | less )
and look in the output for DCC.  The DCC daemon doesn't have to be
running for DCC to work.

I've found that if the DCC daemon is running I get timeout errors at
times and nobody's been able to show me how to get rid of them.