Hi, a few comments as I digged around in this issue today for an hour or two, too.
Adam D. Barratt wrote: > On Wed, 2015-01-07 at 12:46 +0100, Werner Detter wrote: > > as of January 1st, 2015 the DNSBLs from ahbl.org have been shutdown which > > may lead to false positives > > as requests are positively answered now by the list operators. See the > > relevant announcement: > > > > http://www.ahbl.org/content/changes-ahbl > > > > This adds now 2.699 Hits to every Mail when Spamassassin is used, e.g. > > > > X-Spam-Status: Yes, score=2.825 tagged_above=-999 required=2 > > tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, > > DNS_FROM_AHBL_RHSBL=2.699 > > fwiw this is only an issue if one does not have rule updates enabled > (which one really should): > > /var/lib/spamassassin/3.003002/updates_spamassassin_org/50_scores.cf:# AHBL > is closing down. disabling early. (Axb-2014-03-28) > /var/lib/spamassassin/3.003002/updates_spamassassin_org/50_scores.cf:#score > DNS_FROM_AHBL_RHSBL 0 2.438 0 2.699 # n=0 n=2 Today, there isn't a single mentioning (anymore) of AHBL in the current /var/lib/spamassassin/3.003002/updates_spamassassin_org/ (e.g. http://sa-update.secnap.net/1651303.tar.gz). What I find confusing is that a) not finding DNS_FROM_AHBL_RHSBL in /var/lib/spamassassin/3.003002/updates_spamassassin_org/50_scores.cf (or having it commented as when Adam grepped for it) means that it is disabled even despite a score is set in /usr/share/spamassassin/50_scores.cf, but b) a non-existing /var/lib/spamassassin/3.003002/updates_spamassassin_org/50_scores.cf (or a parent directory thereof) means that the the score of DNS_FROM_AHBL_RHSBL in /usr/share/spamassassin/50_scores.cf counts. Having an explicit "score DNS_FROM_AHBL_RHSBL 0" in the updated SA rules instead of the above sounds much more transparent to me than the logic outlined above. (Yes, this is probably something which would have to be changed upstream.) Noah Meyerhans wrote: > On Wed, Jan 07, 2015 at 08:34:52PM +0100, Werner Detter wrote: > > Which leads me to the next question: why are the rule updates not > > enabled by default in /etc/default/spamassassin ? Default IMHO > > should be CRON=1 instead of CRON=0. > > I agree, but ages ago it was decided (at least in this context), that > reconfiguring hosts non-interactively based on third-party internet > resources by default was not The Debian Way. > > I'm happy to review this decision, but I'd like somebody to make a case > that something has changed, rather than we're simply changing our mind. I think it should be down as with ClamAV: The spamassassin package shouldn't do any updates ("the debian way"), but installing a (fictive) spamassassin-autoupdates package (mostly containing today's /etc/cron.daily/spamassassin) activates them. At least it should be clear from the package's name alone that it does fetch stuff from the internet automatically. Werner Detter wrote: > This decision is absolutly reasonable in general. But ... in the context of > mailservers and mailserver setups - there are third-party internet resources > mailservers rely on and those resources have a direct impact of the > functionality > and configuration (well, "passive" but anyway) - updates for ClamAV for > instance. Yeah, I also see SA and ClamAV in the similar categories, but I must admit that updates are much more severe for ClamAV being able to working properly than for SA. Regards, Axel -- ,''`. | Axel Beckert <a...@debian.org>, http://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `- | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
