FS#37865 - [spamassasin] add sa-update to cron.daily for spamassasin

Attached to Project: Arch Linux
Opened by Łukasz Michalski (zork) - Thursday, 21 November 2013, 16:44 GMT
Last edited by Florian Pritz (bluewind) - Monday, 02 December 2013, 09:42 GMT
Task Type Feature Request
Category Packages: Extra
Status Closed
Assigned To Florian Pritz (bluewind)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:
Spamassassin should update its spam matching patterns from cron job.

Additional info:
spamassassin 3.3.2-9
This task depends upon

Closed by  Florian Pritz (bluewind)
Monday, 02 December 2013, 09:42 GMT
Reason for closing:  Won't implement
Comment by Jens Adam (byte) - Friday, 29 November 2013, 23:08 GMT
I know this cron job from Debian systems and while the idea is good, I want to note that it might be a lot more complex than you'd think.

If people are using "loadplugin Mail::SpamAssassin::Plugin::Rule2XSBody", you'd have to make sure that sa-compile gets run after sa-update, and daemons like spamd or spampd need a restart as well.
Comment by Florian Pritz (bluewind) - Saturday, 30 November 2013, 09:46 GMT
There are a few more corner cases (multiple update channels, run more than once a day) that complicate this further and I don't really see the gain. I don't want to maintain such a cronjob and I especially don't want to have to deal with all the fallout such a change would bring if not done properly (which is hard) so sorry, won't implement.
Comment by Łukasz Michalski (zork) - Monday, 02 December 2013, 09:06 GMT
When i.e. clamav, slocate packages are installed, scripts that update their databases are added to crontab. One can expect that spammassasin package will behave like this too.
So I would consider at least adding a message when package is installed that I need to schedule sa-update myself.

Comment by Florian Pritz (bluewind) - Monday, 02 December 2013, 09:42 GMT
FWIW: clamav doesn't ship a cronjob, there is a service file for the update daemon, but you have to enable that so it doesn't count here.

Information regarding setup doesn't belong into install messages, it belongs into the wiki. If you think it is really necessary please create a Spamassassin wiki page.

Loading...