|
Spam Filtering @ Monkeys.Com This page provides a set of links that can be used to download the current and up-to-the-minute versions of the various locally-generated and locally-maintained file-based spam blocking lists that we use in conjunction with the various filtering capabilities of our locally-enhanced version of the Postfix mail server. Note that in addition to these locally-maintained file-based spam blocking lists, Monkeys.Com is also using one externally maintained DNS-based spam blocking list, specifically the ORDB List of known/proven unsecured ``open relay'' mail servers (single-hop only). We also use and maintain two DNS-based anti-spam lists ourselves that are popular with other Internet sites, i.e. the Monkeys.Com Unsecured Proxies List, and the Monkeys.Com Unsecured FormMail Spam Sources List. Note that these various locally and externally maintained DNS-based anti-spam lists are actually responsible for the majority of spam blocking that takes place, in practice, here at Monkeys.Com. They are each indispensible to our overall spam defense strategy. Current (up-to-the-minute) versions of our various locally-maintained file-based spam blocking lists may be obtained by following the various links below. Note that these files are not usable directly by Postfix as they stand. Rather, we invoke this Makefile (via the UNIX make command) every time we make a change to any one of these files, and that it turn munges these various .in files into other, munged files that are suitable as input files for the postmap data base creation command. Once those input files have been created, postmap is run on each one of them to create a corresponding Berkeley DB data base file that Postfix can use directly, i.e. when it wants to do fast lookups (e.g. of envelope sender address, envelope sender domain, client domain, client IP address, HELO/EHLO domain, etc.) Look here for information about how we use the lists below in conjunction with Postfix's various filtering capabilities. Note that we try hard to do most of our filtering based on domain names (either domain name parts of envelope sender addresses or domain names given in HELO/EHLO command or the inverse DNS domain names of SMTP clients) as opposed to filtering based on IP addresses (or ranges) because domain name based filtering tends to remain effective even if the spammers relocate to different IP address or address blocks. (Spammers frequently vary their envelope sender domains, in an attempt to bypass filters, but we have yet to see any that are clever enough to vary the HELO/EHLO parameter in the spamware they use, for example.) And now, without further ado, here are our current file-based spam filtering lists.
|