<?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: Microsoft Blacklist Strategy Swaps Accuracy For MS&#8217;s Convenience</title>
	<link>http://www.emailbattles.com/2006/07/11/spam_aaebefcfac_cf/</link>
	<description>Spam, Security, Privacy, Spyware, Phishing &#038; Viruses from the Front Lines.</description>
	<pubDate>Thu, 08 Jan 2009 12:32:02 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.4</generator>

	<item>
		<title>by: CThom</title>
		<link>http://www.emailbattles.com/2006/07/11/spam_aaebefcfac_cf/#comment-1031</link>
		<pubDate>Tue, 11 Jul 2006 13:47:28 +0000</pubDate>
		<guid>http://www.emailbattles.com/2006/07/11/spam_aaebefcfac_cf/#comment-1031</guid>
					<description>Charlie --&gt; check out this EB story --&gt; http://www.emailbattles.com/archive/battles/spam_aaebfdaich_if/.&lt;br&gt; &lt;br&gt; EB's linking to research by CIPHERTRUST. Yuh think they sell THAT spam appliance too??? Sh*thed.</description>
		<content:encoded><![CDATA[<p>Charlie &#8211;> check out this EB story &#8211;> <a href='http://www.emailbattles.com/archive/battles/spam_aaebfdaich_if/.' rel='nofollow'>http://www.emailbattles.com/archive/battles/spam_aaebfdaich_if/.</a></p>
<p> EB&#8217;s linking to research by CIPHERTRUST. Yuh think they sell THAT spam appliance too??? Sh*thed.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: BJ</title>
		<link>http://www.emailbattles.com/2006/07/11/spam_aaebefcfac_cf/#comment-1030</link>
		<pubDate>Tue, 11 Jul 2006 10:17:51 +0000</pubDate>
		<guid>http://www.emailbattles.com/2006/07/11/spam_aaebefcfac_cf/#comment-1030</guid>
					<description>Hi Charlie and Matthias.&lt;br&gt; RE: IMTS *is* greylisting... ridiculous invention of a new term, etc.&lt;br&gt; The "IMTS" process is not conventional greylisting. It differs in important ways. I've added a discussion of the difference to the article. If we called IMTS greylisting, greylisting fanboys would be up in arms. It's up to others to decide whether ITMS or greylisting makes more sense for their needs. &lt;br&gt; &lt;br&gt; Inbound message traffic shaping, by any name, is not suitable for every environment. Neither is greylisting... or blacklists as guardians of the front door.&lt;br&gt; &lt;br&gt; This approach ratchets the risk of losing important communications to a level many may find unacceptable; thus, not suitable for every environment.&lt;br&gt; &lt;br&gt; I'm with Paul Graham. I don't believe it's possible to maintain *wiseness* in a blacklist indefinitely.&lt;br&gt; &lt;br&gt; SPECIAL NOTE TO CHARLIE: Sorry I didn't buy some other email gateway to provide a counterweight for the questionable rationalization behind using blacklists as your front door. Other brands could prove the same point. But doggone it, Charlie, I had a tMI setting on the shelf. What would *you* have used? BTW: Nice technique for diversion from the point of the discussion. I bet it works great on your spouse.</description>
		<content:encoded><![CDATA[<p>Hi Charlie and Matthias.<br /> RE: IMTS *is* greylisting&#8230; ridiculous invention of a new term, etc.<br /> The &#8220;IMTS&#8221; process is not conventional greylisting. It differs in important ways. I&#8217;ve added a discussion of the difference to the article. If we called IMTS greylisting, greylisting fanboys would be up in arms. It&#8217;s up to others to decide whether ITMS or greylisting makes more sense for their needs. </p>
<p> Inbound message traffic shaping, by any name, is not suitable for every environment. Neither is greylisting&#8230; or blacklists as guardians of the front door.</p>
<p> This approach ratchets the risk of losing important communications to a level many may find unacceptable; thus, not suitable for every environment.</p>
<p> I&#8217;m with Paul Graham. I don&#8217;t believe it&#8217;s possible to maintain *wiseness* in a blacklist indefinitely.</p>
<p> SPECIAL NOTE TO CHARLIE: Sorry I didn&#8217;t buy some other email gateway to provide a counterweight for the questionable rationalization behind using blacklists as your front door. Other brands could prove the same point. But doggone it, Charlie, I had a tMI setting on the shelf. What would *you* have used? BTW: Nice technique for diversion from the point of the discussion. I bet it works great on your spouse.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Matthias Leisi</title>
		<link>http://www.emailbattles.com/2006/07/11/spam_aaebefcfac_cf/#comment-1029</link>
		<pubDate>Tue, 11 Jul 2006 09:39:32 +0000</pubDate>
		<guid>http://www.emailbattles.com/2006/07/11/spam_aaebefcfac_cf/#comment-1029</guid>
					<description>"IMTS", as you call it (or "grey-listing" as it is generally referred to) is not a good solution for all situations. &lt;br&gt; &lt;br&gt; Especially if you have a distributed incoming mail setup with multiple mail servers, you effectively go back to a single point of failure -- all machines must share a pool of "seen" sending IP addresses. &lt;br&gt; &lt;br&gt; On the other hand, *wisely* selected blacklists will be both effective and will not jeopardize your careful distributed setup.</description>
		<content:encoded><![CDATA[<p>&#8220;IMTS&#8221;, as you call it (or &#8220;grey-listing&#8221; as it is generally referred to) is not a good solution for all situations. </p>
<p> Especially if you have a distributed incoming mail setup with multiple mail servers, you effectively go back to a single point of failure &#8212; all machines must share a pool of &#8220;seen&#8221; sending IP addresses. </p>
<p> On the other hand, *wisely* selected blacklists will be both effective and will not jeopardize your careful distributed setup.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: mick</title>
		<link>http://www.emailbattles.com/2006/07/11/spam_aaebefcfac_cf/#comment-1028</link>
		<pubDate>Tue, 11 Jul 2006 08:45:33 +0000</pubDate>
		<guid>http://www.emailbattles.com/2006/07/11/spam_aaebefcfac_cf/#comment-1028</guid>
					<description>Charlie,&lt;br&gt; You're a dip****.&lt;br&gt; Were you required to open your wallet to read any of the articles or use any of the free tools on this site? Neither was I.&lt;br&gt; This article is one of the first that I've noticed any product mentioned.</description>
		<content:encoded><![CDATA[<p>Charlie,<br /> You&#8217;re a dip****.<br /> Were you required to open your wallet to read any of the articles or use any of the free tools on this site? Neither was I.<br /> This article is one of the first that I&#8217;ve noticed any product mentioned.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Charlie</title>
		<link>http://www.emailbattles.com/2006/07/11/spam_aaebefcfac_cf/#comment-1027</link>
		<pubDate>Mon, 10 Jul 2006 21:33:12 +0000</pubDate>
		<guid>http://www.emailbattles.com/2006/07/11/spam_aaebefcfac_cf/#comment-1027</guid>
					<description>I was about to comment on this article's ridiculous invention of a new term to describe greylisting ... until I noticed that this is a marketing site from a mail appliance vendor.</description>
		<content:encoded><![CDATA[<p>I was about to comment on this article&#8217;s ridiculous invention of a new term to describe greylisting &#8230; until I noticed that this is a marketing site from a mail appliance vendor.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Wally</title>
		<link>http://www.emailbattles.com/2006/07/11/spam_aaebefcfac_cf/#comment-1026</link>
		<pubDate>Mon, 10 Jul 2006 19:09:02 +0000</pubDate>
		<guid>http://www.emailbattles.com/2006/07/11/spam_aaebefcfac_cf/#comment-1026</guid>
					<description>MS Rule of Order:&lt;br&gt; 1. ms  &lt;br&gt; 2. ms &lt;br&gt; 3. ms&lt;br&gt; 4. ms&lt;br&gt; 5. johns &lt;br&gt; what did you expect?</description>
		<content:encoded><![CDATA[<p>MS Rule of Order:<br /> 1. ms  <br /> 2. ms <br /> 3. ms<br /> 4. ms<br /> 5. johns <br /> what did you expect?
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
