DCC -> report failed: Exited with non-zero exit code 67

> From: Sidney Markowitz 

> > 67 is the default `dccproc -x` value or exit code when the counts
> > exceed the local threshold.  Version 1.3.15 assumes that when you
> > say `dccproc -t many`, you're talking and want to hear about spam.

> The following shows two calls to dccproc version 1.3.31, one using -t many and
>one not. The one that does not use -t many does return a "many" result. But the
> exit code is 0.
> Why?

> $ dccproc -t many -H -a 64.4.11.51 < ~/testspam/Good\ Day.eml
> X-DCC-CollegeOfNewCaledonia-Metrics: sidona.sidney.com 1189; bulk Body=many
>         Fuz1=many Fuz2=many
> $ echo $?
> 67

`dccproc -tMANY` in effect also sets `dccproc -cALL,MANY`

> $ dccproc -H -a 64.4.11.51 < ~/testspam/Good\ Day.eml
> X-DCC-CollegeOfNewCaledonia-Metrics: sidona.sidney.com 1189; Body=many
>         Fuz1=many Fuz2=many
> $ echo $?
> 0

Without a "-c type,[log-thold,]rej-thold" setting (or -tMANY),
the default rejection threshold is NEVER.

To force the second test to exit with 67, try

    dccproc -H -a 64.4.11.51 -c ALL,MANY < ~/testspam/Good\ Day.eml


By the way, it would not be good to ship in SpamAssassin a test
that reports spam with -a64.4.11.51.  Sites with the DCC Reputation
code would be falsely reporting that IP address as a source of spam
to the network.

Vernon Schryver    vjs@rhyolite.com