1. The trouble with ivuribl is it doesn't work too well with
dbl.spamhaus.org.
And I wish we'd see some changes to invuribl to accommodate it.
One problem is that all numbered IP addresses will return 127.0.1.255. Which
shouldn't be scored.
The second problem that the invuribl bitmasking rea
I suggest monitoring the sniffer hits and increase/decrease the scoring
accordingly depending on the false positives you see. Ideally you should
be combo'ing a sniffer hit w/other tests to maximize sniffers
effectiveness.
-Nick
MadRiverAccess.com|Skywaves.com Tech Support
US/Canada 877-873-6482
I am using the built-in version of Sniffer and the recommended Declude setting.
However, lately I'm seeing lots of spam get through that is failing some of the
sniffer tests. I'd like to increase the weight on some of these failures.
Recommendations?
---
This E-mail came from the Declude.Jun
Well this all looks good. if this invuribl app makes a log check it to see if
you are getting hits; if you aren't that is a problem...
Additionally add dbl.spamhaus.org as an additional uribl test
-Nick
MadRiverAccess.com|Skywaves.com Tech Support
US/Canada 877-873-6482 or International +1-802-
I’m not quite sure what you mean. In the Declude global.cfg file the only
reference to inv-uribl is
INV-URIBL external weight "D:\imail\INVURIBL\INVURIBL.exe %WEIGHT%
%REMOTEIP%" 0 0
In the invUribl.exe.config file there is (in part):
**
What uribl tests are you using and are you getting hits on them - check
your logs..
I'm suggesting you may need different tests - the one you are using may
have blacklisted you or are dead even...
-Nick
MadRiverAccess.com|Skywaves.com Tech Support
US/Canada 877-873-6482 or International +1-802-22
I'm still having trouble with more spam seepage, so I've been looking at my
various tests. I noticed that in the past, the Inv-uribl test caught 63-70%
of messages, but recently it's only catching 56%. When I look at a lot of
the low value spam (messages that barely get classified as spam), they
