SpamAssassin 3.2.0 released!

Dear John
I updating to 1.29.6 and run script http://files.directadmin.com/services/all/spam.sh




ms# /usr/bin/spamd -d -c -m 5
[68220] info: config: score: the non-numeric score (.85) is not valid, a numeric score is required
[68220] info: config: SpamAssassin failed to parse line, "MY_DSL .85" is not valid for "score", skipping: score MY_DSL .85
[68220] info: config: score: the non-numeric score (.25) is not valid, a numeric score is required
[68220] info: config: SpamAssassin failed to parse line, "AOL_DSL .25" is not valid for "score", skipping: score AOL_DSL .25
[68220] info: config: score: the non-numeric score (.75) is not valid, a numeric score is required
[68220] info: config: SpamAssassin failed to parse line, "SARE_FROM_SPAM_WORD3 .75" is not valid for "score", skipping: score SARE_FROM_SPAM_WORD3 .75
[68220] info: config: score: the non-numeric score (.43) is not valid, a numeric score is required
[68220] info: config: SpamAssassin failed to parse line, "SALES_REPLY .43" is not valid for "score", skipping: score SALES_REPLY .43
 
# killall -9 spamd
# /usr/bin/spamd -d -c -m 5

is enought to fix it, without reboot the box.

Code:
>/usr/bin/spamd -d -c -m 5
[8727] warn: server socket setup failed, retry 1: spamd: could not create INET socket on 127.0.0.1:783: Address already in use
[8727] warn: server socket setup failed, retry 2: spamd: could not create INET socket on 127.0.0.1:783: Address already in use
[8727] error: spamd: could not create INET socket on 127.0.0.1:783: Address already in use
spamd: could not create INET socket on 127.0.0.1:783: Address already in use
 
Ai,

for the intressted my local.cf:

report_safe 1
fold_headers 1
use_bayes 1
bayes_auto_learn 1
skip_rbl_checks 0
use_razor2 1
use_dcc 1
use_pyzor 1

and my v320.pre
# Plugins which used to be EvalTests.pm
# broken out into separate plugins
loadplugin Mail::SpamAssassin::plugin::Bayes
loadplugin Mail::SpamAssassin::plugin::BodyEval
loadplugin Mail::SpamAssassin::plugin::DNSEval
loadplugin Mail::SpamAssassin::plugin::HTMLEval
loadplugin Mail::SpamAssassin::plugin::HeaderEval
loadplugin Mail::SpamAssassin::plugin::MIMEEval
loadplugin Mail::SpamAssassin::plugin::RelayEval
loadplugin Mail::SpamAssassin::plugin::URIEval
loadplugin Mail::SpamAssassin::plugin::WLBLEval
loadplugin Mail::SpamAssassin::plugin::Razor2
loadplugin Mail::SpamAssassin::plugin::DCC
 
Last edited:
HTML::parser 3.55

I can confirm that HTML::parser 3.55 works with the default Centos 3 perl (5.8.0) and with that the new spamassassin will build.

Jon
 
I have a problem when i run
spamassassin -D -lint

It stalls on at this part
[17600] dbg: dns: is Net::DNS::Resolver available? yes
[17600] dbg: dns: Net::DNS version: 0.59


Anyone have any ideas ? I thought it mite be my resolvers but ive changed them, and still doesnt seem to fix the problem...

I have all modules installed
 
I have a problem when i run
spamassassin -D -lint

It stalls on at this part
[17600] dbg: dns: is Net::DNS::Resolver available? yes
[17600] dbg: dns: Net::DNS version: 0.59


Anyone have any ideas ? I thought it mite be my resolvers but ive changed them, and still doesnt seem to fix the problem...

I have all modules installed

Same happens to me... Is it normal or something need to patched/fixed

Code:
[root@server ~]# spamassassin -D -lint
[28135] warn: The -l option has been deprecated and is no longer supported, ignoring.
[28135] dbg: logger: adding facilities: all
[28135] dbg: logger: logging level is DBG
[28135] dbg: generic: SpamAssassin version 3.2.0
[28135] dbg: config: score set 0 chosen.
[28135] dbg: util: running in taint mode? yes
[28135] dbg: util: taint mode: deleting unsafe environment variables, resetting PATH
[28135] dbg: util: PATH included '/usr/kerberos/sbin', keeping
[28135] dbg: util: PATH included '/usr/kerberos/bin', keeping
[28135] dbg: util: PATH included '/usr/local/sbin', keeping
[28135] dbg: util: PATH included '/usr/local/bin', keeping
[28135] dbg: util: PATH included '/sbin', keeping
[28135] dbg: util: PATH included '/bin', keeping
[28135] dbg: util: PATH included '/usr/sbin', keeping
[28135] dbg: util: PATH included '/usr/bin', keeping
[28135] dbg: util: PATH included '/usr/X11R6/bin', keeping
[28135] dbg: util: PATH included '/root/bin', which doesn't exist, dropping
[28135] dbg: util: final PATH set to: /usr/kerberos/sbin:/usr/kerberos/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/X11R6/bin
[28135] dbg: dns: no ipv6
[28135] dbg: dns: is Net::DNS::Resolver available? yes
[28135] dbg: dns: Net::DNS version: 0.59
 
