Re: warn: reporter: DCC report via dccproc failed
Chris, > > I can see now: > > failed: Can't locate object method "close_pipe_fh" via package > > "Mail::SpamAssassin::Reporter" at /etc/mail/spamassassin/DCC.pm > > You are running an old version of the DCC.pm plugin with a new version > > of SpamAssassin. Remove your old copy from /etc/mail/spamassassin/ . > > Mark > > Thanks Mark, I removed it now, the only DCC.pm is in > /usr/lib/perl5/site_perl/5.10.1/Mail/SpamAssassin/Plugin > > Had to change my v310.pre to reflect this and looks like it's working > now. Thanks for the advice. Thanks, I'm glad my suspicion was right. > No need for a bug report now is there? No need. Worth remembering though... Mark
Re: warn: reporter: DCC report via dccproc failed
On Wed, 2010-02-03 at 17:06 +0100, Mark Martinec wrote: > Chris, > > > > > spamd[30068]: util: failed to spawn a process > > > > "/usr/local/bin/dccproc, -H, -x, 0, -a, 204.15.81.110": > > > > Insecure dependency in exec while running setgid > > > > at /usr/lib/perl5/site_perl/5.10.1/Mail/SpamAssassin/Util.pm line 1533. > > > > at /usr/lib/perl5/site_perl/5.10.1/Mail/SpamAssassin/Util.pm line 1438. > > > Mark, running spamassassin -D -r (spam) nets: > > [...] > > Feb 1 19:24:11.500 [16499] warn: reporter: DCC report via dccproc > > failed: Can't locate object method "close_pipe_fh" via package > > "Mail::SpamAssassin::Reporter" at /etc/mail/spamassassin/DCC.pm > > line 803 > > I can see now: > > failed: Can't locate object method "close_pipe_fh" via package > "Mail::SpamAssassin::Reporter" at /etc/mail/spamassassin/DCC.pm > > You are running an old version of the DCC.pm plugin with a new version > of SpamAssassin. Remove your old copy from /etc/mail/spamassassin/ . > > Mark Thanks Mark, I removed it now the only DCC.pm is in /usr/lib/perl5/site_perl/5.10.1/Mail/SpamAssassin/Plugin Had to change my v310.pre to reflect this and looks like it's working now. Thanks for the advice. No need for a bug report now is there? Chris -- KeyID 0xE372A7DA98E6705C signature.asc Description: This is a digitally signed message part
Re: warn: reporter: DCC report via dccproc failed
Chris, > > > spamd[30068]: util: failed to spawn a process > > > "/usr/local/bin/dccproc, -H, -x, 0, -a, 204.15.81.110": > > > Insecure dependency in exec while running setgid > > > at /usr/lib/perl5/site_perl/5.10.1/Mail/SpamAssassin/Util.pm line 1533. > > > at /usr/lib/perl5/site_perl/5.10.1/Mail/SpamAssassin/Util.pm line 1438. > Mark, running spamassassin -D -r (spam) nets: > [...] > Feb 1 19:24:11.500 [16499] warn: reporter: DCC report via dccproc > failed: Can't locate object method "close_pipe_fh" via package > "Mail::SpamAssassin::Reporter" at /etc/mail/spamassassin/DCC.pm > line 803 I can see now: failed: Can't locate object method "close_pipe_fh" via package "Mail::SpamAssassin::Reporter" at /etc/mail/spamassassin/DCC.pm You are running an old version of the DCC.pm plugin with a new version of SpamAssassin. Remove your old copy from /etc/mail/spamassassin/ . Mark
Re: warn: reporter: DCC report via dccproc failed
> > > > you did a spamassassin -r? > > > > On 01.02.10 06:07, Chris wrote: > > > In a way yes, I run a perl script that runs sa-learn and also reports > > > the spam to razor/pyzor/DCC all in one run. > On Mon, 2010-02-01 at 17:49 +0100, Matus UHLAR - fantomas wrote: > > now, how does this differ from running spamassassin -r? On 01.02.10 19:36, Chris wrote: > Not much except sa-learn for ham/spam and reporting to razor/pyzor/DCC > and SC are all in one script. Just makes it easier for me to run > "reporter.pl". this is afaik the same what "spamassassin -r" does :-) > The script also moves all spam after it's processed to another folder > where I can run another script which reports all spam to their various > abuse addresses. aha, now that't THE difference. -- Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/ Warning: I wish NOT to receive e-mail advertising to this address. Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu. 99 percent of lawyers give the rest a bad name.
Re: warn: reporter: DCC report via dccproc failed
On Mon, 2010-02-01 at 17:49 +0100, Matus UHLAR - fantomas wrote: > > > On 1/31/10 9:03 PM, Chris wrote: > > > > SA 3.3.0, just installed via CPAN this afternoon. When running my spam > > > > reporter script I noticed this: > > > > > > > > warn: reporter: DCC report via dccproc failed: Can't locate object > > > > method "close_pipe_fh" via package "Mail::SpamAssassin::Reporter" > > > > at /etc/mail/spamassassin/DCC.pm line 803, line 2. > > > > Jan 31 18:01:05.755 [17665] info: reporter: could not report spam to DCC > > > > via dccproc > > > > you did a spamassassin -r? > > On 01.02.10 06:07, Chris wrote: > > In a way yes, I run a perl script that runs sa-learn and also reports > > the spam to razor/pyzor/DCC all in one run. > > now, how does this differ from running spamassassin -r? > Not much except sa-learn for ham/spam and reporting to razor/pyzor/DCC and SC are all in one script. Just makes it easier for me to run "reporter.pl". The script also moves all spam after it's processed to another folder where I can run another script which reports all spam to their various abuse addresses. -- KeyID 0xE372A7DA98E6705C signature.asc Description: This is a digitally signed message part
Re: warn: reporter: DCC report via dccproc failed
On Mon, 2010-02-01 at 14:14 +0100, Mark Martinec wrote: > Chris, > > > SA 3.3.0, just installed via CPAN this afternoon. When running my spam > > reporter script I noticed this: > > > > warn: reporter: DCC report via dccproc failed: Can't locate object > > method "close_pipe_fh" via package "Mail::SpamAssassin::Reporter" > > at /etc/mail/spamassassin/DCC.pm line 803, line 2. > > Jan 31 18:01:05.755 [17665] info: reporter: could not report spam to > > DCC via dccproc > > > > spamd[18248]: rules: failed to run DCC_REPUT_13_19 test, skipping: > > spamd[30068]: util: failed to spawn a process > > "/usr/local/bin/dccproc, -H, -x, 0, -a, 204.15.81.110": > > Insecure dependency in exec while running setgid > > at /usr/lib/perl5/site_perl/5.10.1/Mail/SpamAssassin/Util.pm line 1533. > > at /usr/lib/perl5/site_perl/5.10.1/Mail/SpamAssassin/Util.pm line 1438. > > > > > you did a spamassassin -r? > > > > In a way yes, I run a perl script that runs sa-learn and also reports > > the spam to razor/pyzor/DCC all in one run. > > Can you reproduce the problem with a plain 'spamassassin -r' > (possibly setgui'd, like yours)? I wasn't successful. I guess you > will have to show your (stripped down) code that calls DCC reporting > so that the problem is reproducible. Please open a bug report > if you won't be able to locate the problem. One of the > arguments/options or a command path itself was tainted. > > Mark Mark, running spamassassin -D -r (spam) nets: Feb 1 19:24:11.481 [16499] dbg: dcc: dccifd is not available: no r/w dccifd socket found Feb 1 19:24:11.482 [16499] dbg: util: current PATH is: /bin:/usr/bin:/usr/local/bin:/usr/games:/usr/lib/qt4/bin:/home/chris/bin Feb 1 19:24:11.482 [16499] dbg: util: executable for dccproc was found at /usr/local/bin/dccproc Feb 1 19:24:11.482 [16499] dbg: dcc: dccproc is available: /usr/local/bin/dccproc Feb 1 19:24:11.483 [16499] dbg: info: entering helper-app run mode Feb 1 19:24:11.484 [16499] dbg: report: opening pipe: /usr/local/bin/dccproc -H -t many -x 0 -a 82.102.24.225 < /tmp/.spamassassin16499o8XfN7tmp Feb 1 19:24:11.486 [16536] dbg: util: setuid: ruid=500 euid=500 Feb 1 19:24:11.490 [16499] dbg: info: leaving helper-app run mode Feb 1 19:24:11.500 [16499] warn: reporter: DCC report via dccproc failed: Can't locate object method "close_pipe_fh" via package "Mail::SpamAssassin::Reporter" at /etc/mail/spamassassin/DCC.pm line 803, line 2. Feb 1 19:24:11.500 [16499] info: reporter: could not report spam to DCC via dccproc The reporting part of the script is posted here: http://pastebin.com/m18e4e140 -- KeyID 0xE372A7DA98E6705C signature.asc Description: This is a digitally signed message part
Re: warn: reporter: DCC report via dccproc failed
On Mon, 2010-02-01 at 07:13 -0500, Michael Scheidell wrote: > On 2/1/10 7:07 AM, Chris wrote: > > > > I have the standard (free) version of DCC. There were no issues when I > > ran the script a few days previously with 3.2.5. > > > > > > > cdcc -V exit > > what do you get? > > at least > 1.3.111? > cdcc -V exit 1.3.116 -- KeyID 0xE372A7DA98E6705C signature.asc Description: This is a digitally signed message part
Re: warn: reporter: DCC report via dccproc failed
> > On 1/31/10 9:03 PM, Chris wrote: > > > SA 3.3.0, just installed via CPAN this afternoon. When running my spam > > > reporter script I noticed this: > > > > > > warn: reporter: DCC report via dccproc failed: Can't locate object > > > method "close_pipe_fh" via package "Mail::SpamAssassin::Reporter" > > > at /etc/mail/spamassassin/DCC.pm line 803, line 2. > > > Jan 31 18:01:05.755 [17665] info: reporter: could not report spam to DCC > > > via dccproc > > you did a spamassassin -r? On 01.02.10 06:07, Chris wrote: > In a way yes, I run a perl script that runs sa-learn and also reports > the spam to razor/pyzor/DCC all in one run. now, how does this differ from running spamassassin -r? -- Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/ Warning: I wish NOT to receive e-mail advertising to this address. Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu. Save the whales. Collect the whole set.
Re: warn: reporter: DCC report via dccproc failed
Chris, > SA 3.3.0, just installed via CPAN this afternoon. When running my spam > reporter script I noticed this: > > warn: reporter: DCC report via dccproc failed: Can't locate object > method "close_pipe_fh" via package "Mail::SpamAssassin::Reporter" > at /etc/mail/spamassassin/DCC.pm line 803, line 2. > Jan 31 18:01:05.755 [17665] info: reporter: could not report spam to > DCC via dccproc > > spamd[18248]: rules: failed to run DCC_REPUT_13_19 test, skipping: > spamd[30068]: util: failed to spawn a process > "/usr/local/bin/dccproc, -H, -x, 0, -a, 204.15.81.110": > Insecure dependency in exec while running setgid > at /usr/lib/perl5/site_perl/5.10.1/Mail/SpamAssassin/Util.pm line 1533. > at /usr/lib/perl5/site_perl/5.10.1/Mail/SpamAssassin/Util.pm line 1438. > > > you did a spamassassin -r? > > In a way yes, I run a perl script that runs sa-learn and also reports > the spam to razor/pyzor/DCC all in one run. Can you reproduce the problem with a plain 'spamassassin -r' (possibly setgui'd, like yours)? I wasn't successful. I guess you will have to show your (stripped down) code that calls DCC reporting so that the problem is reproducible. Please open a bug report if you won't be able to locate the problem. One of the arguments/options or a command path itself was tainted. Mark
Re: warn: reporter: DCC report via dccproc failed
On 2/1/10 7:07 AM, Chris wrote: I have the standard (free) version of DCC. There were no issues when I ran the script a few days previously with 3.2.5. cdcc -V exit what do you get? at least 1.3.111? -- 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: warn: reporter: DCC report via dccproc failed
On Mon, 2010-02-01 at 06:38 -0500, Michael Scheidell wrote: > On 1/31/10 9:03 PM, Chris wrote: > > SA 3.3.0, just installed via CPAN this afternoon. When running my spam > > reporter script I noticed this: > > > > warn: reporter: DCC report via dccproc failed: Can't locate object > > method "close_pipe_fh" via package "Mail::SpamAssassin::Reporter" > > at /etc/mail/spamassassin/DCC.pm line 803, line 2. > > Jan 31 18:01:05.755 [17665] info: reporter: could not report spam to DCC > > via dccproc > > > > > you did a spamassassin -r? In a way yes, I run a perl script that runs sa-learn and also reports the spam to razor/pyzor/DCC all in one run. > > you have a new(ish) version of DCC? the standard version? or the > commercial version? > I have the standard (free) version of DCC. There were no issues when I ran the script a few days previously with 3.2.5. -- KeyID 0xE372A7DA98E6705C signature.asc Description: This is a digitally signed message part
Re: warn: reporter: DCC report via dccproc failed
On 1/31/10 9:03 PM, Chris wrote: SA 3.3.0, just installed via CPAN this afternoon. When running my spam reporter script I noticed this: warn: reporter: DCC report via dccproc failed: Can't locate object method "close_pipe_fh" via package "Mail::SpamAssassin::Reporter" at /etc/mail/spamassassin/DCC.pm line 803, line 2. Jan 31 18:01:05.755 [17665] info: reporter: could not report spam to DCC via dccproc you did a spamassassin -r? you have a new(ish) version of DCC? the standard version? or the commercial version? -- 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: warn: reporter: DCC report via dccproc failed
On Sun, 2010-01-31 at 20:03 -0600, Chris wrote: > SA 3.3.0, just installed via CPAN this afternoon. When running my spam > reporter script I noticed this: > > warn: reporter: DCC report via dccproc failed: Can't locate object > method "close_pipe_fh" via package "Mail::SpamAssassin::Reporter" > at /etc/mail/spamassassin/DCC.pm line 803, line 2. > Jan 31 18:01:05.755 [17665] info: reporter: could not report spam to DCC > via dccproc > > Ideas anyone? > > Chris > More information I see in my latest syslog cut: Jan 31 20:21:39 localhost spamd[18248]: rules: failed to run DCC_REPUT_13_19 test, skipping: Jan 31 20:21:39 localhost spamd[30068]: util: failed to spawn a process "/usr/local/bin/dccproc, -H, -x, 0, -a, 204.15.81.110": Insecure dependency in exec while running setgid at /usr/lib/perl5/site_perl/5.10.1/Mail/SpamAssassin/Util.pm line 1533. at /usr/lib/perl5/site_perl/5.10.1/Mail/SpamAssassin/Util.pm line 1438. Jan 31 20:21:39 localhost spamd[18248]: dcc: check failed: failed to read header Jan 31 20:21:39 localhost spamd[18248]: rules: failed to run DCC_REPUT_70_89 test, skipping: Jan 31 20:21:40 localhost spamd[18248]: rules: failed to run DCC_REPUT_99_100 test, skipping: Jan 31 20:21:41 localhost spamd[18248]: rules: failed to run DCC_REPUT_90_94 test, skipping: Jan 31 20:21:41 localhost spamd[18248]: rules: failed to run DCC_REPUT_00_12 test, skipping: Jan 31 20:21:41 localhost spamd[18248]: rules: failed to run DCC_REPUT_95_98 test, skipping: Jan 31 20:22:07 localhost spamd[18251]: rules: failed to run DCC_REPUT_13_19 test, skipping: Jan 31 20:22:07 localhost spamd[30195]: util: failed to spawn a process "/usr/local/bin/dccproc, -H, -x, 0, -a, 204.15.81.110": Insecure dependency in exec while running setgid at /usr/lib/perl5/site_perl/5.10.1/Mail/SpamAssassin/Util.pm line 1533. at /usr/lib/perl5/site_perl/5.10.1/Mail/SpamAssassin/Util.pm line 1438. -- KeyID 0xE372A7DA98E6705C signature.asc Description: This is a digitally signed message part
warn: reporter: DCC report via dccproc failed
SA 3.3.0, just installed via CPAN this afternoon. When running my spam reporter script I noticed this: warn: reporter: DCC report via dccproc failed: Can't locate object method "close_pipe_fh" via package "Mail::SpamAssassin::Reporter" at /etc/mail/spamassassin/DCC.pm line 803, line 2. Jan 31 18:01:05.755 [17665] info: reporter: could not report spam to DCC via dccproc Ideas anyone? Chris -- KeyID 0xE372A7DA98E6705C signature.asc Description: This is a digitally signed message part