Re: SA 3.3.0 and sa-compile

2009-10-02 Thread to...@starbridge.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Benny Pedersen a écrit :
 On tor 01 okt 2009 18:09:38 CEST, to...@starbridge.org wrote
 thank for your answers. It's done:
 https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6214

 also

 spamassassin 21 -D -t msg  output.log and another time with the
 plugin disabled shows it work (this time with output.log)

 add output.log to the ticket

it's done


-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkrFs78ACgkQ8FtMlUNHQIN86QCglgcJCF0r26lWKxWFoosEOT6h
qAIAn0B6yUq01LaXSI3RpsbEJDqqZwWb
=NKGw
-END PGP SIGNATURE-



Re: SA 3.3.0 and sa-compile

2009-10-01 Thread Zdenek Herman
I have same problem.
Any solution ?

Regards

Zdenek Herman
zdenek.her...@ille.cz
tel: 777 730 218
http://www.cistaposta.cz



to...@starbridge.org napsal(a):
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1

 Hi,
 i'm running SA 3.3.0 (3.3.0-alpha3-r808953) and i've some problem with
 compiled rules.

 sa-compile runs without errors, and SA seems to works fine when restarted.
 But some body rules are now not detected.

 exemple of simple body rule (for testing):

 body TONIO_SPAM_TEST/toniospam/i
 describe TONIO_SPAM_TESTMentions Generic toniospamtest
 score   TONIO_SPAM_TEST 5

 if i commented out
 loadplugin Mail::SpamAssassin::Plugin::Rule2XSBody
 in v320.pre, body rules is working again.

 I've tested with SA 3.2.5 and it's working fine with Rule2XSBody active.
 I've tried to delete compiled rules and compile again: same result.

 Some info on my environnement:
 debian testing
 perl v5.10.0
 xsubpp version 2.200401 (from debian perl package)
 re2c version 0.13.5-1

 Thanks for your help
 Regards
 Tonio

 NB: sorry for this second post, but i've made a mistake with the
 previous one (replying to  an other thread)

 -BEGIN PGP SIGNATURE-
 Version: GnuPG v1.4.9 (GNU/Linux)
 Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

 iEYEARECAAYFAkrDzE4ACgkQ8FtMlUNHQINOIgCeIgXvgz5VafWgZmeb7RhS3vvo
 7ZUAn0+ANE9/uzBbSTcCsn26PGVHlflt
 =sq17
 -END PGP SIGNATURE-


   


Re: SA 3.3.0 and sa-compile

2009-10-01 Thread John Hardin

On Thu, 1 Oct 2009, Zdenek Herman wrote:


I have same problem.
Any solution ?

to...@starbridge.org napsal(a):


i'm running SA 3.3.0 (3.3.0-alpha3-r808953) and i've some problem with
compiled rules.

sa-compile runs without errors, and SA seems to works fine when 
restarted. But some body rules are now not detected.


A suggestion to both of you, based on sa-compile support requests seen 
earlier on the list: run sa-compile with the debug option turned on, 
publish the debugging output and intermediate files on a webserver 
somewhere, and post the URIs for that info here so they can be examined.


--
 John Hardin KA7OHZhttp://www.impsec.org/~jhardin/
 jhar...@impsec.orgFALaholic #11174 pgpk -a jhar...@impsec.org
 key: 0xB8732E79 -- 2D8C 34F4 6411 F507 136C  AF76 D822 E6E6 B873 2E79
---
  Therapeutic Phrenologist - send email for affordable rate schedule.
---
 Approximately 9051420 firearms legally purchased in the U.S. this year


Re: SA 3.3.0 and sa-compile

