<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Getting Rid of Foreign Language Spam</title>
	<atom:link href="http://blog.dogbark.com/getting-rid-of-foreign-language-spam/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.dogbark.com/getting-rid-of-foreign-language-spam/</link>
	<description>sniffing around the Internet</description>
	<lastBuildDate>Tue, 24 Feb 2009 02:14:53 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2</generator>
	<item>
		<title>By: Wagging the Dog(Bark) &#187; Blog Archive &#187; The Fight Against Spam</title>
		<link>http://blog.dogbark.com/getting-rid-of-foreign-language-spam/comment-page-1/#comment-415</link>
		<dc:creator>Wagging the Dog(Bark) &#187; Blog Archive &#187; The Fight Against Spam</dc:creator>
		<pubDate>Thu, 30 Oct 2008 20:43:36 +0000</pubDate>
		<guid isPermaLink="false">http://blog.dogbark.com/?p=230#comment-415</guid>
		<description>[...] Spam with foreign languages cannot be blocked simply based on the language it was written in.  Why? Because we most likely have customers speaking that language, so blocking those messages based on that wouldn&#8217;t be fair to everyone using our services. It wouldn&#8217;t be cool for us to block all English emails would it? If you want to take this kind of spam head-on please see this article about rules and filters. [...]</description>
		<content:encoded><![CDATA[<p>[...] Spam with foreign languages cannot be blocked simply based on the language it was written in.  Why? Because we most likely have customers speaking that language, so blocking those messages based on that wouldn&#8217;t be fair to everyone using our services. It wouldn&#8217;t be cool for us to block all English emails would it? If you want to take this kind of spam head-on please see this article about rules and filters. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Harry</title>
		<link>http://blog.dogbark.com/getting-rid-of-foreign-language-spam/comment-page-1/#comment-409</link>
		<dc:creator>Harry</dc:creator>
		<pubDate>Mon, 27 Oct 2008 20:52:44 +0000</pubDate>
		<guid isPermaLink="false">http://blog.dogbark.com/?p=230#comment-409</guid>
		<description>A couple of notes on this one: 

• as with most filters, this is pretty specific. charset=koi8-r is not the same as charset=&quot;koi8-r&quot;. You may have to augment the filter occasionally.
• this will only affect emails that have a declared charset, i.e. plain-text emails. If the text is HTML, then the content type will be MIME, and the charset will be called from within the HTML, which means that the filter won&#039;t see it.

However, this kind of method should help you filter out a large majority of the foreign language junk mail you are receiving.</description>
		<content:encoded><![CDATA[<p>A couple of notes on this one: </p>
<p>• as with most filters, this is pretty specific. charset=koi8-r is not the same as charset=&#8221;koi8-r&#8221;. You may have to augment the filter occasionally.<br />
• this will only affect emails that have a declared charset, i.e. plain-text emails. If the text is HTML, then the content type will be MIME, and the charset will be called from within the HTML, which means that the filter won&#8217;t see it.</p>
<p>However, this kind of method should help you filter out a large majority of the foreign language junk mail you are receiving.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

