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.000000000 +0100
> +++ DCC.pm 2011-12-22 23:22:11.000000000 +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
