PEAK XOOPS - News 
The success ratio of mod_access_rbl was up to 50-60%, in this three days statistics.
It does not look enough.
Thus, all XOOPS site should be installed Protector with its URI counting filter, I guess.
That's because RBL servers is made not for comment/trackback SPAMs but for mailing SPAMs.
Only sbl-xbl.spamhaus.org works great for comment/trackback SPAMs.
With this result, I've just added it as default servers into Protector's RBL plugin.
There are too many comment/trackback spams recently.
The amount of comment/trackback spams should be called as DDoS.
Thus I've just installed mod_access_rbl as an apache module in this site.
As I cannot access here (I don't know why),
http://www.blars.org/mod_access_rbl.html
I have to re-import the patch from Apache2 to Apache1.3
If you can get the original patch from blarson@blars.org, use it instead of mine 
Protector V3 has just been released.
You'll find this is a changed version drastically.
- The logic goes to XOOPS_TRUST_PATH
Don't forget remove "2 lines" for hooking into protector in mainfile.php before updating the module.
After Protector V3 has been installed/updated, you have to insert "2 lines" containing XOOPS_TRUST_PATH instead of XOOPS_ROOT_PATH into mainfile.php.
- Denying IPs
Protector V3 uses a file for denying IP instead of DB.
If you banned yourself, just remove the file under XOOPS_TRUST_PATH/modules/protector/configs/
- Limiting IPs for group=1
If webmaters of your site access from small range of IPs, set this.
It saves you from password cracking, session hijacking etc.
If you cannot log your site in, just remove the file under XOOPS_TRUST_PATH/modules/protector/configs/
- anti-XSS (BigUmbrella)
http://xoops.peak.ne.jp/md/news/index.php?page=article&storyid=126
- anti-SPAM with many URIs
Basic logic:
http://xoops.hypweb.net/wiki/5589.html
- compatibility checks with XOOPS Cube 2.1 Legacy
Of course, Protector V3 works with XOOPS 2.0.x*, 2.2.x, and Oreteki.
XOOPS Cube 2.1 Legacy RC has already released on 22nd Jan 2007.
I've just tested it whether my modules work fine or not.
The result... ALL GREEN!
Though Cube 2.1 Legacy has full-scratched core far from X2, it maintains high module compatibity!
I'm surprised with the great work.
Bravo! minahito, nobunobu, and Tom_G3X.
I've just made an icon of "XC2.1 Ready!".
I'll add it into mydownload's records of the modules have been checked the compatibility.
In D3 modules (pico, wraps etc.), the module icons are drawn with its dirname automatically.
But they are not so clear to distinguish, if you've installed them a lot.
You can override each module icons safely.
Just make a icon named module_icon.png and copy it into public side of XOOPS_ROOT_PATH/modules/dirname/ .
The file will never be overwritten by updating D3 module.