-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 In <[EMAIL PROTECTED]">mid:[EMAIL PROTECTED]>, Tom Geldner [TG] wrote:'
TG> The one point on which I disagree with the article is that DNSable TG> blacklists are somehow actionable in court. That seems like pure TG> nonsense to me. Nobody HAS to use a blacklist. It is the ISP's or TG> individual customer's choice. They are services and nothing more. This is the crux of the matter and I agree. MDaemon on my server here has spam filtering functionality that uses blacklist servers but I've explicitly disabled this because I can't tolerate false innocent mail getting caught. This was happening to me when I was using a domain mail forwarding service offered by my DNS host for free. I'm glad that's behind me. TG> SpamCop does have one serious shortcoming. It does NOT reduce TG> your spam by reporting through it. 90% of the junk mail comes TG> from about 10 major sources in China and a few in Brazil. They TG> could care less who reports them and their upstream feeds to the TG> backbone don't either. Reporting spam is one of the services offered by SpamCop. The other is a paid service where you're given an e-mail address which spamcop will keep free of spam using it's spam filtering service. It's this service that the article is referring to. I haven't read any of the terms of service but I'm pretty sure it should contain something that covers their responsibility for inadvertent filtering of legitimate mail sent via blacklisted servers. There are various ways to configure the filtering system anyway. - -- Allie C Martin \ TB! v1.62/Beta5 & WinXP Pro (SP1) List Moderator / PGP Key - http://pub-key.ac-martin.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.0 (Win32) - GPGshell v2.60 iD8DBQE9lkPcV8nrYCsHF+IRAgsbAKDUfvSoEa/069M+Dc4UzDZXeqj6zwCg+G3l LXKthjnovnu7acuNa2fySZ4= =XvZQ -----END PGP SIGNATURE----- ________________________________________________ Current version is 1.61 | "Using TBUDL" information: http://www.silverstones.com/thebat/TBUDLInfo.html
