On Fri, Feb 27, 2015 at 08:26:43AM +0800, Paul Wise wrote: > I guess it is possible but it seems unlikely. CRON=0 was set so it > definitely didn't have sa-update running on an ongoing basis. > > Is there any way to tell what happened after the fact?
If you re-set spamassassin to the default configuration with no updates
(rm -rf /var/lib/spamassassin/{3*,compiled}), and bounce the
spamassassin service, do you still see AHBL hits?
> Personally I wonder why sa-update isn't the default when network is
> available, have you considered doing that, maybe for stretch?
Yeah, I've definitely considered that. I posted about it on my blog
(aggregated on planet) recently and got a few responses. Some really
liked the idea, others really disliked it. My inclination is to make the
change, but with a debconf note and/or NEWS.Debian update to make sure
the change is widely communicated.
https://noah.meyerhans.us/blog/2015/01/15/spamassassin-updates/
(Many of the comments came by email, presumably by people who didn't
want to post via disqus.)
noah
signature.asc
Description: Digital signature
