On Tue, 2009-02-24 at 12:55 +0100, Oliver Schinagl wrote: > Hmm, I thought you could specify several channels with sa-update. > > This is my current update line: > sa-update --allowplugins --gpgkey xxxxxxxxxxxxxxxxxxxxxxxxx --channel > saupdates.openprotect.com --channel updates.spamassasin.org > > and now that I paste it ... I see it ... spamassassin should be with > double S. BTW do I need that gpgkey line there? It seems to check for > updates just fine without it (I did run sa-update --import <keyfile>)? > > But It states there's no updates on spamassassin channel. Which makes a > little sense, as it's a fresh install not all rules should be needing > updating (in theory).
I guess that's because you ran sa-update correctly at least once since your OP and this "no updates" response. Your attached debug output supports this. The missing stuff clearly is there now. > [8027] dbg: config: using "/var/lib/spamassassin/3.002005" for sys rules pre > files > [8027] dbg: config: read file > /var/lib/spamassassin/3.002005/saupdates_openprotect_com.pre > [8027] dbg: config: using "/var/lib/spamassassin/3.002005" for default rules > dir > [8027] dbg: config: read file > /var/lib/spamassassin/3.002005/saupdates_openprotect_com.cf > [8027] dbg: config: read file > /var/lib/spamassassin/3.002005/updates_spamassassin_org.cf > Anyway I did the same check using the > sample-spam.txt and yes, I see more rules being used (from the updated > rules obviously) but it's still not checking the default rules in > /usr/share/spamassasin/. Whether that needs to be a problem, I don't Yup, SA won't use that dir, if the one above (created by sa-update) exists. This is exactly your original problem -- SA using the updates dir, cause it exists and was populated with the SARE rules, but no stock rules. > know. I can only think of rules now not being used if they haven't been > updated yet. Also the updates SA rules are being done after the SARE > ones? I'd figure 70 be higher then 10 - 60 .. I hope it won't matter. sa-update updates all rules -- in fact, it pretty much pulls the entire stock rules, containing the latest (stable) changes pushed to the update channel. It is not a diff. The order of specifying the channels or running the updates (once the stock rules *are* updated, mind you) is irrelevant. That's no problem. > I attached the output this time as it's quite a lot to go through. But > again the 'score' of 0 on everything: Talking about your incoming mail? Are you using spamd? Did you restart it after running sa-update? In order to pick up the updated rules (if any), spamd needs to be restarted whenever updates have been retrieved. You can find more about this and how to automatically restart spamd only if there are updates documented in the wiki: http://wiki.apache.org/spamassassin/RuleUpdates > It only gets 1000 points for the GTUBE rule; so atleast that's working ... Huh? No, it triggers more than that. :) Seems to work just fine, now. > X-Spam-Status: Yes, score=1002.7 required=5.0 tests=AWL,BAYES_40,GTUBE, > NO_RECEIVED,NO_RELAYS,PYZOR_CHECK autolearn=no version=3.2.5 -- char *t="\10pse\0r\0dtu...@ghno\x4e\xc8\x79\xf4\xab\x51\x8a\x10\xf4\xf4\xc4"; main(){ char h,m=h=*t++,*x=t+2*h,c,i,l=*x,s=0; for (i=0;i<l;i++){ i%8? c<<=1: (c=*++x); c&128 && (s+=h); if (!(h>>=1)||!t[s+h]){ putchar(t[s]);h=m;s=0; }}}
