On Ubuntu 16.04, I have no issues with the plugin, it works fine for me. On Wed, Nov 22, 2017 at 8:34 PM, Kevin Miller <kevin.mil...@juneau.org> wrote:
> Debian Jessie, Perl version 5.020002 (5.20.2) > > Not bleeding edge, but not from the Dark Ages either. How about > yourself? What distro/version do you have? > > FWIW, to install it I downloaded the plugin from http://msbl.org/tools/sa- > hashbl.tar.gz, extracted it and saved the two files in it to > /etc/spamassassin. To wit, hashbl.cf and HashBL.pm. > > It may be a version issue however, because on Debian Stretch I just did > that, and I don't get the error. No idea which perl module is behind the > times however. Updating all my mail servers to Stretch is problematic; > when I did it on my test host a number of things went pear shaped, and I > haven't had time to work through them so that my live boxes aren't > clobbered during an upgrade. > > ...Kevin > -- > Kevin Miller > Network/email Administrator, CBJ MIS Dept. > 155 South Seward Street > Juneau, Alaska 99801 > Phone: (907) 586-0242, Fax: (907) 586-4588 Registered Linux User No: > 307357 > > > -----Original Message----- > From: Alex [mailto:mysqlstud...@gmail.com] > Sent: Wednesday, November 22, 2017 11:11 AM > To: Kevin Miller; SA Mailing list > Subject: Re: MSBL Email Blocklist (EBL) SA usage query > > Hi, > > On Wed, Nov 22, 2017 at 2:20 PM, Kevin Miller <kevin.mil...@juneau.org> > wrote: > > I have not solved that error. I’m not a perl programmer so I emailed > the folks at msbl.org and they haven't been able to get hold of the > author of the perl module (Steve Freegard I believe). I think I have all > required perl modules installed but names vary between distributions so > sometimes that a toss of the dice. I don't know if it's just a Debian > thing or is more widespread... > > I've been using hashbl for a few months now and haven't had any problems. > It's caught quite a few, although none of them have caused an email to be > triggered as spam (they would have all been spam anyway). > > What environment are you using? It was written in 2016, so at the least, > make sure your perl and perl modules are at least that current. > -- - Markus
