<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.4" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Spamhaus, SpamCop Dissed By NTsecurity</title>
	<link>http://www.emailbattles.com/2004/11/17/spam_aajjgjfhea_ff/</link>
	<description>Spam, Security, Privacy, Spyware, Phishing &#038; Viruses from the Front Lines.</description>
	<pubDate>Wed, 19 Nov 2008 23:56:47 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.4</generator>

	<item>
		<title>by: Anonymous Lumberjack</title>
		<link>http://www.emailbattles.com/2004/11/17/spam_aajjgjfhea_ff/#comment-1586</link>
		<pubDate>Wed, 25 Oct 2006 16:36:44 +0000</pubDate>
		<guid>http://www.emailbattles.com/2004/11/17/spam_aajjgjfhea_ff/#comment-1586</guid>
					<description>Filters are great, but they are expensive (for bandwidth costs and processing requirements on my end) because the cost of spam is still my burden.  Blacklists work extremely well because the blocked spam never enters my system in the first place, and pressure is put on the sending systems' upstream providers to clean up their act when users complain that their eMail is blocked.

"Clueless" is the word I'd use to describe you because spammers 
regularly forge Received SMTP headers.  If SpamCop.Net believed every 
Rececived SMTP header it found, then I wouldn't use it. 

You also call it a "false positive" when an entire ISPs netblock is 
blacklisted, but I don't see it this way -- to me, if the ISP gets 
their entire netblock blacklisted, then there's obviously a very 
serious problem on their systems and the only ones who will truly have 
the needed influence to put an end to the spam problem are the paying 
customers who don't like being blacklisted. 

I see it as completely justifiable to blacklist an ISPs entire 
netblocks after they've demonstrated that they don't take the spam 
problem seriously, because they 1., don't terminate spammers (ignoring 
abuse reports may be part of the problem), and 2., are more likely to 
acquire additional spammers as customers (ISPs who take the spam 
problem seriously tend to be far less attractive to spammers).</description>
		<content:encoded><![CDATA[<p>Filters are great, but they are expensive (for bandwidth costs and processing requirements on my end) because the cost of spam is still my burden.  Blacklists work extremely well because the blocked spam never enters my system in the first place, and pressure is put on the sending systems&#8217; upstream providers to clean up their act when users complain that their eMail is blocked.</p>
<p>&#8220;Clueless&#8221; is the word I&#8217;d use to describe you because spammers<br />
regularly forge Received SMTP headers.  If SpamCop.Net believed every<br />
Rececived SMTP header it found, then I wouldn&#8217;t use it. </p>
<p>You also call it a &#8220;false positive&#8221; when an entire ISPs netblock is<br />
blacklisted, but I don&#8217;t see it this way &#8212; to me, if the ISP gets<br />
their entire netblock blacklisted, then there&#8217;s obviously a very<br />
serious problem on their systems and the only ones who will truly have<br />
the needed influence to put an end to the spam problem are the paying<br />
customers who don&#8217;t like being blacklisted. </p>
<p>I see it as completely justifiable to blacklist an ISPs entire<br />
netblocks after they&#8217;ve demonstrated that they don&#8217;t take the spam<br />
problem seriously, because they 1., don&#8217;t terminate spammers (ignoring<br />
abuse reports may be part of the problem), and 2., are more likely to<br />
acquire additional spammers as customers (ISPs who take the spam<br />
problem seriously tend to be far less attractive to spammers).
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