the same problem occurs here on a production server with version 3.1.8 wich working fine.

i m currently testing version 3.2.0 on a non-production server with no success.

No errors anymore after starting spamd, but no sign of spamd in the mail headers.

Somebody ?
 
When I run the 'spamassassin --lint' command I get the following. Do I have rule configuration problems??

*************************************

[root@stargatesg1 spamassassin]# spamassassin --lint
[28921] warn: config: 'uridnsbl_timeout' is obsolete, use 'rbl_timeout' instead at /usr/lib/perl5/site_perl/5.8.0/Mail/SpamAssassin/Plugin/URIDNSBL.pm line 398.
[28921] warn: config: warning: score set for non-existent rule PART_CID_STOCK_LESS
[28921] warn: config: warning: score set for non-existent rule FRT_OPPORTUN2
[28921] warn: config: warning: score set for non-existent rule HEADER_COUNT_SUBJECT
[28921] warn: config: warning: score set for non-existent rule FRT_XANAX1
[28921] warn: config: warning: score set for non-existent rule FRT_DOLLAR
[28921] warn: config: warning: score set for non-existent rule FRT_DIPLOMA
[28921] warn: config: warning: score set for non-existent rule BASE64_LENGTH_79_INF
[28921] warn: config: warning: score set for non-existent rule FRT_SOMA2
[28921] warn: config: warning: score set for non-existent rule TVD_STOCK1
[28921] warn: config: warning: score set for non-existent rule FRT_TODAY2
[28921] warn: config: warning: score set for non-existent rule TVD_FW_GRAPHIC_NAME_MID
[28921] warn: config: warning: score set for non-existent rule FRT_ESTABLISH2
[28921] warn: config: warning: score set for non-existent rule TVD_SPACE_RATIO
[28921] warn: config: warning: score set for non-existent rule TVD_FW_GRAPHIC_NAME_LONG
[28921] warn: config: warning: score set for non-existent rule FRT_OFFER2
[28921] warn: config: warning: score set for non-existent rule FRT_ADOBE2
[28921] warn: config: warning: score set for non-existent rule FRT_BIGGERMEM1
[28921] warn: config: warning: score set for non-existent rule TVD_FUZZY_SYMBOL
[28921] warn: config: warning: score set for non-existent rule FRT_XANAX2
[28921] warn: config: warning: score set for non-existent rule FRT_VALIUM1
[28921] warn: config: warning: score set for non-existent rule HTTPS_HTTP_MISMATCH
[28921] warn: config: warning: score set for non-existent rule FRT_DISCOUNT
[28921] warn: config: warning: score set for non-existent rule BASE64_LENGTH_78_79
[28921] warn: config: warning: score set for non-existent rule TVD_FUZZY_FINANCE
[28921] warn: config: warning: score set for non-existent rule TVD_FUZZY_MICROCAP
[28921] warn: config: warning: score set for non-existent rule FRT_SEXUAL
[28921] warn: config: warning: score set for non-existent rule FRT_****2
[28921] warn: config: warning: score set for non-existent rule FRT_MEETING
[28921] warn: config: warning: score set for non-existent rule FRT_GUARANTEE1
[28921] warn: config: warning: score set for non-existent rule FRT_INVESTOR
[28921] warn: config: warning: score set for non-existent rule FRT_VALIUM2
[28921] warn: config: warning: score set for non-existent rule FRT_PRICE
[28921] warn: config: warning: score set for non-existent rule FUZZY_MERIDIA
[28921] warn: config: warning: score set for non-existent rule HTML_IFRAME_SRC
[28921] warn: config: warning: score set for non-existent rule FRT_LEVITRA
[28921] warn: config: warning: score set for non-existent rule FRT_ROLEX
[28921] warn: config: warning: score set for non-existent rule FRT_STRONG2
[28921] warn: config: warning: score set for non-existent rule DNS_FROM_DOB
[28921] warn: config: warning: score set for non-existent rule FRT_WEIGHT2
[28921] warn: config: warning: score set for non-existent rule FRT_STRONG1
[28921] warn: config: warning: score set for non-existent rule TVD_FUZZY_DEGREE
[28921] warn: config: warning: score set for non-existent rule PART_CID_STOCK
[28921] warn: config: warning: score set for non-existent rule FRT_PENIS1
[28921] warn: config: warning: score set for non-existent rule FRT_SYMBOL
[28921] warn: config: warning: score set for non-existent rule TVD_FUZZY_PHARMACEUTICAL
[28921] warn: config: warning: score set for non-existent rule CTYPE_8SPACE_GIF
[28921] warn: config: warning: score set for non-existent rule TVD_FUZZY_FIXED_RATE
[28921] warn: config: warning: score set for non-existent rule URI_TRUNCATED
[28921] warn: config: warning: score set for non-existent rule FRT_REFINANCE1
[28921] warn: config: warning: score set for non-existent rule FRT_SOMA
check: no loaded plugin implements 'check_main': cannot scan! at /usr/lib/perl5/site_perl/5.8.0/Mail/SpamAssassin/PerMsgStatus.pm line 164.
[root@stargatesg1 spamassassin]#
 
