more troubles with DCC on SA 3.30 : dccifd options? dcc_options sent to wrong place?
was using this on SA 3.2.5 in local.cf dcc_options -R -x 0 dcc_home /usr/local/dcc dcc_dccifd_path /usr/local/dcc/dccifd now, on SA 3.30, I get this (constantly). Feb 1 07:19:14 mx1 dccifd[10069]: unrecognized option value: -R -x 0 note, that dcc_options are options that are supposed to be sent to the dccproc command, NOT dccifd. dcc_options options Specify additional options to the dccproc(8) command. Please note that only characters in the range [0-9A-Za-z ,._/-] are allowed for security reasons. The default is undef. from man dccproc: -R says the first Received lines have the standard helo (name [address])... format and the address is that of the SMTP client that would otherwise be provided with -a. The -a option should be used if the local SMTP server adds a Received line with some other format or does not add a Received line. Received headers specifying IP addresses marked MX or MXDCC in the -w whiteclnt file are skipped. -x exitcode specifies the code or status with which dccproc exits if the -c thresholds are reached or the -w whiteclnt file blacklists the mes- sage. The default value is EX_NOUSER. EX_NOUSER is 67 on many systems. Use 0 to always exit successfully. -- Michael Scheidell, CTO Phone: 561-999-5000, x 1259 *| *SECNAP Network Security Corporation * Certified SNORT Integrator * 2008-9 Hot Company Award Winner, World Executive Alliance * Five-Star Partner Program 2009, VARBusiness * Best Anti-Spam Product 2008, Network Products Guide * King of Spam Filters, SC Magazine 2008 __ This email has been scanned and certified safe by SpammerTrap(r). For Information please see http://www.secnap.com/products/spammertrap/ __
Re: more troubles with DCC on SA 3.30 : dccifd options? dcc_options sent to wrong place?
Michael,
was using this on SA 3.2.5 in local.cf
dcc_options -R -x 0
dcc_home /usr/local/dcc
dcc_dccifd_path /usr/local/dcc/dccifd
now, on SA 3.30, I get this (constantly).
Feb 1 07:19:14 mx1 dccifd[10069]: unrecognized option value: -R -x 0
note, that dcc_options are options that are supposed to be sent to the
dccproc command, NOT dccifd.
Wrong options. Please open a bug report.
I believe this is the fix:
--- lib/Mail/SpamAssassin/Plugin/DCC.pm (revision 905273)
+++ lib/Mail/SpamAssassin/Plugin/DCC.pm (working copy)
@@ -679,7 +679,7 @@
my $left;
my $right;
my $timeout = $conf-{dcc_timeout};
- my $opts = $conf-{dcc_options};
+ my $opts = $conf-{dccifd_options};
my @opts = !defined $opts ? () : split(' ',$opts);
$permsgstatus-enter_helper_run_mode();
@@ -906,7 +906,7 @@
my $conf = $self-{main}-{conf};
my $timeout = $conf-{dcc_timeout};
# instead of header use whatever the report option is
- my $opts = $conf-{dcc_options};
+ my $opts = $conf-{dccifd_options};
my @opts = !defined $opts ? () : split(' ',$opts);
$options-{report}-enter_helper_run_mode();
Mark
Re: more troubles with DCC on SA 3.30 : dccifd options? dcc_options sent to wrong place?
On 2/1/10 8:01 AM, Mark Martinec wrote: Wrong options. Please open a bug report. I believe this is the fix: Thanks, that fixed mine. won't help 'chris's problem, will it? -- Michael Scheidell, CTO Phone: 561-999-5000, x 1259 *| *SECNAP Network Security Corporation * Certified SNORT Integrator * 2008-9 Hot Company Award Winner, World Executive Alliance * Five-Star Partner Program 2009, VARBusiness * Best Anti-Spam Product 2008, Network Products Guide * King of Spam Filters, SC Magazine 2008 __ This email has been scanned and certified safe by SpammerTrap(r). For Information please see http://www.secnap.com/products/spammertrap/ __
Re: more troubles with DCC on SA 3.30 : dccifd options? dcc_options sent to wrong place?
Thanks, that fixed mine. Thanks for testing. Please open the bug report nevertheless, so that the fix is documented and can be properly rolled into 3.3.1. won't help 'chris's problem, will it? No, its is unrelated. Mark
Re: more troubles with DCC on SA 3.30 : dccifd options? dcc_options sent to wrong place?
On 2/1/10 8:16 AM, Mark Martinec wrote: Thanks, that fixed mine. Thanks for testing. Please open the bug report nevertheless, so that the fix is documented and can be properly rolled into 3.3.1. bug opened, patch documented! thanks for help across the big pond! bet the snow capped mountains are unbelievable there this week! chris's: wonder if he is using dccproc or dccifd... -- Michael Scheidell, CTO Phone: 561-999-5000, x 1259 *| *SECNAP Network Security Corporation * Certified SNORT Integrator * 2008-9 Hot Company Award Winner, World Executive Alliance * Five-Star Partner Program 2009, VARBusiness * Best Anti-Spam Product 2008, Network Products Guide * King of Spam Filters, SC Magazine 2008 __ This email has been scanned and certified safe by SpammerTrap(r). For Information please see http://www.secnap.com/products/spammertrap/ __
Re: more troubles with DCC on SA 3.30 : dccifd options? dcc_options sent to wrong place?
On Mon, 2010-02-01 at 08:19 -0500, Michael Scheidell wrote: On 2/1/10 8:16 AM, Mark Martinec wrote: Thanks, that fixed mine. Thanks for testing. Please open the bug report nevertheless, so that the fix is documented and can be properly rolled into 3.3.1. bug opened, patch documented! thanks for help across the big pond! bet the snow capped mountains are unbelievable there this week! chris's: wonder if he is using dccproc or dccifd... Using dccproc, always have been. -- KeyID 0xE372A7DA98E6705C signature.asc Description: This is a digitally signed message part
