On Sat, 03 Feb 2007 19:27:44 +0100, David Obando <[EMAIL PROTECTED]> wrote:
>Nigel Frankcom schrieb am 03.02.2007 19:23: >> On Sat, 03 Feb 2007 19:13:19 +0100, David Obando <[EMAIL PROTECTED]> >> wrote: >> >> >>> Nigel Frankcom schrieb am 03.02.2007 18:53: >>> >>>> On Sat, 03 Feb 2007 18:42:51 +0100, David Obando <[EMAIL PROTECTED]> >>>> wrote: >>>> >>>> >>>> >>>>> Dear all, >>>>> >>>>> I'm using SA 3.1.7 on a Debian Etch system. My config is in >>>>> /etc/spamassassin, the default rules that came with SA are in >>>>> /usr/share/spamassassin/, and the rules I get via sa-update-channels are >>>>> in /var/lib/spamassassin/3.001007. It all worked fine. >>>>> For a couple of days now the rules in /var/lib/spamassassin/3.001007 >>>>> aren't used anymore. When doing a "sa-update -D" or "spamassassin --lint >>>>> -D" I can see these rules are referenced but they are simply not used >>>>> when mail checks are made. >>>>> >>>>> Could anyone give me a clue how I could activate them again? >>>>> >>>>> Thanks and regards, >>>>> David >>>>> >>>>> >>>> How have you established the rules in 3.001 etc. are not being used? >>>> >>>> Can I check SA is in /etc/spamassassin or /etc/mail/spamassassin? is >>>> that a Debian thing? >>>> >>>> KR >>>> >>>> Nigel >>>> >>>> >>> When I look in my syslog I can see which rules "hit" a mail. A couple of >>> days before *no* rules have been used anymore. >>> I then tried to include the rules by putting: >>> include /usr/share/spamassassin/10_misc.cf >>> etc... >>> in my local.cf. For /usr/share/spamassassin this works, for >>> /var/lib/spamassassin/3.001007 it does not. >>> >>> There is a Symlink /etc/mail/spamassassin --> /etc/spamassassin by Debian. >>> >>> Regards, >>> David >>> >> >> Are any of the rules in your primary spamassassin directory firing >> (/etc/spamassassin)? >> >> Are you getting any error messages at all? (I'm shooting in the dark >> here so please excuse stupid questions). >> >Yes, all rules in /etc/spamassassin do work and no, I don't get any >error messages... Much as I hate to admit it, I don't really have a clue what may be awry. If it worked OK initially the natural assumption is that something changed in the interim, permissions perhaps? If SA is reading rules ok from the main directory I don't see why it should ignore the 3.00* dir unless it doesn't know about it or can't access it. Hopefully one of the more knowledgeable list members can offer some insight. Kind regards Nigel