My maillog file is getting huge volumes of logs (3 GB + per day - yes, Gigabytes) with this same basic entry:

Code:
May  9 10:45:36 server01 spamd[1102]: Malformed UTF-8 character (unexpected non-continuation byte 0x00, immediately after start byte 0xd1) in pattern match (m//) at /etc/mail/spamassassin/70_sare_adult.cf, rule SARE_OBFUPORNO, line 1. 
May  9 10:45:36 server01 spamd[1102]: Malformed UTF-8 character (unexpected non-continuation byte 0x00, immediately after start byte 0xce) in pattern match (m//) at /etc/mail/spamassassin/70_sare_adult.cf, rule SARE_OBFUPORNO, line 1. 
May  9 10:45:36 server01 spamd[1102]: Malformed UTF-8 character (unexpected non-continuation byte 0x00, immediately after start byte 0xcf) in pattern match (m//) at /etc/mail/spamassassin/70_sare_adult.cf, rule SARE_OBFUPORNO, line 1.

This started immediately after updating to 3.2.0. I have tried to re-update, reboot, etc...

Any ideas?
 
i had this as well, the new spamassassin is not compatible with your old spamasssin rules.

to fix it you have to update perl to newest version.
 
i had this as well, the new spamassassin is not compatible with your old spamasssin rules.

to fix it you have to update perl to newest version.
What's the best way to do that without breaking any modules?
 
Unless there is an RPM out there for your OS, then you may have to compile from source.
 
Well everyone, for those of us who have older CentOS 3.x servers, upgrading to SpamAssassin 3.2.0 which requires the use of Perl 5.8.8 is just not going to happen. When I upgraded to SpamAssassin 3.2.0 this past weekend there developed a memory leak that caused the server to come to a grinding halt ... TWICE.

To the best of my knowledge this was caused when SA 3.2.0 tried reading from rules from the 3.1.x tree but couldn't because it needs Perl 5.8.8 for that and not Perl 5.8.0. This lead me to a big search of whether there was any Perl 5.8.8 binaries out there (which there aren't) and whether I should compile from source. I asked a member of the CentOS dev team who suggested I do *not* compile perl from source into the OS as the risk of damaging the OS was high.

So for now, I'm back to SA 3.1.8 and looks like I'll have to sit there on that version for now until/unless someone makes a Perl 5.8.8 RPM for CentOS 3.
 
The revert back went fine. I edited the /usr/local/directadmin/scripts/spam.sh script to reflect version 3.1.8, saved it, ran ./spam.sh and let it recompile. I made sure my exim.conf file was in tact and ran 'service exim restart' command and all worked great.

Modem: how did you revert back to SA 3.1.8?
 
Going back to 3.1.8 fixed the issue. Apparently this is a known bug. Yesterday this bug caused my log files to fill up my tmp folder causing session errors, PHP errors, and clamAV shutdown (which disabled exim), so basically my server was down.

I HIGHLY recommend NOT installing 3.2.0 and wait until 3.2.1 is released in the next week or so.
 
Going back to 3.1.8 fixed the issue. Apparently this is a known bug. Yesterday this bug caused my log files to fill up my tmp folder causing session errors, PHP errors, and clamAV shutdown (which disabled exim), so basically my server was down.

I HIGHLY recommend NOT installing 3.2.0 and wait until 3.2.1 is released in the next week or so.
Update on debian without any issues..:)
 
I had to install HTML::parser 3.55 first (by hand - CPAN install didn't work). Then spam.sh proceeded without issues.

Running perl 5.8.0 on Centos 3.8 btw.
 
Back
Top