Mailing List Archive: is this a spamassassin error?

is this a spamassassin error?

Feb 11, 2004, 8:29 AM

Post #1 of 4 (867 views)

I'm receiving the following error message in my logs:

Feb 11 09:35:33 gemini2 mimedefang-multiplexor: Slave 0 stderr: Failed
to run __MIME_HTML SpamAssassin test, skipping: ^I(Can't locate object
method "check_for_mime_html" via package
"Mail::SpamAssassin::PerMsgStatus" at
/usr/lib/perl5/site_perl/5.8.0/Mail/SpamAssassin/PerMsgStatus.pm line
2086. )

Is this a spamassassin or a mimedefang error? I can't seem to locate
any information about this particular error.

Re: is this a spamassassin error? [ In reply to ]

mkettler at evi-inc

Feb 11, 2004, 8:44 AM

Post #2 of 4 (858 views)

Permalink

At 10:29 AM 2/11/2004, Dana Holland wrote:
>Feb 11 09:35:33 gemini2 mimedefang-multiplexor: Slave 0 stderr: Failed to
>run __MIME_HTML SpamAssassin test, skipping: ^I(Can't locate object method
>"check_for_mime_html" via package "Mail::SpamAssassin::PerMsgStatus" at
>/usr/lib/perl5/site_perl/5.8.0/Mail/SpamAssassin/PerMsgStatus.pm line 2086. )
>
>
>Is this a spamassassin or a mimedefang error? I can't seem to locate any
>information about this particular error.

What version of SA are you using? That function should be a part of
evaltests.pm and has been there since 2.60.

It sounds like you've got somehow or another got SA code that's pre 2.60,
with rules that are post 2.60.

Did you have an upgrade that failed? Did you try to take the rules from a
new version of SA and forcibly load them in an old version?

Re: is this a spamassassin error? [ In reply to ]

dana.work at navarrocollege

Feb 11, 2004, 8:47 AM

Post #3 of 4 (861 views)

Permalink

I just installed (last week) version 2.63. As far as I could tell, the
upgrade worked just fine - I didn't see any errors at all. Maybe I
failed to do something?

Actually, I made no changes to the rules at all. Perhaps that's my
problem. (I'm definitely a newbie)

Matt Kettler wrote:

> At 10:29 AM 2/11/2004, Dana Holland wrote:
>
>> Feb 11 09:35:33 gemini2 mimedefang-multiplexor: Slave 0 stderr: Failed
>> to run __MIME_HTML SpamAssassin test, skipping: ^I(Can't locate object
>> method "check_for_mime_html" via package
>> "Mail::SpamAssassin::PerMsgStatus" at
>> /usr/lib/perl5/site_perl/5.8.0/Mail/SpamAssassin/PerMsgStatus.pm line
>> 2086. )
>>
>>
>> Is this a spamassassin or a mimedefang error? I can't seem to locate
>> any information about this particular error.
>
>
> What version of SA are you using? That function should be a part of
> evaltests.pm and has been there since 2.60.
>
> It sounds like you've got somehow or another got SA code that's pre
> 2.60, with rules that are post 2.60.
>
> Did you have an upgrade that failed? Did you try to take the rules from
> a new version of SA and forcibly load them in an old version?
>
>
>
>
>

Re: is this a spamassassin error? [ In reply to ]

dana.work at navarrocollege

Feb 11, 2004, 2:35 PM

Post #4 of 4 (856 views)

Permalink

The good news is, I reinstalled using CPAN and I'm no longer getting
these error messages.

The bad news is, it's no longer flagging anything as spam. I still
haven't figured out what changed.

Dana Holland wrote:

> I just installed (last week) version 2.63. As far as I could tell, the
> upgrade worked just fine - I didn't see any errors at all. Maybe I
> failed to do something?
>
> Actually, I made no changes to the rules at all. Perhaps that's my
> problem. (I'm definitely a newbie)
>
>
> Matt Kettler wrote:
>
>> At 10:29 AM 2/11/2004, Dana Holland wrote:
>>
>>> Feb 11 09:35:33 gemini2 mimedefang-multiplexor: Slave 0 stderr:
>>> Failed to run __MIME_HTML SpamAssassin test, skipping: ^I(Can't
>>> locate object method "check_for_mime_html" via package
>>> "Mail::SpamAssassin::PerMsgStatus" at
>>> /usr/lib/perl5/site_perl/5.8.0/Mail/SpamAssassin/PerMsgStatus.pm line
>>> 2086. )
>>>
>>>
>>> Is this a spamassassin or a mimedefang error? I can't seem to locate
>>> any information about this particular error.
>>
>>
>>
>> What version of SA are you using? That function should be a part of
>> evaltests.pm and has been there since 2.60.
>>
>> It sounds like you've got somehow or another got SA code that's pre
>> 2.60, with rules that are post 2.60.
>>
>> Did you have an upgrade that failed? Did you try to take the rules
>> from a new version of SA and forcibly load them in an old version?
>>
>>
>>
>>
>>
>
>
>
>