Karsten Bräckelmann wrote:
> On Sun, 2010-02-28 at 18:44 -0500, Lee Dilkie wrote:
>
>> For what ever reason, my sa-update to 3.30 has buggered itself. In my
>> efforts to debug it's now at the situation that SA has no rules to run
>> and I'm getting swamped.
>>
>
> The first sentence is seriously confusing. You can not "sa-update to
> 3.3.0". sa-update only updates the rules, for the already installed
> version.
>
Yeah, sorry about that... As I've discovered, it's all tied to the
version of SA and 3.2 rules won't run with 3.3 SA.
>
>
>> How, if it's possible, can I tell SA and sa-update to use the 3.2
>> version of the ruleset? Simply deleting the tree and sa-compiling did
>> not work. SA is still looking for 3.3 rules and as it finds none, is
>> letting everything through.
>>
>
> You cannot really and reliably make SA 3.3 use 3.2 rules.
>
agreed ;)
> Anyway, what comes to mind: Did you run sa-update after the upgrade to
> 3.3.0 at all? If not, did you install the rules tarball alongside SA?
>
I was originally running the 3.3 rules and that was fine, and as far as
I know, I did even run sa-upgrade (can't tell you if it upgraded the
rules over the base ones) but it's the latest sa-update that pulled in
newer rules that didn't link. And it's my monkeying around, deleting
rules directories, that has left me without rules from updates
spamassassin_org. And boy! do they block a lot of spam or what! ;)
> How did you upgrade? Any chance both versions ended up living on your
> system?
>
> Running 3.3.0 with a broken sa-update for whatever reason, can be cured
> by removing the entire update dir, and installing the plain, stock 3.3.0
> rules tarball, if not already done.
>
I'm on freebsd, I'm going to try and find out where that's stored, it's
likely in the ports tree somewhere.
thanks for the help..
Unfortunately, my update to the latest ruleset fails lint... as I said
in an earlier email...
config: failed to parse line, skipping, in
"/tmp/.spamassassin545130JflrRtmp/72_active.cf": mimeheader
__TVD_MIME_ATT_AOPDF Content-Type =~ /^application\/octet-stream.*\.pdf/i
config: failed to parse line, skipping, in
"/tmp/.spamassassin545130JflrRtmp/72_active.cf": mimeheader __TVD_MIME_ATT_AP
Content-Type =~ /^application\/pdf/i
config: failed to parse line, skipping, in
"/tmp/.spamassassin545130JflrRtmp/72_active.cf": mimeheader __TVD_MIME_ATT_TP
Content-Type =~ /^text\/plain/i
Is there any way that I can force the system to download the ruleset so
I can comment out the offending lines and carry on? (I'd at least like
to see what they are, and why it doesn't parse, maybe it's something in
my config).
-lee
>
>
--
Fuelly <http://www.fuelly.com/driver/dilkie/golf>
