Weblog entry #4 for muondude

Broken Spamassassin install/config - how to fix?
Posted by muondude on Sat 16 Sep 2006 at 22:00
Tags: none.
I was looking at my procmail log file and noticed some spamassassin error messages. I did a little google search and I may have a broken install.

I am running Debian 3.1 which was an upgrade from Debian 2.

I've include some other information below.

the last part of my .procmail file looks like:


# removed -P at EOL
:0fw
| spamassassin

:0:
* X-Spam-Status: yes
spam

# deliver to local maildir mailbox
:0:
/home/sgasster/Maildir/


***
I'm wondering about how to fix this.
Is it simply a matter of telling spamassassin to look in the correct
config directory? I wasn't sure how to do this or where it should go?
In the spamassassin command in the .procmail file should I point to
the /usr/share/spamassassin directory, since it may be defaulting to
the "old - incorrect" /etc/spamassassin directory?

***


> spamassassin -VD
SpamAssassin version 3.0.3
running on Perl version 5.8.4

In /etc I have:

ll /etc/mail
total 0
lrwxrwxrwx 1 root root 15 Jun 14 22:08 spamassassin -> ../spamassassin

ls /etc/spamassassin/
10_misc.cf 25_body_tests_es.cf 30_text_pl.cf 65_debian.cf local.cf.dpkg-old
20_body_tests.cf 25_body_tests_pl.cf 40_spam_phrases.cf init.pre user_prefs.template
20_head_tests.cf 25_head_tests_pl.cf 50_scores.cf local.cf
20_uri_tests.cf 30_text_es.cf 60_whitelist.cf local.cf.bck

> whereis spamassassin
spamassassin: /usr/bin/spamassassin /etc/spamassassin /usr/share/spamassassin /usr/share/man/man1/spamassassin.1p.gz




> ls /usr/share/spamassassin/
10_misc.cf 20_fake_helo_tests.cf 20_ratware.cf 25_uribl.cf 60_whitelist.cf
20_anti_ratware.cf 20_head_tests.cf 20_uri_tests.cf 30_text_de.cf 65_debian.cf
20_body_tests.cf 20_html_tests.cf 23_bayes.cf 30_text_fr.cf languages
20_compensate.cf 20_meta_tests.cf 25_body_tests_es.cf 30_text_nl.cf triplets.txt
20_dnsbl_tests.cf 20_phrases.cf 25_hashcash.cf 30_text_pl.cf user_prefs.template
20_drugs.cf 20_porn.cf 25_spf.cf 50_scores.cf


*** so it seems like I have two sets of config files!

A sample of the procmail logs looks like:

...snip...
Failed to run LINES_OF_YELLING_2 SpamAssassin test, skipping:
(Can't locate object method "check_for_num_yelling_lines" via package "Mail::SpamAssassin::PerMsgStatus" at /usr/share/perl5/Mail/SpamAssassin/PerMsgStatus.pm line 2340.
)
Failed to run BASE64_ENC_TEXT SpamAssassin test, skipping:
(Can't locate object method "check_for_base64_enc_text" via package "Mail::SpamAssassin::PerMsgStatus" at /usr/share/perl5/Mail/SpamAssassin/PerMsgStatus.pm line 2340.
)
Failed to run RAZOR_CHECK SpamAssassin test, skipping:
(Can't locate object method "check_razor" via package "Mail::SpamAssassin::PerMsgStatus" at /usr/share/perl5/Mail/SpamAssassin/PerMsgStatus.pm line 2340.
)
procmail: [28536] Sat Sep 16 13:27:43 2006
procmail: Match on "X-Spam-Status: yes"
procmail: Locking "spam.lock"
procmail: Assigning "LASTFOLDER=spam"
procmail: Opening "spam"
procmail: Acquiring kernel-lock
procmail: Unlocking "spam.lock"
...snip...

TAI...

 

Comments on this Entry

Posted by MERVERNATOR (216.6.xx.xx) on Wed 27 Sep 2006 at 03:06
[ Send Message ]
I had this issues when using the SA from Debian and then upgrading to the newer one manually.

the difference was that spamd from Debian was in /usr/sbin/
and the upgrade put its files in /usr/bin/

and the rules from Debian were in /usr/share/spamassassin/
but from the update were in /usr/local/share/spamassassin/

I just coppied spamd from /usr/bin/ to /usr/sbin
and all the rule files from /usr/local/share/spamassassin/ to /usr/share/spamassassin/

once I did this and restarted it, everything was fine. Id still like to figure out how to tell it to install in the original directories durring the make process.. but this works for now.

[ Parent | Reply to this comment ]

User Login

Username:

Password:

[ Advanced Login ]

Register Account

Quick Site Search