You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by ".rp" <pr...@afts.com> on 2008/03/24 19:04:42 UTC

update from 3.20 to 3.24 problem with local.cf

SA 3.20 was working okay, went for the 3.24 update. It installed , but upon restarting 
spamd I got error messages. I'd appreciate information on how to fix the local.cf file. 
Here is the log:
Mon Mar 24 10:56:02 2008 [22312] info: logger: removing stderr method
Mon Mar 24 10:56:09 2008 [22314] info: config: failed to parse line, skipping, in 
"/etc/mail/spamassassin/local.cf": rewrite_subject 1
Mon Mar 24 10:56:09 2008 [22314] info: config: failed to parse line, skipping, in 
"/etc/mail/spamassassin/local.cf": subject_tag [:]
Mon Mar 24 10:56:09 2008 [22314] info: config: failed to parse line, skipping, in 
"/etc/mail/spamassassin/local.cf": check_mx_delay 3
Mon Mar 24 10:56:09 2008 [22314] info: config: failed to parse line, skipping, in 
"/etc/mail/spamassassin/local.cf": report_header 1
Mon Mar 24 10:56:09 2008 [22314] info: config: failed to parse line, skipping, in 
"/etc/mail/spamassassin/local.cf": use_terse_report 1
Mon Mar 24 10:56:09 2008 [22314] info: config: failed to parse line, skipping, in 
"/etc/mail/spamassassin/local.cf": detailed_phrase_score 0
Mon Mar 24 10:56:09 2008 [22314] info: config: failed to parse line, skipping, in 
"/etc/mail/spamassassin/local.cf": spam_level_stars 0
Mon Mar 24 10:56:09 2008 [22314] info: config: score: the non-numeric score (.75) is 
not valid, a numeric score is required
Mon Mar 24 10:56:09 2008 [22314] info: config: SpamAssassin failed to parse line, 
"EXTRA_MPART_TYPE .75" is not valid for "score", skipping: score 
EXTRA_MPART_TYPE .75
Mon Mar 24 10:56:09 2008 [22314] info: config: score: the non-numeric score (.8) is 
not valid, a numeric score is required
Mon Mar 24 10:56:09 2008 [22314] info: config: SpamAssassin failed to parse line, 
"FH_HOST_ALMOST_IP .8" is not valid for "score", skipping: score 
FH_HOST_ALMOST_IP .8
Mon Mar 24 10:56:09 2008 [22314] info: config: score: requires a symbolic rule name 
and 1 or 4 scores
Mon Mar 24 10:56:09 2008 [22314] info: config: SpamAssassin failed to parse line, no 
value provided for "score", skipping: score MIME_QP_LONG_LINE RAW .9
Mon Mar 24 10:56:09 2008 [22314] info: config: failed to parse line, skipping, in 
"/etc/mail/spamassassin/local.cf": defang_mime 0
Mon Mar 24 10:56:09 2008 [22314] info: config: failed to parse line, skipping, in 
"/etc/mail/spamassassin/local.cf": razor_timeout 1
Mon Mar 24 10:56:09 2008 [22314] info: config: failed to parse line, skipping, in 
"/etc/mail/spamassassin/local.cf": dcc_timeout 1
Mon Mar 24 10:56:09 2008 [22314] info: config: failed to parse line, skipping, in 
"/etc/mail/spamassassin/local.cf": pyzor_add_header 0
Mon Mar 24 10:56:19 2008 [22314] info: spamd: server started on port 783/tcp 
(running version 3.2.4)
Mon Mar 24 10:56:19 2008 [22314] info: spamd: server pid: 22314
Mon Mar 24 10:56:19 2008 [22314] info: spamd: server successfully spawned child 
process, pid 22331
Mon Mar 24 10:56:19 2008 [22314] info: spamd: server successfully spawned child 
process, pid 22332
Mon Mar 24 10:56:19 2008 [22314] info: prefork: child states: II

here is the /etc/mail/spamassassin/local.cf:
required_hits 3.91
rewrite_subject 1
subject_tag [:]
check_mx_delay 3
skip_rbl_checks 1
fold_headers 0
dns_available no
report_header 1
use_terse_report 1
detailed_phrase_score 0
spam_level_stars 0
use_bayes 0
report_safe     0

score SUBJ_ALL_CAPS 0
score SUBJ_HAS_SPACES 2.5
score USERNAME_IN_SUBJECT 3.01
score DATE_IN_FUTURE_48_96 1
score DATE_IN_FUTURE_12_24 0
score DATE_IN_FUTURE_24_48 0
score DATE_MISSING 0.75
score DATE_IN_FUTURE_06_12 0
score INVALID_DATE 0
score DATE_IN_PAST_96_XX 1
score DATE_IN_PAST_12_24 0
score DATE_IN_PAST_06_12 0
score DATE_IN_FUTURE_96_XX 0
score DATE_IN_PAST_03_06 0
score DATE_IN_FUTURE_03_06 0
score DATE_IN_PAST_24_48 0.5
score DATE_IN_PAST_48_96 1
score DATE_WARNING 1
score NO_REAL_NAME 0
score SUBJECT_HAS_DATE -1.3
score FORGED_JUNO_RCVD 0.5
score SEARCH_ENGINE_PROM 1.1
score FORGED_OUTLOOK_TAGS 0.5
score FORGED_MUA_OUTLOOK 0.7
score ADVERT_CODE -0.1
score X_PRIORITY_HIGH 0.1
score FROM_NO_LOWER 0.9
score HTML_IMAGE_ONLY_16 2.1
score EXTRA_MPART_TYPE .75
score FH_HOST_EQ_D_D_D_D 1.1
score US_DOLLARS_3 0.7
score FH_HOST_ALMOST_IP .8
score MIME_QP_LONG_LINE RAW     .9

defang_mime 0
allow_user_rules 1
header FROM_POSTOFFICE From =~ /PostalStore/
score FROM_POSTOFFICE -0.3
razor_timeout 1
dcc_timeout 1
pyzor_timeout 1
pyzor_add_header 0




Re: update from 3.20 to 3.24 problem with local.cf

Posted by Michael Scheidell <sc...@secnap.net>.
You have (at leqase) some OLD 2.x stuff in that local.cf
http://readlist.com/lists/incubator.apache.org/spamassassin-users/0/4503.htm
l

Also, score have to be like '0.79'  not '.79'.

Google for each option that failed.  I think you will find that they are OLD
2.0 options, for the most part.

Also, dcc.  Make sure you uncomment #DCC in the *.pre files unless you are a
commercial provider (it is commented out by default due to the dual
license). 


-- 
Michael Scheidell, CTO
>|SECNAP Network Security
Winner 2008 Network Products Guide Hot Companies
FreeBsd SpamAssassin Ports maintainer
Charter member, ICSA labs anti-spam consortium

> From: ".rp" <pr...@afts.com>
> Date: Mon, 24 Mar 2008 11:04:42 -0700
> To: spamAssassin Users <us...@spamassassin.apache.org>
> Subject: update from 3.20 to 3.24 problem with local.cf
> 
> check_mx_delay

_________________________________________________________________________
This email has been scanned and certified safe by SpammerTrap(tm). 
For Information please see http://www.spammertrap.com
_________________________________________________________________________