Assuming we're all talking about the same thing, Declude continues to run as a process waiting for replies from IP4r requests but does not consume much CPU time while doing so.
That is correct. It should use very, very little CPU time while waiting for the results to come back.
Does pulling out IP4r tests during an episode show a immidiate decline in CPU use?
It shouldn't cause a noticeable decline in CPU use -- I can't explain Kami's results.
Does anyone know how the people hosting the IP4r tests feel about us slamming them with queries?
You're not. Specifically, they will see the same number of queries whether you are running IMail v8's anti-spam, Declude JunkMail's, or some other anti-spam solution.
The reason for this is that your local DNS server will cache the results.
Suppose I'm cruising along with 20,000 queries a day, then jump to 500,000 over a few weeks, surely that makes an impression somewhere? Is there a point were we should ask about doing more?
There are some spam databases that request that heavy users (typically 100,000+ E-mails/day) do zone transfers (downloading the DNS data a couple times a day).
However, if 80% of the lookups are cached, you're talking about 20,000 queries hitting the spam database for every 100,000 E-mails. The root DNS servers are able to handle up to tens of thousands of queries every second; DNS is very efficient.
-Scott
---
Declude JunkMail: The advanced anti-spam solution for IMail mailservers.
Declude Virus: Catches known viruses and is the leader in mailserver vulnerability detection.
Find out what you have been missing: Ask for a free 30-day evaluation.
--- [This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)]
--- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type "unsubscribe Declude.JunkMail". The archives can be found at http://www.mail-archive.com.
