Hi Linto,
the per-domain basis you can create by using the config-dir option,
wich is well documented in the documentation:
http://www.spamdyke.org/documentation/README.html#CONFIGURATION_DIR
Nearly any combination of sender and recipient can be configured
with this option. This way i
As an answer to this:
Is it possible to just put a whitelist for example.com
http://example.com and deny all others matching this keyword.
Sure. I would just whitelist 66.49.15.190 and blacklist .nuvox.net
http://nuvox.net. Don't know wich one catches
first. I would try.
Regards,
David
Whitelists always override blacklists, no matter where they are found or
what order they are listed in.
-- Sam Clippinger
David Stiller wrote:
As an answer to this:
Is it possible to just put a whitelist for example.com
http://example.com and deny all others matching this keyword.
Sure. I
David/Linto,
This is very interesting setup.
I would like to push it a bit further and try to find out if it's
possible to have a IP_IN_RDNS_KEYWORDS restriction in place
server wide, while allowing a few handpicked domains to have it fully
turned off. We would like to maintain for RDNS
Yes, this can be done using configuration directories. Simply follow
David's example below, but change the configuration files
(.../domain_setups/_recipient_/tld/firstdomain) to contain one or more
of the following options as appropriate:
ip-in-rdns-keyword-blacklist-file=!!!
