On Wed, 21 Nov 2012, Axb wrote:
On 11/21/2012 10:48 PM, Thierry Besancon wrote:
Hello
Google obsoleted GoogleSafeBrowsing version 1 of its protocol several
months ago.
It seems to me that the GoogleSafeBrowsing plugin for Spamassassin
is still Using this version 1 and thus is now outdated.
I'm quite new to this list. Can i be confirmed it is still version 1
and that no version 2 of the plugin is available or was discussed here,
please?
Thanks in advance.
Best regards,
Thierry BESANCON
yep - unsupported abandonware
I contacted the plugin's author about 6 months ago and he wasn't interested
in updating to version 2
It's a bit of a kluge, but you can get much of that functionality indirectly
using ClamAV and the spamassassin clamav plugin.
In your freshclam config file enable the "SafeBrowsing" option, it will start
downloading an optional "safebrowsing.cvd" sig file which is derived from the
Google SafeBrowsing data. Set up spamassassin to use the ClamAV plugin pointing
to the instance of clamd that uses those sigs, and you should then get
hits from the SafeBrowsing data.
I actually run two seperate instances of clamd/freshclam. One using just the
standard base ClamAV sigs which is then used by my incoming MTAs in smtp-reject
mode via milters.
The other clamd/freshclam uses the "SafeBrowsing" option, various heuristics
methods (such as PhishingScanURLs) and a whole bunch of optional 3rd party
signatures (such as the Sanesecurity sigs). I don't trust this for outright
blocking at the MTA level (too great a risk of FPs), but it's great for use in
a weighted scoring system as provided thru spamassassin.
--
Dave Funk University of Iowa
<dbfunk (at) engineering.uiowa.edu> College of Engineering
319/335-5751 FAX: 319/384-0549 1256 Seamans Center
Sys_admin/Postmaster/cell_admin Iowa City, IA 52242-1527
#include <std_disclaimer.h>
Better is not better, 'standard' is better. B{
