> There isn't an easy way to exempt a range of IP addresses from blacklist lookups, but Mercury help suggests this:
>
> Whitelists
>
> The same technique used by blacklist query servers could also be used to create "whitelists" - servers listing machines that are always
> acceptable. At the time of writing, no public whitelists exist on the Internet that we know of, but if you control your own local domain
> name server, there is nothing to prevent you from entering addresses in the proper form within that database then creating a Mercury
> definition to query it. This approach could be useful if you need to correspond with a site that has somehow become blacklisted, without
> turning off blacklist controls for other sites.
From "Robert Croson, Jr" <robert@arcm.com>
You don't really need to run your own DNS server to support a MercuryS whitekist. It is possible to do it using HOSTS file entries.
http://email.arcm.com/wiki/index.php/HOSTSFileWhiteListing
You can also use a DNS caching utility, such as haneWIN DNS, TreeWalk, or FastCache, instead of a DNS server. These programs simply remember all of your DNS requests, and cache the answers. It could possibly speed up your browsing if you have a slow DNS server. These tools also let you add your own permanent entries as well.
Once you have a DNS cache running, you can do all sorts of funky-cool stuff, including whitelisting domains, IP addresses, controlling what servers are used to deliver your mail (useful if you have access to a relay server, and a specific domain refuses to take mail from your own (i.e. you run a server from your home and are rejected because you are on a dynamic IP)), etc.
You can also add your own DNS blacklist for domains, IPs, etc.
http://email.arcm.com/wiki/index.php/DNSWhiteLists
&gt; There isn't an easy way to exempt a range of IP addresses from blacklist lookups, but Mercury help suggests this:
&gt;
&gt; Whitelists
&gt;
&gt; The same technique used by blacklist query servers could also be used to create "whitelists" - servers listing machines that are always
&gt; acceptable. At the time of writing, no public whitelists exist on the Internet that we know of, but if you control your own local domain
&gt; name server, there is nothing to prevent you from entering addresses in the proper form within that database then creating a Mercury
&gt; definition to query it. This approach could be useful if you need to correspond with a site that has somehow become blacklisted, without
&gt; turning off blacklist controls for other sites.
From "Robert Croson, Jr" &lt;robert@arcm.com&gt;
You don't really need to run your own DNS server to support a MercuryS whitekist. It is possible to do it using HOSTS file entries. &nbsp;
<a href="http://email.arcm.com/wiki/index.php/HOSTSFileWhiteListing" title="http://email.arcm.com/wiki/index.php/HOSTSFileWhiteListing" mce_href="http://email.arcm.com/wiki/index.php/HOSTSFileWhiteListing">http://email.arcm.com/wiki/index.php/HOSTSFileWhiteListing</a>
You can also use a DNS caching utility, such as haneWIN DNS, TreeWalk, or FastCache, instead of a DNS server. These programs simply remember all of your DNS requests, and cache the answers. It could possibly speed up your browsing if you have a slow DNS server. These tools also let you add your own permanent entries as well. &nbsp;
Once you have a DNS cache running, you can do all sorts of funky-cool stuff, including whitelisting domains, IP addresses, controlling what servers are used to deliver your mail (useful if you have access to a relay server, and a specific domain refuses to take mail from your own (i.e. you run a server from your home and are rejected because you are on a dynamic IP)), etc. &nbsp;
You can also add your own DNS blacklist for domains, IPs, etc.
<a href="http://email.arcm.com/wiki/index.php/DNSWhiteLists" title="http://email.arcm.com/wiki/index.php/DNSWhiteLists" mce_href="http://email.arcm.com/wiki/index.php/DNSWhiteLists">http://email.arcm.com/wiki/index.php/DNSWhiteLists</a>