"Covington, Chris" <[EMAIL PROTECTED]> writes: > Why is this test deprecated in 2.60?
Because trusted_networks works better to avoid checking internal hosts. It still works for 2.6x, though. The documentation clearly explains this. It even says "It will be removed in a future version." > I've had to disable RBLs all together because of too many FPs from > people who have DHCP/Cable Modems (on RBLs) and use their legitimate ISP > SMTP servers (not on RBLs). This setting would fix the problem if it > weren't disabled. No, it is not disabled. No, it would not address that issue. num_check_received doesn't remove the originating IP unless you set it to zero which is the same as turning off RBLs entirely. num_check_received sets how many IPs to include, starting from the originating IP, which is going to be the same one as those dynamic addresses. If you have too many false positives for a blacklist, you can disable it by setting the score to 0: score RCVD_IN_DYNABLOCK 0 score RCVD_IN_NJABL_DIALUP 0 > I'd like to un-disable RBLs and set num_check_received to 2 or 3 for > those users who forward email from outside accounts to our domain and > therefore bypass RBL checks at the MTA-level (since the forwarding SMTP > server is not on any RBLs). > > How does its replacement trusted_networks solve this problem? Specify that you trust those IP addresses (and the forwarding SMTP server) to send you mail. They shouldn't be checked by any RBLs then. Daniel ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
