Re: Apache SpamAssassin 3.2.0 using older version of ImageInfo

r p wrote: I can not even get the 3.2 to run cleanly due to ImageInfo. When I leave the ImageInfo in the init.pre and in the plugin directory I get: That's the problem, ImageInfo is enabled in v320.pre in the new SA, review that old init.pre . What plugin directory? what do you mean by that

Re: re2c and sare rules

On Sun, 06 May 2007 13:25:08 +0100 [EMAIL PROTECTED] (Justin Mason) wrote: > Loren Wilton writes: > > Its a new feature with 3.2. We have to rewrite most of the obfu > > rules to get around this, and none of us have had the time yet. > > more correctly, it's a perl bug, not a new feature in 3.2.

Re: Apache SpamAssassin 3.2.0 using older version of ImageInfo

On Sun, May 06, 2007 at 02:59:13PM -0700, r p wrote: > I can not even get the 3.2 to run cleanly due to ImageInfo. > When I leave the ImageInfo in the init.pre and in the plugin directory I get: > warn: Subroutine new redefined at /etc/mail/spamassassin/ImageInfo.pm > line 68. You have the standar

Re: Apache SpamAssassin 3.2.0 using older version of ImageInfo

On 2 May 2007 at 15:32, Rose, Bobby wrote: > The ImageInfo packaged with 3.2.0 isn't the latest version from SARE as > it's missing the image_name_regex method. > > -=B > > I can not even get the 3.2 to run cleanly due to ImageInfo. When I leave the ImageInfo in the init.pre and in the plugin dir

Re: False Positive

Marc Perkel wrote the following on 5/6/2007 9:17 AM -0800: > Been getting a few strange false positives lately. Here's something > unusual. > > X-Spam-Report: > * 0.0 HTML_MESSAGE BODY: HTML included in message > * -2.0 BAYES_05 BODY: Bayesian spam probability is 1 to 5% > * [score: 0.0206] >

R: False Positive

> -Messaggio originale- > Da: Marc Perkel [mailto:[EMAIL PROTECTED] > > Been getting a few strange false positives lately. Here's something > unusual. > > X-Spam-Report: > * 0.0 HTML_MESSAGE BODY: HTML included in message > * -2.0 BAYES_05 BODY: Bayesian spam probability is 1 to 5% >

False Positive

Been getting a few strange false positives lately. Here's something unusual. X-Spam-Report: * 0.0 HTML_MESSAGE BODY: HTML included in message * -2.0 BAYES_05 BODY: Bayesian spam probability is 1 to 5% * [score: 0.0206] * 1.4 MIME_QP_LONG_LINE RAW: Quoted-printable line longer than 76 chars

Evaluating how good is a rule

Dears, I'm something in need to write custom rules in order to penalize some kind of messages running through my SA. Now, of course I do apply a 0.001 score to my own test rules in order not to create FPs on received mails. Also, things are setup such that no SA header is added to messages yieldi

Problem installing SA 3.2.0 via CPAN on OPenSuSE 10.2 or SLES 10

Hi guys, I've tried to install SA 3.2.0 on both an unpatched and fully patched versions of OpenSuSE 10.2 and SLES 10 via CPAN but on all attempts I receive the following errors during one of the test phases. It would be great if someone could help me out. t/spamc_z...Not fo

Re: sa-compile Problem

Klaus Heinz wrote: > Wolfgang Breyha wrote: > >> But after restarting spamd I get lots of message complaining about missing >> body_400.pm up to body_1000.pm and same for body_neg400.pm to >> body_neg1000.pm. > ^^^ > Are you sure about this one? I have not seen this yet. Correct! The

Re: SA-Compile Error

check the FAQ --[ UxBoD ]-- writes: > Hi, > > I have just run sa-compile against my rules which ran through okay. > Though when I perform a lint now I get the following error :- > > /usr/bin/perl: symbol lookup > error: > /var/lib/spamassassin/compiled/3.002000/auto/Mail/SpamAssassin/CompiledR

Re: sa-compile Problem

Wolfgang Breyha writes: > Hi! > > I tried to use sa-compile. sa-compile itself succeeded and body_0 rules are > built. > > But after restarting spamd I get lots of message complaining about missing > body_400.pm up to body_1000.pm and same for body_neg400.pm to body_neg1000.pm. > > eg.: > Can'

SA-Compile Error

Hi, I have just run sa-compile against my rules which ran through okay. Though when I perform a lint now I get the following error :- /usr/bin/perl: symbol lookup error: /var/lib/spamassassin/compiled/3.002000/auto/Mail/SpamAssassin/CompiledRegexps/body_0/body_0.so: undefined symbol: Mail_SpamAs

Re: re2c and sare rules

Loren Wilton writes: > Its a new feature with 3.2. We have to rewrite most of the obfu rules to > get around this, and none of us have had the time yet. more correctly, it's a perl bug, not a new feature in 3.2.0. --j.

Re: sa-compile Problem

yep, sounds like a bug, unfortunately... --j. Loren Wilton writes: > This looks like something that should be posted to Bugzilla. Likely there > was very little testing with allow_user_rules = 1. > > Loren > > - Original Message - > From: "Klaus Heinz" <[EMAIL PROTECTED]> >

RE: ANNOUNCE: Apache SpamAssassin 3.2.0 available

At 07:56 AM 5.5.2007 -0400, Michael Scheidell wrote: > >> -Original Message- >> From: Jack L. Stone [mailto:[EMAIL PROTECTED] >> Sent: Friday, May 04, 2007 9:20 AM >> To: Justin Mason; users@spamassassin.apache.org; >> [EMAIL PROTECTED]; [EMAIL PROTECTED] >> Cc: [EMAIL PROTECTED] >> Subje

Re: sa-compile Problem

This looks like something that should be posted to Bugzilla. Likely there was very little testing with allow_user_rules = 1. Loren - Original Message - From: "Klaus Heinz" <[EMAIL PROTECTED]> To: Sent: Sunday, May 06, 2007 1:57 AM Subject: Re: sa-compile Problem Wolfgang B

Re: sa-compile Problem

Wolfgang Breyha wrote: > But after restarting spamd I get lots of message complaining about missing > body_400.pm up to body_1000.pm and same for body_neg400.pm to body_neg1000.pm. ^^^ Are you sure about this one? I have not seen this yet. > > eg.: > Can't locate Mail/SpamAssassin/Co