----- Original Message ----- From: "Gordan Bobic" <[EMAIL PROTECTED]>
[EMAIL PROTECTED] wrote: >> No one has mentioned that it's necessary to wait until >> the possible spammer identifies his target to know >> whether the target has him whitelisted. Gordan wrote: > Whitelists aren't really practicaly on big setups. You need to block a > lot before they even get as far as talking TCP. If you can manage a > decent job with that, RBLs can prune enough of what's left for > spamassassin and virus scanners to be able to cope with the minute > amount of mail that is actually deliverable. It is not all that uncommon > to see the spam:ham ratio of around 250:1. When you have a system > handling mail for half a million domains, well, you get the idea. > Whitelists aren't really practicaly on big setups handling mail for half a million domains. Ahhh, but nonetheless they are a part of the Courier algorithm... ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ courier-users mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
