On 1/1/07, Shaun T. Erickson <[EMAIL PROTECTED]> wrote:
What am I doing wrong?
I just ran amavisd with the debug-sa option, and as near as I can
tell, it appears to only be using the original ruleset - and doesn't
even seem to know that I am pulling new rules down with sa-update.
I must have missed some important configuration step somewhere ...
--
-ste
You must be running SA 3.1.4 or older and amavisd-new 2.4.2 or older. This
issue was resolved in both 3.1.5 and 2.4.3 so upgrading to a newer version
of either would solve the problem. You can also patch older versions of
amavisd-new by adding LOCAL_STATE_DIR => '/var/lib', in the location shown
here:
--- amavisd~ Mon Apr 3 16:32:34 2006
+++ amavisd Thu Aug 3 15:13:19 2006
@@ -14562,2 +14562,3 @@
stop_at_threshold => 0,
+ LOCAL_STATE_DIR => '/var/lib',
# DEF_RULES_DIR => '/usr/local/share/spamassassin',
From amavisd-new release notes:
- add "LOCAL_STATE_DIR => '/var/lib'" to the SA object initialization
for versions of SA 3.1.4 or older, so that SpamAssassin would see
additional rules provided by sa-update and placed to its default location;
the SA 3.1.5 provides its own default so this becomes unnecessary;
Gary V
_________________________________________________________________
Find sales, coupons, and free shipping, all in one place! MSN Shopping
Sales & Deals
http://shopping.msn.com/content/shp/?ctid=198,ptnrid=176,ptnrdata=200639
