I seem to be missing something on the configuration of F, or
perhaps my knowledge of how to install plugins is lacking. I initially
put this line in /
loadplugin F /
and spamassassin complains:
smtp.cs.utexas.edu$ spamassassin
[8948] warn: plugin: failed to load plugin / No such file or directory
smtp.cs.utexas.edu$
Huh? I don't understand why it is looking there for F, but ok,
I'll rename it (and edit the path in init.pre):
smtp.cs.utexas.edu$ mv / \
/
smtp.cs.utexas.edu$ spamassassin
[9334] warn: Subroutine new redefined at / line 56.
[9334] warn: Subroutine parse_config redefined at / line 66.
[9334] warn: Subroutine dummy_check redefined at / line 101.
[9334] warn: Subroutine wrong_ctype redefined at / line 105.
[9334] warn: Subroutine corrupt_img redefined at / line 119.
[9334] warn: Subroutine check_fuzzy_ocr redefined at / line 133.
smtp.cs.utexas.edu$
Does anyone know why perl is generating these warnings? The plugin seems
to work otherwise, i.e. it correctly identifies the images in the sample
tar file.
Thanks
Fletcher

PGP SIGNED MESSAGE
Hash: SHA1

Fletcher Mattox wrote:
I seem to be missing something on the configuration of F, or
perhaps my knowledge of how to install plugins is lacking. I
initially put this line in /

loadplugin F /

and spamassassin complains:

smtp.cs.utexas.edu$ spamassassin [8948] warn: plugin: failed
to load plugin / No
such file or directory smtp.cs.utexas.edu$

Huh? I don't understand why it is looking there for F,
but ok, I'll rename it (and edit the path in init.pre):

smtp.cs.utexas.edu$ mv / \
/

smtp.cs.utexas.edu$ spamassassin [9334] warn: Subroutine new
redefined at / line
56. [9334] warn: Subroutine parse_config redefined at
/ line 66. [9334]
warn: Subroutine dummy_check redefined at
/ line 101. [9334]
warn: Subroutine wrong_ctype redefined at
/ line 105. [9334]
warn: Subroutine corrupt_img redefined at
/ line 119. [9334]
warn: Subroutine check_fuzzy_ocr redefined at
/ line 133.
smtp.cs.utexas.edu$

Does anyone know why perl is generating these warnings? The plugin
seems to work otherwise, i.e. it correctly identifies the images in
the sample tar file.

Thanks Fletcher

You should simply extract the tar.gz file into
/etc/mail/spamassassin/, there is no need to put anything in pre
files, everything is done in the cf file that is shipped :)

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

llzRPQrkAias4xr9X10=
=Uz8v
PGP SIGNATURE

Chris,

Seems like I have to specify rule priority above 500 for fuzzy_ocr rules,
otherwise the focr_autodisable_score is mostly ineffective as it misses
half the SARE and similar meta rules. Something like:

priority FUZZYCR 600
priority FUZZYCR_WRNG_CTYPE 600
priority FUZZYCR_CRRUPT_IMG 600

