http://issues.apache.org/SpamAssassin/show_bug.cgi?id=4861
------- Additional Comments From [EMAIL PROTECTED] 2006-04-16 10:55 -------
Looking at dcc_report, I see that it calls
$options->{report}->close_pipe_fh(\*DCC);
That function dies if there is a non-zero exit code. But dccproc exits with code
67 for spammy messages, a change with dccproc version 1.3.15 (see
http://www.rhyolite.com/pipermail/dcc/2005/002773.html )
I notice that dccproc_lookup does not call close_pipe_fh, instead closing the
file handle, with a debug log message if there is a non-zero exit code.
Does anyone know a good reason to call close_pipe_fh? dccproc takes a -x 0
option which would return it to the old behavior of exit code 0 when reporting
spam. Should I just use that and leave in the call to close_pipe_fh?
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
