Generally speaking, because spamdyke does not run as a daemon, any kind
of caching is very difficult. The cache would have to be disk-based,
which can be tricky when the server is very busy and multiple instances
of spamdyke are attempting to update the disk. If the server isn't very
busy, having a cache won't matter much.
For the two things you mentioned, DNS RBL and rDNS lookups, try
installing a caching DNS server on the mail server. You can configure
it (or use iptables) to only allow queries from the local machine. I
think you'll be surprised how much it helps.
-- Sam Clippinger
Paulo Henrique wrote:
Sam, I was wondering if it would be possible to implement a system of
cache in spamdyke, I believe that improving the speed in RBL test and
rDNS.
A spammer usually tries to send messages to more than one account in
the same domain, with the system cache, as soon as the first attempt
was denied the ip address of origin would be stored in a file or
directory and future attempts would be consulted in the cache, if the
address is found in the cache the other tests should not be run, if
not found the tests continue the normal procedure.
I am thinking in a way to do this using bash script + iptables, but I
think this would be a point to the spamdyke.
What do you think?
___
spamdyke-users mailing list
spamdyke-users@spamdyke.org
http://www.spamdyke.org/mailman/listinfo/spamdyke-users
