On Wed, 18 Apr 2007, Bill McCormick wrote:
Duane Hill wrote:
On Wed, 18 Apr 2007, jpff wrote:
Well the SARE_* rules come from the SARE rulesets over at
rulesemporium.com, which sa-update does NOT update. sa-update, by
default, updates the official ruleset only.
Not true; I update the SA
Duane Hill wrote:
On Wed, 18 Apr 2007, jpff wrote:
Well the SARE_* rules come from the SARE rulesets over at
rulesemporium.com, which sa-update does NOT update. sa-update, by
default, updates the official ruleset only.
Not true; I update the SARE runs using sa-update
So you are saying
On Wed, 18 Apr 2007, jpff wrote:
Well the SARE_* rules come from the SARE rulesets over at
rulesemporium.com, which sa-update does NOT update. sa-update, by
default, updates the official ruleset only.
Not true; I update the SARE runs using sa-update
So you are saying just by typing 'sa-upd
> Well the SARE_* rules come from the SARE rulesets over at
> rulesemporium.com, which sa-update does NOT update. sa-update, by
> default, updates the official ruleset only.
Not true; I update the SARE runs using sa-update
> That said, they're only warnings. You might want to go check if some of
jpff wrote:
> To add to the apparent Perl problems I have with deleting non-existent
> memory and spamassassin totally stopping all mail delivery, when I
> start spamassassin I see the messages
>
> Apr 15 11:03:48 snout spamd[6569]: rules: meta test SARE_SPEC_PROLEO_M2a has
> dependency 'MIME_QP_L
To add to the apparent Perl problems I have with deleting non-existent
memory and spamassassin totally stopping all mail delivery, when I
start spamassassin I see the messages
Apr 15 11:03:48 snout spamd[6569]: rules: meta test SARE_SPEC_PROLEO_M2a has
dependency 'MIME_QP_LONG_LINE' with a zero s