2009-10-01 Thread Justin Mason
On Thu, Oct 1, 2009 at 16:15, John Hardin jhar...@impsec.org wrote:
 On Thu, 1 Oct 2009, Zdenek Herman wrote:

 I have same problem.
 Any solution ?

 to...@starbridge.org napsal(a):

 i'm running SA 3.3.0 (3.3.0-alpha3-r808953) and i've some problem with
 compiled rules.

 sa-compile runs without errors, and SA seems to works fine when
 restarted. But some body rules are now not detected.

 A suggestion to both of you, based on sa-compile support requests seen
 earlier on the list: run sa-compile with the debug option turned on, publish
 the debugging output and intermediate files on a webserver somewhere, and
 post the URIs for that info here so they can be examined.

even better: open a Bugzilla entry and do the same.  That's how we
track (possible) bugs and prioritize them.

-- 
--j.


Re: SA 3.3.0 and sa-compile

2009-10-01 Thread John Hardin

On Thu, 1 Oct 2009, Justin Mason wrote:


On Thu, Oct 1, 2009 at 16:15, John Hardin jhar...@impsec.org wrote:

On Thu, 1 Oct 2009, Zdenek Herman wrote:


I have same problem.
Any solution ?

to...@starbridge.org napsal(a):


i'm running SA 3.3.0 (3.3.0-alpha3-r808953) and i've some problem with
compiled rules.

sa-compile runs without errors, and SA seems to works fine when
restarted. But some body rules are now not detected.


A suggestion to both of you, based on sa-compile support requests seen
earlier on the list: run sa-compile with the debug option turned on, publish
the debugging output and intermediate files on a webserver somewhere, and
post the URIs for that info here so they can be examined.


even better: open a Bugzilla entry and do the same.  That's how we
track (possible) bugs and prioritize them.


And the bugzilla entry could have the logs as attachments. I wasn't sure 
if it was appropriate to open a bug yet, but if Justin suggests it then I 
guess it is...


--
 John Hardin KA7OHZhttp://www.impsec.org/~jhardin/
 jhar...@impsec.orgFALaholic #11174 pgpk -a jhar...@impsec.org
 key: 0xB8732E79 -- 2D8C 34F4 6411 F507 136C  AF76 D822 E6E6 B873 2E79
---
  Therapeutic Phrenologist - send email for affordable rate schedule.
---
 Approximately 9051420 firearms legally purchased in the U.S. this year


Re: SA 3.3.0 and sa-compile

2009-10-01 Thread to...@starbridge.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Justin Mason a écrit :
 On Thu, Oct 1, 2009 at 16:15, John Hardin jhar...@impsec.org wrote:
 On Thu, 1 Oct 2009, Zdenek Herman wrote:

 I have same problem.
 Any solution ?

 to...@starbridge.org napsal(a):

 i'm running SA 3.3.0 (3.3.0-alpha3-r808953) and i've some problem with
 compiled rules.

 sa-compile runs without errors, and SA seems to works fine when
 restarted. But some body rules are now not detected.
 A suggestion to both of you, based on sa-compile support requests seen
 earlier on the list: run sa-compile with the debug option turned on,
publish
 the debugging output and intermediate files on a webserver somewhere, and
 post the URIs for that info here so they can be examined.

 even better: open a Bugzilla entry and do the same.  That's how we
 track (possible) bugs and prioritize them.

thank for your answers.
It's done:
https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6214
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkrE1EEACgkQ8FtMlUNHQINOJgCdG7Piu3Phd1Mb2iYl7dmX1pV7
b0UAn1yITwVbWgddDiUlJtdQgCWsb4QL
=mPa4
-END PGP SIGNATURE-



Re: SA 3.3.0 and sa-compile

2009-10-01 Thread Benny Pedersen

On tor 01 okt 2009 18:09:38 CEST, to...@starbridge.org wrote

thank for your answers.
It's done:
https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6214


also

spamassassin 21 -D -t msg  output.log
and another time with the plugin disabled shows it work (this time  
with output.log)


add output.log to the ticket

--
xpoint



SA 3.3.0 and sa-compile

