I just opened
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=8041
The issue is that the test spam t/data/spam/pyzor is a real world spam
that is on the public pyzor server, but the server is apparently
configured to expire spam reports. I'm guessing it has a one year expiry
given that Giovanni had to update the test with a new spam about a year
ago, and t/pyzor.t just started failing.
I ran
pyzor report < t/data/spam/pyzor
and all was well again.
Is it reasonable for to put a cron job on one of our infrastructor
machines that, perhaps once a month, or some other convenient interval,
runs the pyzor report command to ensure that the test spam doesn't
expire? Extra points for running pyzor check < t/data/spam/pyzor before
and after the report to confirm that the report worked and incremented
the count, but that is less important.
What do you all think about that?
Sidney
