<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
	<channel>
		<title><![CDATA[UPDATE: Secret Spam Message! - Consumerist Comments]]></title>
		<image>
			<url><![CDATA[http://cache.gawker.com/assets/base/img/thumbs140x140/consumerist.com.png]]></url>
			<title><![CDATA[UPDATE: Secret Spam Message! - Consumerist Comments]]></title>
			<link><![CDATA[http://consumerist.com]]></link>
		</image>
	    	<lastBuildDate><![CDATA[Wed, 12 Apr 2006 07:49:41 EDT]]></lastBuildDate>
	    	<pubDate><![CDATA[Wed, 12 Apr 2006 07:49:41 EDT]]></pubDate>
		<link><![CDATA[http://consumerist.com/consumer/spam/update-secret-spam-message-166383.php]]></link>
		<description><![CDATA[]]></description>
		<item>
		    <title><![CDATA[UPDATE: Secret Spam Message!]]></title>
		    <link><![CDATA[http://consumerist.com/consumer/spam/update-secret-spam-message-166383.php#c98276]]></link>
										
		    <description><![CDATA[You want me to translate it for you? <p>Jesse in Japan</p>]]></description>
			<dc:creator><![CDATA[Jesse in Japan]]></dc:creator>
		    <guid isPermaLink="false"><![CDATA[31:166383:c98276]]></guid>
		    <pubDate><![CDATA[Wed, 12 Apr 2006 07:49:41 EDT]]></pubDate>
		</item>
		<item>
		    <title><![CDATA[UPDATE: Secret Spam Message!]]></title>
		    <link><![CDATA[http://consumerist.com/consumer/spam/update-secret-spam-message-166383.php#c98055]]></link>
										
		    <description><![CDATA[.....AOL mail isn't affected, if the mail gets through at all. I've always felt their email module was safer than others. You have to click a special button to even see images and links in a given email. <p>AcidReign</p>]]></description>
			<dc:creator><![CDATA[AcidReign]]></dc:creator>
		    <guid isPermaLink="false"><![CDATA[31:166383:c98055]]></guid>
		    <pubDate><![CDATA[Tue, 11 Apr 2006 18:06:21 EDT]]></pubDate>
		</item>
		<item>
		    <title><![CDATA[UPDATE: Secret Spam Message!]]></title>
		    <link><![CDATA[http://consumerist.com/consumer/spam/update-secret-spam-message-166383.php#c97366]]></link>
										
		    <description><![CDATA[The inexplicably large headers are probably deliberate, trying to cause a buffer error by overloading a field that's not intended for tons of data. Your email client craps out, but not before allowing whatever code was supplied in the header to wreak havoc on your system.

Watch your ass. <p>Paul D</p>]]></description>
			<dc:creator><![CDATA[Paul D]]></dc:creator>
		    <guid isPermaLink="false"><![CDATA[31:166383:c97366]]></guid>
		    <pubDate><![CDATA[Tue, 11 Apr 2006 09:25:05 EDT]]></pubDate>
		</item>
		<item>
		    <title><![CDATA[UPDATE: Secret Spam Message!]]></title>
		    <link><![CDATA[http://consumerist.com/consumer/spam/update-secret-spam-message-166383.php#c97343]]></link>
										
		    <description><![CDATA[I use Eudora, and every now and then there's a message that kills it dead too. Since my not-very-1337 anti-spam solution is Mailwasher (old review: <a href="http://www.dansdata.com/mailwasher.htm">http://www.dansdata.com/mailwasher.htm</a> ), I just use that to delete the offending message from the server.

The last time I bothered tracking down why such a crash happened, it was because of an awesomely large header section in the message - which is a double pisser, because any program that "only downloads the headers" can appear to have hung, as it tries to digest N megabytes of freakin' header crap. There are several other "magic cookies" that can thork various mail clients, though. <p><a href="http://www.dansdata.com/">Daniel Rutter</a></p>]]></description>
			<dc:creator><![CDATA[Daniel Rutter]]></dc:creator>
		    <guid isPermaLink="false"><![CDATA[31:166383:c97343]]></guid>
		    <pubDate><![CDATA[Tue, 11 Apr 2006 08:08:18 EDT]]></pubDate>
		</item>
		<item>
		    <title><![CDATA[UPDATE: Secret Spam Message!]]></title>
		    <link><![CDATA[http://consumerist.com/consumer/spam/update-secret-spam-message-166383.php#c97332]]></link>
										
		    <description><![CDATA[I use Eudora, and every now and then there's a message that kills <i>it</i> dead too. Since my not-very-1337 anti-spam solution...</a> ), I just use that to delete the offending message from the server.

The last time I bothered tracking down why such a crash happened, it was because of an awesomely large header section in the message - which is a double pisser, because any program that "only downloads the headers" can <i>appear</i> to have hung, as it tries to digest N megabytes of freakin' header crap. There are several other "magic cookies" that can thork various mail clients, though. <p><a href="http://www.dansdata.com/">Daniel Rutter</a></p>]]></description>
			<dc:creator><![CDATA[Daniel Rutter]]></dc:creator>
		    <guid isPermaLink="false"><![CDATA[31:166383:c97332]]></guid>
		    <pubDate><![CDATA[Tue, 11 Apr 2006 07:27:32 EDT]]></pubDate>
		</item>
	</channel>
</rss>