Jason Haar wrote:
Then the third filed is NONE. That's how I do it. But the idea is that
any kind of daya can be collectively gathered and distributed.
Instead of a TCP channel (which means software), what about using DNS?
If the SA clients did RBL lookups that contained the details as part of
the query,
With any sane SpamAssassin setup for multiple users this wouldn't work.
Any SA install except for very small mail flows should use a caching DNS
server/proxy, preferably one that caches negative results. It's also a
good idea if the caching server used for DNSL checks enforces a minimum TTL.
This results in repeated queries not making it to the origin servers.
Even if the origin server uses ridicilously low TTLs.
The distributed caching nature of DNS is a reason why DNSLs are so
efficient, but also one reason why DNS isn't suitable for everything.
Regards
/Jonas
--
Jonas Eckerman
Fruktträdet & Förbundet Sveriges Dövblinda
http://www.fsdb.org/
http://www.frukt.org/
http://whatever.frukt.org/