2009-09-30 Thread to...@starbridge.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi,
i'm running SA 3.3.0 (3.3.0-alpha3-r808953) and i've some problem with
compiled rules.

sa-compile runs without errors, and SA seems to works fine when restarted.
But some body rules are now not detected.

exemple of simple body rule (for testing):

body TONIO_SPAM_TEST/toniospam/i
describe TONIO_SPAM_TESTMentions Generic toniospamtest
score   TONIO_SPAM_TEST 5

if i commented out
loadplugin Mail::SpamAssassin::Plugin::Rule2XSBody
in v320.pre, body rules is working again.

I've tested with SA 3.2.5 and it's working fine with Rule2XSBody active.
I've tried to delete compiled rules and compile again: same result.

Some info on my environnement:
debian testing
perl v5.10.0
xsubpp version 2.200401 (from debian perl package)
re2c version 0.13.5-1

Thanks for your help
Regards
Tonio

NB: sorry for this second post, but i've made a mistake with the
previous one (replying to  an other thread)

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkrDzE4ACgkQ8FtMlUNHQINOIgCeIgXvgz5VafWgZmeb7RhS3vvo
7ZUAn0+ANE9/uzBbSTcCsn26PGVHlflt
=sq17
-END PGP SIGNATURE-



Re: 3.3.0 and sa-compile

2009-09-29 Thread to...@starbridge.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

to...@starbridge.org a écrit :
 to...@starbridge.org a écrit :
 Benny Pedersen a écrit :
 On fre 25 sep 2009 13:38:19 CEST, to...@starbridge.org wrote
 I've tested with SA 3.2.5 and it's working fine with
 Rule2XSBody active. I've tried to delete compiled rules and
 compile again: same result.
 forget to sa-compile in 3.3 ?
 sa-compile has been run correctly with no errors (even in debug)
 has anyone encountered the same problem ?
nobody ?
i really need help on this one

thx
Regards
Tonio
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkrBpuIACgkQ8FtMlUNHQINEvwCg27ECYMTslFW1K80srvM5SdB3
YB0AoIytnseU1nW6iqlRasCNTCNFjrQW
=tjQR
-END PGP SIGNATURE-



Re: 3.3.0 and sa-compile

2009-09-29 Thread McDonald, Dan
On Tue, 2009-09-29 at 08:19 +0200, to...@starbridge.org wrote:
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1
 
 to...@starbridge.org a écrit :
  to...@starbridge.org a écrit :
  Benny Pedersen a écrit :
  On fre 25 sep 2009 13:38:19 CEST, to...@starbridge.org wrote
  I've tested with SA 3.2.5 and it's working fine with
  Rule2XSBody active. I've tried to delete compiled rules and
  compile again: same result.
  forget to sa-compile in 3.3 ?
  sa-compile has been run correctly with no errors (even in debug)
  has anyone encountered the same problem ?

Someone posted a problem with perl 5.6. What version of perl are you
running?

-- 
Daniel J McDonald, CCIE # 2495, CISSP # 78281, CNX
www.austinenergy.com


signature.asc
Description: This is a digitally signed message part


Re: 3.3.0 and sa-compile

2009-09-29 Thread to...@starbridge.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

McDonald, Dan a écrit :
 On Tue, 2009-09-29 at 08:19 +0200, to...@starbridge.org wrote:
 -BEGIN PGP SIGNED MESSAGE- Hash: SHA1

 to...@starbridge.org a écrit :
 to...@starbridge.org a écrit :
 Benny Pedersen a écrit :
 On fre 25 sep 2009 13:38:19 CEST, to...@starbridge.org
 wrote
 I've tested with SA 3.2.5 and it's working fine with
 Rule2XSBody active. I've tried to delete compiled rules
 and compile again: same result.
 forget to sa-compile in 3.3 ?
 sa-compile has been run correctly with no errors (even in
 debug)
 has anyone encountered the same problem ?

 Someone posted a problem with perl 5.6. What version of perl are
 you running?

