https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7121
Kevin A. McGrail <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #1 from Kevin A. McGrail <[email protected]> --- Here's some ideas to improve the script 1 - Have the script ALSO check the DNS entries and list them in the email as well as checking ruleqa? If DNS is changed, we published a rule, for example: TXT 1.4.3.updates.spamassassin.org TXT 0.4.3.updates.spamassassin.org TXT 3.3.3.updates.spamassassin.org 2 - Perhaps post the entries from the last few days? That will show the trend much more accurately I think. 3 - In general, the script helps me know when a rule publishing did not occur but it is not always accurate. There is a deviation between ruleqa and the masscheck scripts on counts that I have not identified the source. 4 - The script that runs that does updates is: Cron <updatesd@spamassassin-vm> bash /export/home/updatesd/svn/mkupdates-with-scores/do-stable-update-with-scores The output of that script arrives about 10:30PM Eastern and 5 - If that script fails, it emails the ruleqa list like [auto] do-nightly-rescore-example 8 6 - I then can look at the cron output for do-stable-update-with-scores to find out why it failed. 7 - if we publish a rule, there is a cron like Output from your job 104 from Rule Updates Daemon -- You are receiving this mail because: You are the assignee for the bug.
