RE: How do I know if DCC is running and working?
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
Re: How do I know if DCC is running and working?
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?
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.
RE: How do I know if DCC is running and working?
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?
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
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