I am using sa-update for the stock rules. I run:

sa-update -D --channelfile /etc/mail/spamassassin/sa-update-channels.txt
--gpgkey 856AA88A

where sa-update-channels.txt contains:

updates.spamassassin.org
70_sare_stocks.cf.sare.sa-update.dostech.net
70_sare_genlsubj0.cf.sare.sa-update.dostech.net
70_sare_html0.cf.sare.sa-update.dostech.net
70_sare_html1.cf.sare.sa-update.dostech.net
70_sare_header0.cf.sare.sa-update.dostech.net
70_sare_header1.cf.sare.sa-update.dostech.net
70_sare_header2.cf.sare.sa-update.dostech.net
72_sare_bml_post25x.cf.sare.sa-update.dostech.net
70_sare_spoof.cf.sare.sa-update.dostech.net
70_sare_oem.cf.sare.sa-update.dostech.net
70_sare_obfu0.cf.sare.sa-update.dostech.net
70_sare_obfu1.cf.sare.sa-update.dostech.net
70_sare_obfu2.cf.sare.sa-update.dostech.net



Karsten Bräckelmann wrote:

> > On Tue, 2008-08-26 at 00:34 -0400, Munroe Sollog wrote:
> >
>
>> >> I'm not quite sure I understand what is happening here:
>> >>
>> >> http://www.pastebin.ca/1184943
>> >>
>> >> it looks like the message is triggering rules but in the end it is
>> >> getting '0' points
>> >>
>>
> >
> > See the very last two lines. They mention the rules hit. In fact, there
> > are no (regular) rules hit at all, but subtests only.
> >
> >
> >
>
>> >> dbg: config: read file /var/lib/spamassassin/3.002005/70_sare_genlsubj0_cf_sare_sa-update_dostech_net.cf
>> >>
>>
> >
> > Skimming through the debug output it looks like you manually put these
> > cf files there. That's the dir for sa-update to keep the "channels" (a
> > directory per rule update source). However, keeping the cf files there
> > rather than channels shouldn't be the problem.
> >
> > The problem is, that once that dir exists, SA expects to find all rules
> > underneath that directory.
> >
> > That effectively means, that SA on your machine knows no rules but the
> > SARE ones you put there manually. You can see that for yourself in your
> > output, where no stock rule files are read at all.
> >
> > (a) If you just want to add some SARE rules, /etc/mail/spamassassin is
> > the dir to put them.
> > (b) And if you use sa-update for a third-party channel, be sure to use
> > sa-update for the stock rules as well. [1]
> >
> > Now why do I write email, let alone public email, before I got my
> > coffee?
> >
> > guenther
> >
> >
> > [1] I believe this is documented somewhere. Alas, I can't find it...
> >
> >
>

Munroe Sollog
Systems Engineer
Digirati Consulting, Inc
sollog@digiraticonsulting.com




Karsten Bräckelmann wrote:
> On Tue, 2008-08-26 at 00:34 -0400, Munroe Sollog wrote:
>
>> I'm not quite sure I understand what is happening here:
>>
>> http://www.pastebin.ca/1184943
>>
>> it looks like the message is triggering rules but in the end it is
>> getting '0' points
>>
>
> See the very last two lines. They mention the rules hit. In fact, there
> are no (regular) rules hit at all, but subtests only.
>
>
>
>> dbg: config: read file /var/lib/spamassassin/3.002005/70_sare_genlsubj0_cf_sare_sa-update_dostech_net.cf
>>
>
> Skimming through the debug output it looks like you manually put these
> cf files there. That's the dir for sa-update to keep the "channels" (a
> directory per rule update source). However, keeping the cf files there
> rather than channels shouldn't be the problem.
>
> The problem is, that once that dir exists, SA expects to find all rules
> underneath that directory.
>
> That effectively means, that SA on your machine knows no rules but the
> SARE ones you put there manually. You can see that for yourself in your
> output, where no stock rule files are read at all.
>
> (a) If you just want to add some SARE rules, /etc/mail/spamassassin is
> the dir to put them.
> (b) And if you use sa-update for a third-party channel, be sure to use
> sa-update for the stock rules as well. [1]
>
> Now why do I write email, let alone public email, before I got my
> coffee?
>
> guenther
>
>
> [1] I believe this is documented somewhere. Alas, I can't find it...
>
>