We have been moving our IP4R tests from Declude to IMail (version 8) and are finding it more and more effective.
This has the added benefit to delete emails before they reach Declude.
we have added over 60 of the IP4R tests to IMail and checked the options for REVDNS, Verify email, and the HELO verification. Then made it delete if 10 tests fail....
But to me it seems like this is more CPU effective.
I'm just going to add a few of my own comments to this thread. :)
The one main advantage to having IMail delete the E-mail is that the Declude.exe process doesn't need to start, which saves CPU time. This would be very useful if you process lots of E-mail (100,000s a day), and/or have extensive processing in Declude JunkMail (such as lots of filters).
However, the main disadvantage here is that it will slow down delivery of the E-mail by having IMail process it. If you have 60 ip4r tests running in IMail, and they take an average of 1 second each to get the DNS results back, that's a full minute that the E-mail delivery will be delayed for valid E-mail (assuming that your local DNS server doesn't have a cached answer). Also, if IMail's SMTPD process has a limit to the number of E-mails it can handle at the same time, this limit would get hit much more quickly with lots of ip4r tests running (I don't know if there is a limit, however).
-Scott
---
Declude JunkMail: The advanced anti-spam solution for IMail mailservers.
Declude Virus: Catches known viruses and is the leader in mailserver vulnerability detection.
--- [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.
