| Some success SPAM is a crime and I feel buying software to block it just ignores the crime. I fight it first-hand: I wrote a program that stores the delivering IP address in a database; another program captures from my logs the IP addresses blocked by Spamhaus; once a week, another program generates Cisco ACLs for blocking ranges of addresses. Blocking key ranges makes a huge dent in the SPAM I receive.
To answer the person who asks if SPAM filters have made SPAM a non-issue, SPAM still consumes a lot of the bandwidth all of us are paying for, and it consumes server resources (plus power, space, hardware, software, support).
I'd like to know exactly why the opposite of Spamhaus - a list of known good e-mail servers - never went forward.
I'd like to see the US - the world's largest SPAMmer - require that ISPs include in Whois certain details about how their IP ranges are used. If a pool is strictly dial-up, or is used for DHCP, any mail delivered from those IPs could not be from a legitimate mail server and could be blocked.
Unlike Spamhaus, I never remove an address from my filters. I think that if this became common, the ISPs would not find customers for these tainted addresses when the SPAMmers released them. Then they'd find a solution to the SPAM problem pretty quick. |
