[Michael Morris]

Agreed. Together they are pretty tight, and the nice thing about the new plug in system is the (I presume) can run at the same time without bothering each other.

vSpamScan checks the whole message for the domains - not just the URL's (It's actually more difficult from a coding perspective to stick to just the url's). For instance freewebs.com is on the blacklist. The program will score that whereever it shows up in the message - url tag, img tag, out in the open, it doesn matter.

Now admittedly it doesn't check signatures or PM's (I think - do those use the build_new_post function? If so it checks them cause that's where the hook is at)

Oh well. I probably will download this too for those cases when spam gets by the filter (though I've only had it happen once in 7 months and against 400 tries, which is a good record I think). Also you are right in that coventry posts take memory on the system even if they are unseen - but the main reason for vSpamScan's use of that system is for those occassions when the system scores a false positive. I've had 3 of those since I started with the prototype on 3.0.7 - and they can be a diplomatic pain.