sa-update & psa-spamassassin

[CPJ]

I have a question about the best way to set up a regular sa-update with psa-spamassassin on Debian 5 & Plesk 9.3.

I can see that psa-spamassassin is using the folder "/usr/share/spamassassin" for the spam rule files, rather than the normal "/var/lib/spamassassin/<version>". I don't think Plesk runs a regular sa-update on the spam rule files because the rule files in "/usr/share/spamassassin" are all dated 1st of Jan 2010.

If I manually run "sa-update --updatedir /usr/share/spamassassin", it creates a sub-folder "/usr/share/spamassassin/updates_spamassassin_org/ with the new rule files and a "updates_spamassassin_org.cf" file in "/usr/share/spamassassin" to "include" all these new rule files.

So far so good...

But what is the correct way to setup a regular sa-update ?

Should I just create a cron job ? Or will this conflict with Plesk's own updates ?

Do I also need to restart psa-spamassassin after running sa-update ?

If I move to 9.5, are there any changes or improvements in spamassassin or greyfilters ?

Thanks for any advice...

By the way, if anyone from Parallels reads this thread, I couldn't find ANY Plesk documentation on setting up the spamassassin or greylist filters & updates... Since SPAM is changing all the time, it's just not acceptable to have a static set of rules...

 

[CPJ]

I've made some progress...

I found there is a spamassassin script file in /etc/cron.daily, which calls sa-update and sa-compile.

Of course, it doesn't work with psa-spamassassin...

I've modified it to work with psa-spamassassin and it's directories.

 

[nickweavers]

Hi CPJ,

Well done for digging into this and finding the problem and the solution.

Were the mods to the scripts obvious? If not, could you possibly post a copy here for the benefit of others wanting to get the regular updates working under plesk?

TIA,
Nick