Q: This documentation doesn't seem to cover how to configure DNS-Blocklists. The following blocklist providers have implemented a Block Notification Rule with SpamAssassin: However, we do not support methodologies that purposefully return wrong answers and those DNS-Blocklists will be disabled by default. SpamAssassin supports the "free for some" model since it works for the majority of SpamAssassin installations. The choice is up to the DNS-Blocklist administrator. Resolving the block might be as simple as using your own non-forwarding caching nameserver to avoid being lumped together with other users queries setting up your own mirror of the DNS-blocklist or paying to use the blocklist. If you were directed to this link from a rule description, then you have a DNS-Blocklist that is purposefully blocking your queries. What does this mean?Ī: DNS-Blocklists often run on the "free for some" model and/or they may limit the number of queries you can perform to maximize resources. Q: My queries to a DNS-blocklist were blocked. (For example, a blocklist that returned a match for every single mail would 'catch all the spam', but would also mark every nonspam mail too.) Some of the above pages omit this information, so take with a pinch of salt. Note that it's extremely important to compare false positive rates (nonspam messages marked as spam), as well as spam hit-rates, when evaluating any anti-spam system, include DNS blocklists. Weekly Blacklist Statistics (including hit rate and false positive rate). Other places to find out about DNS blacklists / blocklists:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |