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

> From: <dcc@mikecappella.com>
 
> > Since installing dcc-dccd-1.3.15, I'm seeing the error:
> >
> >   DCC -> report failed: Exited with non-zero exit code 67

> I modified my Reporter.pm spamassassin module to pass -x 0, and this solves
> the problem.
> 
> Perhaps it would be best to restore the pre 1.3.15 return value.

I've and convinced myself that the old behavior was broken.  Something
like
     dccproc -t 3 -c cmn,10 -i file
should yield the default -x exit code if the DCC server already has a
count of 7 for the message.  So should
     dccproc -t 1 -c cmn,many -i file
or the equivalent
     dccproc -i file
if the DCC server has a value of 16777199 or 1 less than the internal
value that is "many."

It would be wrong for 
    dccproc -t many -i file
to do something else

It would clearly be better to change SpamAssassin with something like
the enclose patch for version 3.0.4 to specify the exit code it wants.
That as far as I can tell the exit code of 67 does no worse than cause
annoying noise supports that notion.

When is the SpamAssassin function report() called?  Is it invoked for
ordinary mail that exceeds a threshold or is it only for spam traps?


Vernon Schryver    vjs@rhyolite.com



*** lib/Mail/SpamAssassin/Reporter.pm   Fri Mar 18 17:06:27 2005
--- lib/Mail/SpamAssassin/Reporter.pm-new       Sat Aug 27 18:10:26 2005
***************
*** 299,305 ****
      }
  
      my $pid = Mail::SpamAssassin::Util::helper_app_pipe_open(*DCC,
!                     $tmpf, 1, $path, "-t", "many", split(' ', $opts));
      $pid or die "$!\n";
      my @ignored = <DCC>;
      $self->close_pipe_fh (\*DCC);
--- 299,305 ----
      }
  
      my $pid = Mail::SpamAssassin::Util::helper_app_pipe_open(*DCC,
!                     $tmpf, 1, $path, "-tmany", "-x0", split(' ', $opts));
      $pid or die "$!\n";
      my @ignored = <DCC>;
      $self->close_pipe_fh (\*DCC);