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.
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
@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
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
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
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:
