You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by Gene Heskett <ge...@verizon.net> on 2007/07/27 10:29:51 UTC
upgraded to 3.2.2, now have errors
Greetings;
From /var/log/maillog:
Jul 27 04:26:53 coyote spamd[10637]: spamd: processing message
<11...@thor.sulgenrain.local> for gene:500
Jul 27 04:26:53 coyote spamd[10637]: rules: failed to run CG_FUJI_JPG test,
skipping:
Jul 27 04:26:53 coyote spamd[10637]: (Can't locate object
method "image_name_regex" via package "Mail::SpamAssassin::PerMsgStatus" at
(eval 761) line 1359.
Jul 27 04:26:53 coyote spamd[10637]: )
Jul 27 04:26:53 coyote spamd[10637]: rules: failed to run CG_DOUBLEDOT_GIF
test, skipping:
Jul 27 04:26:53 coyote spamd[10637]: (Can't locate object
method "image_name_regex" via package "Mail::SpamAssassin::PerMsgStatus" at
(eval 761) line 1618.
Jul 27 04:26:53 coyote spamd[10637]: )
Jul 27 04:26:53 coyote spamd[10637]: rules: failed to run CG_SONY_JPG test,
skipping:
Jul 27 04:26:53 coyote spamd[10637]: (Can't locate object
method "image_name_regex" via package "Mail::SpamAssassin::PerMsgStatus" at
(eval 761) line 2581.
Jul 27 04:26:53 coyote spamd[10637]: )
Jul 27 04:26:53 coyote spamd[10637]: rules: failed to run CG_CANON_JPG test,
skipping:
Jul 27 04:26:53 coyote spamd[10637]: (Can't locate object
method "image_name_regex" via package "Mail::SpamAssassin::PerMsgStatus" at
(eval 761) line 3918.
Jul 27 04:26:53 coyote spamd[10637]: )
Jul 27 04:26:53 coyote spamd[11153]: pyzor: check failed: util: setuid 0 to
500 failed! at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/Util.pm
line 1343.
Jul 27 04:26:55 coyote spamd[11153]: spamd: clean message (-3.0/5.0) for
gene:500 in 3.0 seconds, 3620 bytes.
Jul 27 04:26:55 coyote spamd[11153]: spamd: result: . -3 -
AWL,BAYES_00,RCVD_IN_DNSWL_LOW,RDNS_NONE
scantime=3.0,size=3620,user=gene,uid=500,required_score=5.0,rhost=localhost.localdomain,raddr=127.0.0.1,rport=33941,mid=<11...@thor.sulgenrain.local>,bayes=0.000000,autolearn=ham
Jul 27 04:26:55 coyote spamd[11153]: spamd: accidental fork: 11153 != 10637
at /usr/bin/spamd line 1628.
Jul 27 04:26:57 coyote spamd[10637]: spamd: clean message (-3.0/5.0) for
gene:500 in 4.2 seconds, 3620 bytes.
Jul 27 04:26:57 coyote spamd[10637]: spamd: result: . -3 -
AWL,BAYES_00,RCVD_IN_DNSWL_LOW,RDNS_NONE
scantime=4.2,size=3620,user=gene,uid=500,required_score=5.0,rhost=localhost.localdomain,raddr=127.0.0.1,rport=33941,mid=<11...@thor.sulgenrain.local>,bayes=0.000000,autolearn=unavailable
Jul 27 04:26:57 coyote spamc[11152]: failed sanity check, 3832 bytes claimed,
7741 bytes seen
Jul 27 04:26:57 coyote spamd[10630]: prefork: child states: II
This is a per message occurrence. What should I check?
Thanks.
--
Cheers, Gene
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Writing is turning one's worst moments into money.
-- J.P. Donleavy
Re: upgraded to 3.2.2, now have errors
Posted by Ed Kasky <ed...@esson.net>.
On Fri, 27 Jul 2007, Gene Heskett wrote:
> On Friday 27 July 2007, Ed Kasky wrote:
>> At 09:58 AM Friday, 7/27/2007, Gene Heskett wrote -=>
>>
>>> On Friday 27 July 2007, Gene Heskett wrote:
>>>> Jul 27 04:26:53 coyote spamd[10637]: spamd: processing message
>>>> <11...@thor.sulgenrain.local> for gene:500
>>>> Jul 27 04:26:53 coyote spamd[10637]: rules: failed to run CG_FUJI_JPG
>>>> test, skipping:
>>>> Jul 27 04:26:53 coyote spamd[10637]: (Can't locate object
>>>> method "image_name_regex" via package "Mail::SpamAssassin::PerMsgStatus"
>>>> at (eval 761) line 1359.
>>>> Jul 27 04:26:53 coyote spamd[10637]: )
>>
>> -snip-
>>
>>>> This is a per message occurrence. What should I check?
>>>>
>>>> Thanks.
>>
>> If you did the same thing that I did, it's because when you upgraded
>> to 3.2.2, it over-wrote your copy of ImageInfo plugin which has the
>> function "image_name_regex" defined. The version that shipped with
>> 3.2.2 is actually older than the one from rulesemporium and the cf
>> for the newer version has the rules defined that caused your errors.
>>
>> You have two option if this is the case:
>> 1. Disable the rules in your imageinfo.cf
>> 2. Re-install ImageInfo.pm from rulesemporium
>>
> I was able to get the rulesdujour script to run, and it may have updated that
> file, if so, what filedate/version should I see in imageinfo.cf? Or the .pm
> file for that matter. I find I have that file
> in /var/lib/spamassassin/3.002001/updates-etc, but not
> in the /var/lib/spamassassin/3.002002 tree.
Both files from rulesemporium show version 0.7. I didn't see a
version # in the pm that shipped with 3.2.2.
Ed
. . . . . . . . . . . . . . .
Randomly generated quote:
One must think like a hero to behave like a merely decent
human being. -May Sarton, poet and novelist (1912-1995)
Re: upgraded to 3.2.2, now have errors
Posted by Gene Heskett <ge...@verizon.net>.
On Friday 27 July 2007, Ed Kasky wrote:
>At 09:58 AM Friday, 7/27/2007, Gene Heskett wrote -=>
>
>>On Friday 27 July 2007, Gene Heskett wrote:
>> >Jul 27 04:26:53 coyote spamd[10637]: spamd: processing message
>> ><11...@thor.sulgenrain.local> for gene:500
>> >Jul 27 04:26:53 coyote spamd[10637]: rules: failed to run CG_FUJI_JPG
>> > test, skipping:
>> >Jul 27 04:26:53 coyote spamd[10637]: (Can't locate object
>> >method "image_name_regex" via package "Mail::SpamAssassin::PerMsgStatus"
>> > at (eval 761) line 1359.
>> >Jul 27 04:26:53 coyote spamd[10637]: )
>
>-snip-
>
>> >This is a per message occurrence. What should I check?
>> >
>> >Thanks.
>
>If you did the same thing that I did, it's because when you upgraded
>to 3.2.2, it over-wrote your copy of ImageInfo plugin which has the
>function "image_name_regex" defined. The version that shipped with
>3.2.2 is actually older than the one from rulesemporium and the cf
>for the newer version has the rules defined that caused your errors.
>
>You have two option if this is the case:
>1. Disable the rules in your imageinfo.cf
>2. Re-install ImageInfo.pm from rulesemporium
>
I was able to get the rulesdujour script to run, and it may have updated that
file, if so, what filedate/version should I see in imageinfo.cf? Or the .pm
file for that matter. I find I have that file
in /var/lib/spamassassin/3.002001/updates-etc, but not
in the /var/lib/spamassassin/3.002002 tree.
>I took the latter path.
>
>And as Matt reminded me:
>"Note to self: don't use RDJ or other update scripts on the rulefiles
>that go with plugins.. Or do anything else that might update one without
>the other.."
>
>HTH
>
>Ed Kasky
>~~~~~~~~~
>Randomly Generated Quote (254 of 568):
>A thing long expected takes the form of the unexpected when
>at last it comes. - Mark Twain
--
Cheers, Gene
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
All Finagle Laws may be bypassed by learning the simple art of doing
without thinking.
Re: upgraded to 3.2.2, now have errors
Posted by Ed Kasky <ed...@esson.net>.
At 09:58 AM Friday, 7/27/2007, Gene Heskett wrote -=>
>On Friday 27 July 2007, Gene Heskett wrote:
> >Jul 27 04:26:53 coyote spamd[10637]: spamd: processing message
> ><11...@thor.sulgenrain.local> for gene:500
> >Jul 27 04:26:53 coyote spamd[10637]: rules: failed to run CG_FUJI_JPG test,
> >skipping:
> >Jul 27 04:26:53 coyote spamd[10637]: (Can't locate object
> >method "image_name_regex" via package "Mail::SpamAssassin::PerMsgStatus" at
> >(eval 761) line 1359.
> >Jul 27 04:26:53 coyote spamd[10637]: )
-snip-
> >This is a per message occurrence. What should I check?
> >
> >Thanks.
If you did the same thing that I did, it's because when you upgraded
to 3.2.2, it over-wrote your copy of ImageInfo plugin which has the
function "image_name_regex" defined. The version that shipped with
3.2.2 is actually older than the one from rulesemporium and the cf
for the newer version has the rules defined that caused your errors.
You have two option if this is the case:
1. Disable the rules in your imageinfo.cf
2. Re-install ImageInfo.pm from rulesemporium
I took the latter path.
And as Matt reminded me:
"Note to self: don't use RDJ or other update scripts on the rulefiles
that go with plugins.. Or do anything else that might update one without
the other.."
HTH
Ed Kasky
~~~~~~~~~
Randomly Generated Quote (254 of 568):
A thing long expected takes the form of the unexpected when
at last it comes. - Mark Twain
Re: upgraded to 3.2.2, now have errors
Posted by Gene Heskett <ge...@verizon.net>.
On Friday 27 July 2007, Gene Heskett wrote:
>Greetings;
>
>>>From /var/log/maillog:
>
>Jul 27 04:26:53 coyote spamd[10637]: spamd: processing message
><11...@thor.sulgenrain.local> for gene:500
>Jul 27 04:26:53 coyote spamd[10637]: rules: failed to run CG_FUJI_JPG test,
>skipping:
>Jul 27 04:26:53 coyote spamd[10637]: (Can't locate object
>method "image_name_regex" via package "Mail::SpamAssassin::PerMsgStatus" at
>(eval 761) line 1359.
>Jul 27 04:26:53 coyote spamd[10637]: )
>Jul 27 04:26:53 coyote spamd[10637]: rules: failed to run CG_DOUBLEDOT_GIF
>test, skipping:
>Jul 27 04:26:53 coyote spamd[10637]: (Can't locate object
>method "image_name_regex" via package "Mail::SpamAssassin::PerMsgStatus" at
>(eval 761) line 1618.
>Jul 27 04:26:53 coyote spamd[10637]: )
>Jul 27 04:26:53 coyote spamd[10637]: rules: failed to run CG_SONY_JPG test,
>skipping:
>Jul 27 04:26:53 coyote spamd[10637]: (Can't locate object
>method "image_name_regex" via package "Mail::SpamAssassin::PerMsgStatus" at
>(eval 761) line 2581.
>Jul 27 04:26:53 coyote spamd[10637]: )
>Jul 27 04:26:53 coyote spamd[10637]: rules: failed to run CG_CANON_JPG test,
>skipping:
>Jul 27 04:26:53 coyote spamd[10637]: (Can't locate object
>method "image_name_regex" via package "Mail::SpamAssassin::PerMsgStatus" at
>(eval 761) line 3918.
>Jul 27 04:26:53 coyote spamd[10637]: )
>Jul 27 04:26:53 coyote spamd[11153]: pyzor: check failed: util: setuid 0 to
>500 failed! at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/Util.pm
>line 1343.
>Jul 27 04:26:55 coyote spamd[11153]: spamd: clean message (-3.0/5.0) for
>gene:500 in 3.0 seconds, 3620 bytes.
>Jul 27 04:26:55 coyote spamd[11153]: spamd: result: . -3 -
>AWL,BAYES_00,RCVD_IN_DNSWL_LOW,RDNS_NONE
>scantime=3.0,size=3620,user=gene,uid=500,required_score=5.0,rhost=localhost.
>localdomain,raddr=127.0.0.1,rport=33941,mid=<1185524770.16292.235.camel@thor
>.sulgenrain.local>,bayes=0.000000,autolearn=ham Jul 27 04:26:55 coyote
> spamd[11153]: spamd: accidental fork: 11153 != 10637 at /usr/bin/spamd line
> 1628.
>Jul 27 04:26:57 coyote spamd[10637]: spamd: clean message (-3.0/5.0) for
>gene:500 in 4.2 seconds, 3620 bytes.
>Jul 27 04:26:57 coyote spamd[10637]: spamd: result: . -3 -
>AWL,BAYES_00,RCVD_IN_DNSWL_LOW,RDNS_NONE
>scantime=4.2,size=3620,user=gene,uid=500,required_score=5.0,rhost=localhost.
>localdomain,raddr=127.0.0.1,rport=33941,mid=<1185524770.16292.235.camel@thor
>.sulgenrain.local>,bayes=0.000000,autolearn=unavailable Jul 27 04:26:57
> coyote spamc[11152]: failed sanity check, 3832 bytes claimed, 7741 bytes
> seen
>Jul 27 04:26:57 coyote spamd[10630]: prefork: child states: II
>
>
>This is a per message occurrence. What should I check?
>
>Thanks.
Joanne, I've just discovered that ~/gene/mail/sa_failed is getting most of the
incoming mail since the 3.2.2 update. I need a sed script that I can use to
strip the SA headers so I can mv that whole file back to where fetchmail
hands it off so it will be re-sorted correctly once the 3.2.2 blues have been
handled.
And I'm still at a loss as to whats fubar. I took the stuff in the
ImageInfo.cf out that was causeing the error, and restarted spamassassin, but
its still doing it as of a couple of minutes ago.
If I can't revert this problem in another hour, I'll see if I can revert to
3.2.1
Hell, even this list is being diverted to the sa_failed file!
--
Cheers, Gene
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
I think I am an overnight sensation right now!!