You'll love this..
My nightly sa-update cron ran last night and upgraded my "modified"
rules (was version 916621) to a newer version (version 917420). This, of
course, undid my changes. And equally surprising, --lint passed.
I looked at the diffs and sure enough, the same lines were back (number
of other changes too). Not sure why the gremlins were banished.
Interesting mystery.
-lee
Lee Dilkie wrote:
> Final update folks, sorry for the noise if it's bothersome...
>
> commented out the three offending lines in 72_active.cf and --lint
> passed and I'm back up and running.
>
> No idea what the issue is, those lines looked fine to me. I'm running
> perl 5.8.9, could that be an issue?
>
> -lee
>
> details: ##lee is my handiwork
>
> ifplugin Mail::SpamAssassin::Plugin::MIMEHeader
> mimeheader __TVD_FW_GRAPHIC_ID1 Content-Id =~
> /<[0-9a-f]{12}(?:\$[0-9a-f]{8}){2}\@/
> endif
>
> ifplugin Mail::SpamAssassin::Plugin::MIMEEval
> ##lee mimeheader __TVD_MIME_ATT_AOPDF Content-Type =~
> /^application\/octet-stream.*\.pdf/i
> endif
>
> ifplugin Mail::SpamAssassin::Plugin::MIMEEval
> ##lee mimeheader __TVD_MIME_ATT_AP Content-Type =~ /^application\/pdf/i
> endif
>
> ifplugin Mail::SpamAssassin::Plugin::MIMEEval
> ##lee mimeheader __TVD_MIME_ATT_TP Content-Type =~ /^text\/plain/i
> endif
>
> ifplugin Mail::SpamAssassin::Plugin::MIMEHeader
> mimeheader __TVD_OUTLOOK_IMG Content-Id =~ /<image\d+\.(?:gif|jpe?g|png)\@/
> endif
>
>
>
> Lee Dilkie wrote:
>
>> progress report.. commented out the place where the lint results were
>> checked and rules got installed.
>>
>> looking at 72_active.cf I see a number of lines ending in CR (^M). Is
>> this intentional?
>>
>> ie.
>>
>> header __SUBJ_3DIGIT Subject =~ /\b\d{3}[^0-9]/^M
>>
>> header __SUBJ_APPROVE Subject =~ /Approve/i^M
>>
>> header __SUBJ_RE Subject =~ /^R[eE]:/^M
>>
>> -lee
>>
>>
>> Lee Dilkie wrote:
>>
>>
>>> no joy.
>>>
>>> doesn't look like the ports version of SA comes with any stock rules
>>> (nothing obvious in the ports dir tree, the work/ directory had en empty
>>> 72_active.cf file)... I deinstalled and then installed and it all went
>>> well but it tells me to run sa-update to get the rules, and that's my
>>> problem
>>>
>>> You may wish to run sa-update now to obtain the latest rules.
>>>
>>> NOTE: FREEBSD users: If you are updating from a version prior to 3.20.
>>> sa-update now places state files in /var/db/spamassassin and not
>>> /var/lib/spamassassin. This is to be consistant with Freebsd file
>>> directory conventions.
>>>
>>> If you run sa-compile, you will notice that files are in
>>> /var/db/spamassassin/compiled/<perlversion>/<version> instead of
>>> /var/db/spamassassin/compiled/<version>.
>>> No attempts have been made to move old versions over. You must recompile.
>>>
>>> ===> Installing rc.d startup script(s)
>>> ===> Compressing manual pages for p5-Mail-SpamAssassin-3.3.0_3
>>> ===> Running ldconfig
>>> /sbin/ldconfig -m /usr/local/lib
>>> ===> Registering installation for p5-Mail-SpamAssassin-3.3.0_3
>>>
>>> r...@spock: /usr/ports/mail/p5-Mail-SpamAssassin
>>> $ sa-update
>>> config: failed to parse line, skipping, in
>>> "/tmp/.spamassassin92852PBQ5Yktmp/72_active.cf": mimeheader
>>> __TVD_MIME_ATT_AOPDF Content-Type =~ /^application\/octet-stream.*\.pdf/i
>>> config: failed to parse line, skipping, in
>>> "/tmp/.spamassassin92852PBQ5Yktmp/72_active.cf": mimeheader
>>> __TVD_MIME_ATT_AP Content-Type =~ /^application\/pdf/i
>>> config: failed to parse line, skipping, in
>>> "/tmp/.spamassassin92852PBQ5Yktmp/72_active.cf": mimeheader
>>> __TVD_MIME_ATT_TP Content-Type =~ /^text\/plain/i
>>> channel: lint check of update failed, channel failed
>>>
>>>
>>> So is there *any* way for me to get this ruleset and put it on my server
>>> and edit out the offending lines in 72_active.cf?? Is there an archive I
>>> can download? (I'm thinking of modifying sa-update to comment-out where
>>> it removes the tmp files)
>>>
>>> -lee
>>>
>>> Karsten Bräckelmann wrote:
>>>
>>>
>>>
>>>> On Mon, 2010-03-01 at 06:45 -0500, Lee Dilkie wrote:
>>>>
>>>>
>>>>
>>>>
>>>>> Karsten Bräckelmann wrote:
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>>
>>>>>> 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.
>>>>>
>>>>>
>>>>>
>>>>>
>>>> man spamassassin
>>>>
>>>> See the section Configuration Files. The first path mentioned for
>>>> Default Configuration Data should be the sa-update one. SA version is
>>>> embedded in that path, inside /var/lib here, IIRC /var/db or something
>>>> on FreeBSD.
>>>>
>>>> The last one in that block of paths should be where SA expects the stock
>>>> rules. The first existing one from that list wins, anything else will be
>>>> ignored.
>>>>
>>>> spamassassin -D can help in identifying bad rule sets being picked up,
>>>> and where SA ultimately looks for the cf files.
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>> 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).
>>>>>
>>>>>
>>>>>
>>>>>
>>>> Drop the bad update first, and revert to stock. Re-install it from
>>>> ports, if need be.
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>
>>
>
>
--
Fuelly <http://www.fuelly.com/driver/dilkie/golf>
