[ Date Index ][
Thread Index ]
[ <= Previous by date /
thread ]
[ Next by date /
thread => ]
Kegs wrote:
Not all that small really, SPEWS is well known for its collateral blocking, where they block a whole IP range, so that the ISP can't just move the spammer to an unblocked IP. This normally occurs when the ISP has been unresponsive to complaints, and over time the IP range is widened, there are a few ISP who have had their entire IP range blocked by SPEWS, notably Wanadoo.
I believe they also blocked the Demon SMTP relay servers at one point, which are the output of any open relays at Demon customer sites that utilise the Demon relays for performance, or other reasons. Such approaches just give too many false positives, sure there are some IP address out there who turn out a lot of spam, but not all IP's turning out a lot of spam are turning out just spam. They also prevent you logging SMTP level information, likely to show if it is giving any false positives. One thing worse than stopping genuine emails, is stopping genuine emails and not knowing you are doing it. For anything beyond personal use you should not block more than spam inputs based on IP address I think, even then I prefer other approaches - Spam Assasin and friends. I'm looking at TMDA for personal use (Theo was using this), as a spam reduction technique it looks good, but I'm still trying to figure out how it fits my email configuration. Simon -- The Mailing List for the Devon & Cornwall LUG Mail majordomo@xxxxxxxxxxxx with "unsubscribe list" in the message body to unsubscribe.