In the past I asked this question, but I was told that it was because
of my own rules. I never defined my own rules, So I try the question
again.
I have the following script to update SpamAssassin:
#!/usr/bin/env bash
declare -r GREP_REGEX='not installed\|warning'
declare -r
sa-update should have picked up the mailspike rules. I suppose
you did something to remove updates_spamassassin_org/20_mailspike.cf.
And then you did nothing to the updates_spamassassin_org/72_scores.cf
scores file to remove scores for mailspike.
If you wanted mailspike out of there the better
On 12/26/2012 10:55 AM, Cecil Westerhof wrote:
Dec 26 03:04:13.110 [17074] dbg: config: warning: score set for
non-existent rule RCVD_IN_MSPIKE_H4
Dec 26 03:04:13.111 [17074] dbg: config: warning: score set for
non-existent rule RCVD_IN_MSPIKE_WL
Dec 26 03:04:13.111 [17074] dbg:
Op woensdag 26 dec 2012 17:17 CET schreef j...@earthlink.net:
sa-update should have picked up the mailspike rules. I suppose you
did something to remove updates_spamassassin_org/20_mailspike.cf.
And then you did nothing to the
updates_spamassassin_org/72_scores.cf scores file to remove scores
On 12/26/2012 3:54 PM, Cecil Westerhof wrote:
Op woensdag 26 dec 2012 21:22 CET schreef Kevin A. McGrail:
These errors relate to the fact that those rules are encapsulated
with a version check that is likely above your version.
They can be safely ignored.
In my mailspike I see:
#
Op woensdag 26 dec 2012 23:12 CET schreef Kevin A. McGrail:
On 12/26/2012 3:54 PM, Cecil Westerhof wrote:
Op woensdag 26 dec 2012 21:22 CET schreef Kevin A. McGrail:
These errors relate to the fact that those rules are encapsulated
with a version check that is likely above your version.
