I understand - I think - about IPBYPASS but HOPHIGH is another story..
HOPHIGH, if used, will cause Declude JunkMail to scan extra hops.
For example, if I was to set up our mailserver to send this E-mail through our ISP's mailserver, Declude JunkMail would normally just scan the IP of our ISP's mailserver. But with "HOPHIGH 1", the IPs of both the ISP's mailserver and ours would be scanned.
This is useful to catch spam that is forwarded from an account on another server to an account on yours. It was also useful in the old days before open proxies, where a spammer might find an IP that wasn't listed in any spam databases, and he would relay through it -- but the IP the spammer was sending to the open relay from was listed in spam databases.
I am interested because often times mail is forwarded to my server and as such some tests are not as effective. As an example <sombody>@example.com send an email to a server that in turn forwards the email to one of my users. Spamdomains fails because the connecting server to me was not example.com but foo.com Would hophigh help me out with this - see who originally sent the email?
Yes, it would.
What is the downside to HOPHIGH=1 other than more dns work and if that is the case is it negligible? What is its real purpose?
It does involve extra DNS usage, and delays the E-mail from being delivered for slightly longer in waiting for the results. But that is about it.
-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've been missing: Ask about our 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.
