> using the DAG site and rpm -U, I updated spamassassin and
> spamassissin-tools to
> 3.1.7-1
> Things don't look so good. Here is what happened when I
> restarted spamd
>
>  spamd[26917]: spamd: server killed by SIGTERM, shutting down
>  spamd[27082]: persistent_udp: no such method at
> /usr/lib/perl5/vendor_perl/5.8.0/Mail/SpamAssassin/DnsResolver
> .pm line 99
>  spamd[27082]: logger: removing stderr method
>  spamd[27084]: config: failed to parse line, skipping:
> rewrite_subject 1
>  spamd[27084]: config: failed to parse line, skipping: subject_tag [:]
>  spamd[27084]: config: failed to parse line, skipping:
> check_mx_delay 3
>  spamd[27084]: config: failed to parse line, skipping: report_header 1
>  spamd[27084]: config: failed to parse line, skipping:
> use_terse_report 1
>  spamd[27084]: config: failed to parse line, skipping:
> detailed_phrase_score 0
>  spamd[27084]: config: failed to parse line, skipping:
> spam_level_stars 0
>  spamd[27084]: config: failed to parse line, skipping: defang_mime 0
>  spamd[27084]: config: score: the non-numeric score (-.3) is
> not valid, a numeric
> score is required
>  spamd[27084]: config: SpamAssassin failed to parse line,
> "FROM_POSTOFFICE -
> .3" is not valid for "score", skipping: score FROM_POSTOFFICE -.3
>  spamd[27084]: config: failed to parse line, skipping: razor_timeout 1
>  spamd[27084]: config: failed to parse line, skipping: dcc_timeout 1
>  spamd[27084]: config: failed to parse line, skipping:
> pyzor_add_header 0
>  spamd[27084]: rules: meta test DIGEST_MULTIPLE has undefined
> dependency
> 'RAZOR2_CHECK'
>  spamd[27084]: rules: meta test DIGEST_MULTIPLE has undefined
> dependency
> 'DCC_CHECK'
>  spamd[27084]: rules: meta test DRUGS_ERECTILE has undefined
> dependency
> '__DRUGS_ERECTILE7'
>  spamd[27084]: rules: meta test VIRUS_WARNING_DOOM_BNC has undefined
> dependency 'VIRUS_WARNING_MYDOOM4'
>  spamd[27084]: rules: meta test SARE_OBFU_CIALIS has
> undefined dependency
> 'SARE_OBFU_CIALIS2'
>  spamd[27084]: spamd: server started on port 783/tcp (running
> version 3.1.7)
>  spamd[27084]: spamd: server pid: 27084
>  spamd[27084]: spamd: server successfully spawned child
> process, pid 27091
>  spamd[27084]: spamd: server successfully spawned child
> process, pid 27092
>  spamd[27084]: prefork: child states: IS
>  spamd[27084]: prefork: child states: II
>
> I don't see anything mentioned about this in
>  /usr/share/doc/spamassassin-3.1.7/UPGRADE

The "failed to parse line" warnings are all deprecated settings IIRC.
Check the documentation for current equivalents. I would be surprised if
3.1.1 didn't note those as well.

The score from "FROM_POSTOFFICE" should be -0.3 instead of -.3. Is that
in your local.cf?

The undefined dependency "info" messages are new in a recent version
(sorry-- don't remember which). However, the end result is the same as
before as far as processing goes. It's just the undefined dependencies
are actually noted somewhere now where they weren't before. If you
develop your own meta rules, having this is very helpful. For stardard
or other 3rd-party rules, it's just annoying.

Is your Net::DNS up-to-date per the release notes?

HTH,
Bret



Reply via email to