{"id":137,"date":"2003-08-24T21:13:00","date_gmt":"2003-08-24T11:13:00","guid":{"rendered":"http:\/\/www.erisian.com.au\/wordpress\/?p=137"},"modified":"2003-08-24T21:13:00","modified_gmt":"2003-08-24T11:13:00","slug":"anger-management","status":"publish","type":"post","link":"https:\/\/www.erisian.com.au\/wordpress\/2003\/08\/24\/anger-management","title":{"rendered":"Anger Management"},"content":{"rendered":"<p>The inimitable <a href=\"http:\/\/www.instapundit.com\/\">White Glenn<\/a> received one of those <a href=\"http:\/\/www.instapundit.com\/archives\/011154.php\">obnoxious confirmation-bounces<\/a> anti-spam software occassionally does these days. As a man of good taste and high ideals, he didn&#8217;t like it. How to avoid this problem with our hypothetical $MTP protocol? The only possibility I can see is over analysing all our email &#8212; if you get a reply with an In-Response-To: header matching an email you sent, or one whose From: and Subject: match a To:\/Subject: you&#8217;ve sent.<\/p>\n<p><b>UPDATE 2003\/08\/26:<\/b><\/p>\n<p><a href=\"http:\/\/tmda.net\/\">TMDA<\/a> does some of <a href=\"http:\/\/tmda.net\/faq.cgi?req=show&amp;file=faq05.005.htp\">this sort of stuff<\/a>, apparently. Alone, though, it&#8217;s just increasing the <a href=\"http:\/\/tmda.net\/faq.cgi?req=show&amp;file=faq01.001.htp\">arms race<\/a>.<\/p>\n<p><b>UPDATE 2003\/08\/26:<\/b><\/p>\n<p><a href=\"http:\/\/bugs.debian.org\/cgi-bin\/bugreport.cgi?archive=no&amp;bug=207300\">Some more<\/a> on why email challenges suck. A promising comment from that:<\/p>\n<blockquote>\n<p>Any effective spam remedy must attack one or the other side (or both) of this equation: raise the costs or reduce the technological effectiveness, on the one side, or reduce revenues on the other.<\/p>\n<\/blockquote>\n","protected":false},"excerpt":{"rendered":"<p>The inimitable White Glenn received one of those obnoxious confirmation-bounces anti-spam software occassionally does these days. As a man of good taste and high ideals, he didn&#8217;t like it. How to avoid this problem with our hypothetical $MTP protocol? The only possibility I can see is over analysing all our email &#8212; if you get [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[5],"tags":[],"_links":{"self":[{"href":"https:\/\/www.erisian.com.au\/wordpress\/wp-json\/wp\/v2\/posts\/137"}],"collection":[{"href":"https:\/\/www.erisian.com.au\/wordpress\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.erisian.com.au\/wordpress\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.erisian.com.au\/wordpress\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.erisian.com.au\/wordpress\/wp-json\/wp\/v2\/comments?post=137"}],"version-history":[{"count":0,"href":"https:\/\/www.erisian.com.au\/wordpress\/wp-json\/wp\/v2\/posts\/137\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.erisian.com.au\/wordpress\/wp-json\/wp\/v2\/media?parent=137"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.erisian.com.au\/wordpress\/wp-json\/wp\/v2\/categories?post=137"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.erisian.com.au\/wordpress\/wp-json\/wp\/v2\/tags?post=137"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}