does the job (I'm not sure if all are necessary).

Mark

PGP SIGNED MESSAGE
Hash: SHA1

Mark Martinec wrote:
Chris,

Seems like I have to specify rule priority above 500 for fuzzy_ocr rules,
otherwise the focr_autodisable_score is mostly ineffective as it misses
half the SARE and similar meta rules. Something like:

priority FUZZYCR 600
priority FUZZYCR_WRNG_CTYPE 600
priority FUZZYCR_CRRUPT_IMG 600

does the job (I'm not sure if all are necessary).

Mark

Yea some people reported that earlier, I will include that into the
newest release (in some hours). Btw, only the first priority line is
required, the other two rules are never called directly for scoring,
so they don't need priority :)

Thanks,

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

y2xHQJC2s08DRWYxgGBUA=
=N/Gd
PGP SIGNATURE

Just to double check all of the plugins currently for my
SpamAssassin installation are located in
/ so, that's where I stuck
the .cf and .pm that come with the FPlugin tarball. I still get
the image spams thoughshould the .cf actually be in
/etc/mail/spamassassin? I sort of want to have an idea of what's right
here before I go and push anything out on production boxes. Thanks!

yes they should be in /etc/mail/spamassassin

make sure you lint the ruleset also afterwards and then resart spamd (or
amavis in my case)

PGP SIGNED MESSAGE
Hash: SHA1

Ryan Steele wrote:
All,

Just to double check all of the plugins currently for my
SpamAssassin installation are located in
/ so, that's where I
stuck the .cf and .pm that come with the FPlugin tarball. I
still get the image spams thoughshould the .cf actually be in
/etc/mail/spamassassin? I sort of want to have an idea of what's
right here before I go and push anything out on production boxes.
Thanks!

Best Regards, Ryan

decoder wrote:

All files should go to /etc/mail/spamassassin/. You can probably put
the .pm file somewhere else, but I don't know if you need to change
the .cf file then so it finds the plugin, so if you want to make sure,
simply put both files there.

Chris

P.S.: Be aware that the current version does not do any error
handling, if something goes wrong, the worst case is that all
spamassassin checks are canceled. So pay attention when using this in
a production environment. I am currently working on a new version with
better error handling and will release it soon.

Fletcher Mattox wrote:

I seem to be missing something on the configuration of
F, or perhaps my knowledge of how to install plugins
is lacking. I initially put this line in
/

loadplugin F
/

and spamassassin complains:

smtp.cs.utexas.edu$ spamassassin [8948] warn: plugin:
failed to load plugin
/ No such file
or directory smtp.cs.utexas.edu$

Huh? I don't understand why it is looking there for
F, but ok, I'll rename it (and edit the path in
init.pre):

smtp.cs.utexas.edu$ mv
/ \
/

smtp.cs.utexas.edu$ spamassassin [9334] warn:
Subroutine new redefined at
/ line 56.
[9334] warn: Subroutine parse_config redefined at
/ line 66.
[9334] warn: Subroutine dummy_check redefined at
/ line 101.
[9334] warn: Subroutine wrong_ctype redefined at
/ line 105.
[9334] warn: Subroutine corrupt_img redefined at
/ line 119.
[9334] warn: Subroutine check_fuzzy_ocr redefined at
/ line 133.
smtp.cs.utexas.edu$

Does anyone know why perl is generating these warnings? The
plugin seems to work otherwise, i.e. it correctly identifies
the images in the sample tar file.

Thanks Fletcher

You should simply extract the tar.gz file into
/etc/mail/spamassassin/, there is no need to put anything in pre
files, everything is done in the cf file that is shipped :)

Chris

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

bToT+tDEGR/UepgrTUr9yYM=
=ah+M
PGP SIGNATURE

decoder wrote:
PGP SIGNED MESSAGE
Hash: SHA1

Ryan Steele wrote:

>All,
>>
>Just to double check all of the plugins currently for my
>SpamAssassin installation are located in
>/ so, that's where I
>stuck the .cf and .pm that come with the FPlugin tarball. I
>still get the image spams thoughshould the .cf actually be in
>/etc/mail/spamassassin? I sort of want to have an idea of what's
>right here before I go and push anything out on production boxes.
>Thanks!
>>
>Best Regards, Ryan
>>
>decoder wrote:
>
>
All files should go to /etc/mail/spamassassin/. You can probably put
the .pm file somewhere else, but I don't know if you need to change
the .cf file then so it finds the plugin, so if you want to make sure,
simply put both files there.

you can put the .pm anywhere you want. For instance I've put all the
plugins I use to /etc/mail/spamassassin/plugins
then I added the following line to v310.pre (that's where the LoadPlugin
directives should land officially)

loadplugin F /

Matt

PGP SIGNED MESSAGE
Hash: SHA1

Matthias Keller wrote:
decoder wrote:
>PGP SIGNED MESSAGE Hash: SHA1
>>
>Ryan Steele wrote:
>>
All,

Just to double check all of the plugins currently for my
SpamAssassin installation are located in
/ so, that's where I
stuck the .cf and .pm that come with the FPlugin
tarball. I still get the image spams thoughshould the .cf
actually be in /etc/mail/spamassassin? I sort of want to have
an idea of what's right here before I go and push anything out
on production boxes. Thanks!

Best Regards, Ryan

decoder wrote:

>>
>All files should go to /etc/mail/spamassassin/. You can probably
>put the .pm file somewhere else, but I don't know if you need to
>change the .cf file then so it finds the plugin, so if you want
>to make sure, simply put both files there.
>>
you can put the .pm anywhere you want. For instance I've put all
the plugins I use to /etc/mail/spamassassin/plugins then I added
the following line to v310.pre (that's where the LoadPlugin
directives should land officially)

loadplugin F /

Matt
That is a possibility too, though you need to watch out not to load
the plugin twice. The standard .cf file contains already a loadplugin
line, so you need to remove thatone if you put it into the pre file :)

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

Q+rjv4XXCqZDfEbjNr8C7nk=
=yEQl
PGP SIGNATURE