Re: dccifd error
On Mar 4, 2012, at 21:34, xTrade Assessory xtr...@matik.com.br wrote: you can disable the plugin or setup use_dcc 0 in local.cf The plugin *was* disabled in v310, but the errors still showed up in the maillog, which is what started this. As far as I can see, dcc was never running though there was a very old install of it in /var/dcc.
Re: dccifd error
LuKreme wrote: On Mar 4, 2012, at 21:34, xTrade Assessory xtr...@matik.com.br wrote: you can disable the plugin or setup use_dcc 0 in local.cf The plugin *was* disabled in v310, but the errors still showed up in the maillog, which is what started this. As far as I can see, dcc was never running though there was a very old install of it in /var/dcc. use_dcc loadplugin are two different settings use_dcc 0 make sense if the plugin is loaded from somewhere loadplugin ...::DCC you can find in one or more of your *.pre files if the plugin is not loaded you should not get any err msg so you might have loaded it from some other .pre file if it is not loaded you probable should then comment use_dcc Hans -- XTrade Assessory International Facilitator BR - US - CA - DE - GB - RU - UK +55 (11) 4249. http://xtrade.matik.com.br
Re: dccifd error
Am Sonntag, 4. März 2012, 12:44:40 schrieb LuKreme: I’ve noticed the following error in my mailogs: mail spamd[26839]: dcc: failed to connect to local socket /var/dcc/dccifd spamassassins DCC plugin will use dccproc if dccifd is not available. If dccproc is run more than 500 times in fewer than 500 seconds, dccproc tries to start dccifd. (dccproc(8)) An example init script (e.g. /var/lib/dcc/libexec/rcDCC) explains how to start dccifd with init. Look for the rule DCC_CHECK in your spamd logs to see if DCC is working or not. RTFM: cdcc(8), dcc(8), dccm(8), dccifd(8) [ ... ] regards Stefan
Re: dccifd error
LuKreme wrote: On 04 Mar 2012, at 04:44 , LuKreme wrote: mail spamd[26839]: dcc: failed to connect to local socket /var/dcc/dccifd OK, I found http://wiki.apache.org/spamassassin/InstallingDCC after doing some other googling, got DCC installed (I wiped the existing /var/dcc directory contents), restarted spamd and postfix, and still getting the same error. If I check /var/lib/dcc (I build with the FHS options) the dccifd file does not exist. # cdcc info | grep anon dcc1.dcc-servers.net,- RTT+1000 ms anon dcc2.dcc-servers.net,- RTT+1000 ms anon dcc3.dcc-servers.net,- RTT+1000 ms anon dcc4.dcc-servers.net,- RTT+1000 ms anon dcc5.dcc-servers.net,- RTT+1000 ms anon not sure but probably the dccifd is the remote daemon and since DCC is a commerial service you might not have a account there, so you cannot connect ... ? Hans -- XTrade Assessory International Facilitator BR - US - CA - DE - GB - RU - UK +55 (11) 4249. http://xtrade.matik.com.br
Re: dccifd error
On 04 Mar 2012, at 05:38 , xTrade Assessory wrote: not sure but probably the dccifd is the remote daemon and since DCC is a commerial service you might not have a account there, so you cannot connect ... ? http://www.rhyolite.com/dcc/ The non-commercial DCC software is distributed under a license that is free only to organizations that do not sell filtering devices or services except to their own users and that participate in the global DCC network. ISPs that use DCC to filter mail for their own users are intended to be covered by the free license. “ But here’s the thing, if dcc is not enabled by spamassassin, I get a spamd error for every message. -- BILL: I can't get behind the Gods, who are more vengeful, angry, an dangerous if you don't believe in them! HENRY: Why can't all these God just get along? I mean, they're omni- potent and omnipresent, what's the problem?
Re: dccifd error
LuKreme wrote: On 04 Mar 2012, at 05:38 , xTrade Assessory wrote: not sure but probably the dccifd is the remote daemon and since DCC is a commerial service you might not have a account there, so you cannot connect ... ? http://www.rhyolite.com/dcc/ The non-commercial DCC software is distributed under a license that is free only to organizations that do not sell filtering devices or services except to their own users and that participate in the global DCC network. ISPs that use DCC to filter mail for their own users are intended to be covered by the free license. “ But here’s the thing, if dcc is not enabled by spamassassin, I get a spamd error for every message. you can disable the plugin or setup use_dcc 0 in local.cf otherwise you should check if you have the dcc package on your machine, configured and running Hans -- XTrade Assessory International Facilitator BR - US - CA - DE - GB - RU - UK +55 (11) 4249. http://xtrade.matik.com.br
Re: dccproc/dccifd error
On 12/22/11 9:44 PM, dar...@chaosreigns.com wrote: On 12/22, dar...@chaosreigns.com wrote: The author did say I believe it is entirely upward compatible. in November, which was well after the DCC 1.3.140 release, so it probably works. I'd be interested to hear how that works if you try it. Might be worth posting the results to that bug. found the issue, twofold. #1, the upstream email provider is adding X-DCC-Metrics headers (but they are disconnected from global DCC network) #2, bug.. yep, bug. Vernon (author of DCC) will investigate and fix it, and update the SA BUGzilla soon. (so, yes, this would be a bug in 3.4 if released, but only shows up under one certain condition) -- Michael Scheidell, CTO o: 561-999-5000 d: 561-948-2259 *| *SECNAP Network Security Corporation * Best Mobile Solutions Product of 2011 * Best Intrusion Prevention Product * Hot Company Finalist 2011 * Best Email Security Product * Certified SNORT Integrator __ This email has been scanned and certified safe by SpammerTrap(r). For Information please see http://www.spammertrap.com/ __
Re: dccproc/dccifd error
On 12/23, Michael Scheidell wrote: #2, bug.. yep, bug. Vernon (author of DCC) will investigate and fix it, and update the SA BUGzilla soon. (so, yes, this would be a bug in 3.4 if released, but only shows up under one certain condition) Please post the bug to https://issues.apache.org/SpamAssassin/ so we can keep track of it, and make sure 3.4.0 doesn't get released with it. -- Life is either a daring adventure or it is nothing at all. - Helen Keller http://www.ChaosReigns.com
Re: dccproc/dccifd error
I am going to update the original bug with patch. Ill have mark look at it first. -- Michael Scheidell, CTO SECNAP Network Security -Original message- From: dar...@chaosreigns.com dar...@chaosreigns.com To: Michael Scheidell michael.scheid...@secnap.com Cc: users@spamassassin.apache.org users@spamassassin.apache.org Sent: Fri, Dec 23, 2011 17:28:28 GMT+00:00 Subject: Re: dccproc/dccifd error On 12/23, Michael Scheidell wrote: #2, bug.. yep, bug. Vernon (author of DCC) will investigate and fix it, and update the SA BUGzilla soon. (so, yes, this would be a bug in 3.4 if released, but only shows up under one certain condition) Please post the bug to https://issues.apache.org/SpamAssassin/ so we can keep track of it, and make sure 3.4.0 doesn't get released with it. -- Life is either a daring adventure or it is nothing at all. - Helen Keller http://www.ChaosReigns.com
dccproc/dccifd error
Hi,
I am using perl-5.10.1, amavisd-new 2.7.0, Mail-SpamAssassin-3.3.2 and
dcc-dccd-1.3.140.
When I receive and scan a message with a 'X-DCC-xxx-Metrics'-header the
following error is logged to maillog:
Dec 23 01:04:53 mx dccproc[81847]: unrecognized many usage: [-VdAQCHER] [-h
homedir] [-m map] [-w whiteclnt] [-T tmpdir][-a IP-address] [-f env_from]
[-t targets] [-x exitcode][-c type,[log-thold,][spam-thold]] [-g
[not-]type] [-S header][-i infile] [-o outfile] [-l logdir] [-B
dnsbl-option][-L ltype,facility.level] ; fatal error
After modifying DCC.pm the error is gone:
--- DCC.pm.bak 2011-12-22 23:03:34.0 +0100
+++ DCC.pm 2011-12-22 23:22:11.0 +0100
@@ -859,7 +859,7 @@
}
if ($tag eq dcc:) {
# query instead of report if there is an X-DCC header from upstream
- unshift(@opts, '-Q', 'many') if defined $permsgstatus-{dcc_raw_x_dcc};
+ unshift(@opts, '-Q') if defined $permsgstatus-{dcc_raw_x_dcc};
} else {
# learn or report spam
unshift(@opts, '-t', 'many');
Is this the correct fix? Or is my setup broken?
Thanks.
--
Herbert
Re: dccproc/dccifd error
A new DCC.pm from the author of DCC was added to trunk on November 14th:
https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6698
Looks like it already handles your case:
DCC.pm:863: unshift(@opts, '-Q', 'many') if defined
$permsgstatus-{dcc_raw_x_dcc};
That will be included in the next spamassassin re release, v3.4.0 (which
doesn't have a specific planned release date).
On 12/23, Herbert J. Skuhra wrote:
Hi,
I am using perl-5.10.1, amavisd-new 2.7.0, Mail-SpamAssassin-3.3.2 and
dcc-dccd-1.3.140.
When I receive and scan a message with a 'X-DCC-xxx-Metrics'-header the
following error is logged to maillog:
Dec 23 01:04:53 mx dccproc[81847]: unrecognized many usage: [-VdAQCHER]
[-h homedir] [-m map] [-w whiteclnt] [-T tmpdir][-a IP-address] [-f
env_from] [-t targets] [-x exitcode][-c type,[log-thold,][spam-thold]]
[-g [not-]type] [-S header][-i infile] [-o outfile] [-l logdir] [-B
dnsbl-option][-L ltype,facility.level] ; fatal error
After modifying DCC.pm the error is gone:
--- DCC.pm.bak 2011-12-22 23:03:34.0 +0100
+++ DCC.pm 2011-12-22 23:22:11.0 +0100
@@ -859,7 +859,7 @@
}
if ($tag eq dcc:) {
# query instead of report if there is an X-DCC header from upstream
- unshift(@opts, '-Q', 'many') if defined
$permsgstatus-{dcc_raw_x_dcc};
+ unshift(@opts, '-Q') if defined $permsgstatus-{dcc_raw_x_dcc};
} else {
# learn or report spam
unshift(@opts, '-t', 'many');
Is this the correct fix? Or is my setup broken?
Thanks.
--
Herbert
--
Let's just say that if complete and utter chaos was lightning, then
he'd be the sort to stand on a hilltop in a thunderstorm wearing wet
copper armour and shouting 'All gods are bastards'. - The Color of Magic
http://www.ChaosReigns.com
Re: dccproc/dccifd error
On 12/22, dar...@chaosreigns.com wrote:
DCC.pm:863: unshift(@opts, '-Q', 'many') if defined
$permsgstatus-{dcc_raw_x_dcc};
I am using perl-5.10.1, amavisd-new 2.7.0, Mail-SpamAssassin-3.3.2 and
dcc-dccd-1.3.140.
Dec 23 01:04:53 mx dccproc[81847]: unrecognized many usage: [-VdAQCHER]
[-h homedir] [-m map] [-w whiteclnt] [-T tmpdir][-a IP-address] [-f
env_from] [-t targets] [-x exitcode][-c type,[log-thold,][spam-thold]]
[-g [not-]type] [-S header][-i infile] [-o outfile] [-l logdir] [-B
dnsbl-option][-L ltype,facility.level] ; fatal error
- unshift(@opts, '-Q', 'many') if defined
$permsgstatus-{dcc_raw_x_dcc};
+ unshift(@opts, '-Q') if defined $permsgstatus-{dcc_raw_x_dcc};
Yeah, I read that backwards.
Maybe it's handled by this?
./lib/Mail/SpamAssassin/Plugin/DCC.pm:692: $x_dcc =~ s/many/99/ig;
-
http://svn.apache.org/viewvc/spamassassin/trunk/lib/Mail/SpamAssassin/Plugin/DCC.pm?view=markup
Info on trunk: http://wiki.apache.org/spamassassin/DownloadFromSvn
The author did say I believe it is entirely upward compatible. in
November, which was well after the DCC 1.3.140 release, so it probably
works.
I'd be interested to hear how that works if you try it. Might be worth
posting the results to that bug.
--
Whom God wishes to destroy, he first makes mad.
- Euripides (c.480 - 406 BC).
http://www.ChaosReigns.com