thx for your answer

perl v5.10.0

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkrCDtUACgkQ8FtMlUNHQIOPZgCfSY4GphHXEhWNolU7h0pYKcas
r8kAn1iP1rtNl9WHYPszFPBrpgpjECqv
=ccGX
-END PGP SIGNATURE-



Re: 3.3.0 and sa-compile

2009-09-26 Thread to...@starbridge.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

to...@starbridge.org a écrit :
 Benny Pedersen a écrit :
 On fre 25 sep 2009 13:38:19 CEST, to...@starbridge.org wrote

 I've tested with SA 3.2.5 and it's working fine with
 Rule2XSBody active. I've tried to delete compiled rules and
 compile again: same result.
 forget to sa-compile in 3.3 ?

 sa-compile has been run correctly with no errors (even in debug)
has anyone encountered the same problem ?
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkq9zccACgkQ8FtMlUNHQIMA4wCeK5STV5P49zdRhMgdy9saHmfq
a4oAoNdduS36HIID3G38afVydbgxBhgb
=D8Ng
-END PGP SIGNATURE-



3.3.0 and sa-compile

2009-09-25 Thread to...@starbridge.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi,
i'm running SA 3.3.0 (3.3.0-alpha3-r808953) and i've some problem with
compiled rules.

sa-compile runs without errors, and SA seems to works fine when restarted.
But some body rules are now not detected.

exemple of simple body rule (for testing):

body TONIO_SPAM_TEST/toniospam/i
describe TONIO_SPAM_TESTMentions Generic toniospamtest
score   TONIO_SPAM_TEST 5

if i commented out
loadplugin Mail::SpamAssassin::Plugin::Rule2XSBody
in v320.pre, rules is working again.

I've tested with SA 3.2.5 and it's working fine with Rule2XSBody active.
I've tried to delete compiled rules and compile again: same result.

Some info on my environnement:
debian testing
xsubpp version 2.200401 (from debian perl package)
re2c version 0.13.5-1

Thanks for your help
Regard
Tonio



-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkq8q6sACgkQ8FtMlUNHQIN9zwCg3s5HNL7DKUBRo8fTLbD6BsqV
aWMAoLnDI/+eABGST8KEG5todvABFUSF
=aDLE
-END PGP SIGNATURE-



Re: 3.3.0 and sa-compile

2009-09-25 Thread Benny Pedersen

On fre 25 sep 2009 13:38:19 CEST, to...@starbridge.org wrote


I've tested with SA 3.2.5 and it's working fine with Rule2XSBody
active. I've tried to delete compiled rules and compile again: same
result.


forget to sa-compile in 3.3 ?

--
xpoint



Re: 3.3.0 and sa-compile

2009-09-25 Thread to...@starbridge.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Benny Pedersen a écrit :
 On fre 25 sep 2009 13:38:19 CEST, to...@starbridge.org wrote

 I've tested with SA 3.2.5 and it's working fine with Rule2XSBody
 active. I've tried to delete compiled rules and compile again:
 same result.

 forget to sa-compile in 3.3 ?

sa-compile has been run correctly with no errors (even in debug)
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkq8syMACgkQ8FtMlUNHQIP2+wCdGgQpUR/MLpHT8hdW+4ooARAP
bYIAnRHf2xM7QeUE1HGWirN3OTTovnVW
=tO8Q
-END PGP SIGNATURE-



Re: 3.3.0 and sa-compile

2009-09-25 Thread Matt Kettler
to...@starbridge.org wrote:
 Benny Pedersen a écrit :
  On fre 25 sep 2009 13:38:19 CEST, to...@starbridge.org wrote

  I've tested with SA 3.2.5 and it's working fine with Rule2XSBody
  active. I've tried to delete compiled rules and compile again:
  same result.
  forget to sa-compile in 3.3 ?

 sa-compile has been run correctly with no errors (even in debug)