<?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"
	>
<channel>
	<title>Comments on: Spamfilters are stupid</title>
	<atom:link href="http://blog.wordtothewise.com/2007/11/spamfilters-are-stupid/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.wordtothewise.com/2007/11/spamfilters-are-stupid/</link>
	<description>Spam, delivery, email and more</description>
	<pubDate>Tue, 06 Jan 2009 08:06:59 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: steve</title>
		<link>http://blog.wordtothewise.com/2007/11/spamfilters-are-stupid/#comment-317</link>
		<dc:creator>steve</dc:creator>
		<pubDate>Tue, 13 Nov 2007 20:44:57 +0000</pubDate>
		<guid isPermaLink="false">http://blog.wordtothewise.com/index.php/2007/11/12/spamfilters-are-stupid/#comment-317</guid>
		<description>Idempotent just means that following a link twice has exactly the same effect on persistent state as clicking it once. It does not mean that following the link must not change state, just that after following it once, following it again must not change state further.

There are good reasons to avoid GET requests for changing state, but that's not what idempotent means.

Two step unsubscribe, where the link in the email goes to a webpage with a prominent "click here to unsubscribe" button is often a good thing for unsubscription. It also gives people an option to not unsubscribe, when they click on the wrong link, or hit "return" with the wrong link focused, in a mail inadvertently, which isn't that unusual in link-laden emails.

As for closed-loop opt-in... if someone is mailed a magic cookie that must be returned in order to subscribe them to a mailing list, and they give permission to others to use that cookie by posting the cookie somewhere public I have very little sympathy when those people they've delegated responsibility to use the cookie to add them to a mailing list. Installing software that automatically clicks on links in their inbound email isn't quite the same, but I still won't have any sympathy for the recipient (I'll reserve that sympathy for the mailer who'll later have to put up with frivolous spam complaints from the recipient).</description>
		<content:encoded><![CDATA[<p>Idempotent just means that following a link twice has exactly the same effect on persistent state as clicking it once. It does not mean that following the link must not change state, just that after following it once, following it again must not change state further.</p>
<p>There are good reasons to avoid GET requests for changing state, but that&#8217;s not what idempotent means.</p>
<p>Two step unsubscribe, where the link in the email goes to a webpage with a prominent &#8220;click here to unsubscribe&#8221; button is often a good thing for unsubscription. It also gives people an option to not unsubscribe, when they click on the wrong link, or hit &#8220;return&#8221; with the wrong link focused, in a mail inadvertently, which isn&#8217;t that unusual in link-laden emails.</p>
<p>As for closed-loop opt-in&#8230; if someone is mailed a magic cookie that must be returned in order to subscribe them to a mailing list, and they give permission to others to use that cookie by posting the cookie somewhere public I have very little sympathy when those people they&#8217;ve delegated responsibility to use the cookie to add them to a mailing list. Installing software that automatically clicks on links in their inbound email isn&#8217;t quite the same, but I still won&#8217;t have any sympathy for the recipient (I&#8217;ll reserve that sympathy for the mailer who&#8217;ll later have to put up with frivolous spam complaints from the recipient).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Justin</title>
		<link>http://blog.wordtothewise.com/2007/11/spamfilters-are-stupid/#comment-316</link>
		<dc:creator>Justin</dc:creator>
		<pubDate>Tue, 13 Nov 2007 20:19:33 +0000</pubDate>
		<guid isPermaLink="false">http://blog.wordtothewise.com/index.php/2007/11/12/spamfilters-are-stupid/#comment-316</guid>
		<description>So long as the filters are only using GET requests to pull down links, there's nothing fundamentally wrong with them. It's a basic (though oft-ignored) tenet of web development that GET requests should be idempotent; that is, they shouldn't somehow change anything important on the server. That's what POST is for.

A lot of people ignore this for convenience's sake, but this is just one way that you can get bitten. Anyone remember the Google Web Accelerator that came out a while ago, then promptly disappeared? It'd pre-fetch links on a page to speed up things if you clicked them later on. And if one of those links happened to delete something from a blog, or log you out... well, then you begin to see why GET shouldn't change things.

So yes, the perfect solution to this is a 2-step unsubscribe link: the first step takes to you a page with a form on it, and that form then POSTs something back that finalizes the unsubscribe request.

Tracking links, unfortunately, would need some other solution...</description>
		<content:encoded><![CDATA[<p>So long as the filters are only using GET requests to pull down links, there&#8217;s nothing fundamentally wrong with them. It&#8217;s a basic (though oft-ignored) tenet of web development that GET requests should be idempotent; that is, they shouldn&#8217;t somehow change anything important on the server. That&#8217;s what POST is for.</p>
<p>A lot of people ignore this for convenience&#8217;s sake, but this is just one way that you can get bitten. Anyone remember the Google Web Accelerator that came out a while ago, then promptly disappeared? It&#8217;d pre-fetch links on a page to speed up things if you clicked them later on. And if one of those links happened to delete something from a blog, or log you out&#8230; well, then you begin to see why GET shouldn&#8217;t change things.</p>
<p>So yes, the perfect solution to this is a 2-step unsubscribe link: the first step takes to you a page with a form on it, and that form then POSTs something back that finalizes the unsubscribe request.</p>
<p>Tracking links, unfortunately, would need some other solution&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tim England</title>
		<link>http://blog.wordtothewise.com/2007/11/spamfilters-are-stupid/#comment-314</link>
		<dc:creator>Tim England</dc:creator>
		<pubDate>Tue, 13 Nov 2007 17:58:41 +0000</pubDate>
		<guid isPermaLink="false">http://blog.wordtothewise.com/index.php/2007/11/12/spamfilters-are-stupid/#comment-314</guid>
		<description>I had a couple of questions about this.  Do you have any information on which filters are clicking on links?  What ramifications does this have on spam traps?  If they are showing activity and possibly confirming, it could be difficult to know that you are sending email only to subscribers that want it.</description>
		<content:encoded><![CDATA[<p>I had a couple of questions about this.  Do you have any information on which filters are clicking on links?  What ramifications does this have on spam traps?  If they are showing activity and possibly confirming, it could be difficult to know that you are sending email only to subscribers that want it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Why Anti-Spam Filters Can Affect Opt-ins, Opt-outs and Metrics : The Messaging Times</title>
		<link>http://blog.wordtothewise.com/2007/11/spamfilters-are-stupid/#comment-309</link>
		<dc:creator>Why Anti-Spam Filters Can Affect Opt-ins, Opt-outs and Metrics : The Messaging Times</dc:creator>
		<pubDate>Mon, 12 Nov 2007 23:24:48 +0000</pubDate>
		<guid isPermaLink="false">http://blog.wordtothewise.com/index.php/2007/11/12/spamfilters-are-stupid/#comment-309</guid>
		<description>[...] link. I filed this under &#8220;mildly concerning&#8221; and forgot about it until Laura pointed out that they might equally click on the links in those emails asking folk to confirm their email [...]</description>
		<content:encoded><![CDATA[<p>[...] link. I filed this under &#8220;mildly concerning&#8221; and forgot about it until Laura pointed out that they might equally click on the links in those emails asking folk to confirm their email [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
