<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.technet.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>SMTP Session Tarpitting for Windows 2003 and Exchange</title><link>http://blogs.technet.com/exchange/archive/2004/12/06/275851.aspx</link><description>A common strategy for increasing the cost of would-be mail abuse uses a technique called tarpitting. Mail servers that tarpit wait a specified period of time before issuing SMTP responses to the client, thus increasing the time investment needed to successfully</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: SMTP Session Tarpitting for Windows 2003 and Exchange</title><link>http://blogs.technet.com/exchange/archive/2004/12/06/275851.aspx#275890</link><pubDate>Mon, 06 Dec 2004 20:51:00 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:275890</guid><dc:creator>Michel</dc:creator><description>Excellent work!&lt;br&gt;&lt;br&gt;I had a discussion almost one year ago with David Lemson (URL points to the post on his weblog) about this specific feature. It fired discussions on how MS decides and knows about user feature requests. Tarpitting was one of those features I requested: now it's here!&lt;br&gt;&lt;br&gt;I mentioned in previous posts on David's blog there was (and still is) a content scanning gateway in front of our Exchange organisation. I already have plans layed out to change that: have Exchange use IMF (recipient check), tarpit when needed, and then route back to the content scanning gateway. After the content scan messages will flow into the Exchange org again. &lt;br&gt;&lt;br&gt;Great to see this feature in the SMTP service!</description></item><item><title>re: SMTP Session Tarpitting for Windows 2003 and Exchange</title><link>http://blogs.technet.com/exchange/archive/2004/12/06/275851.aspx#275907</link><pubDate>Mon, 06 Dec 2004 21:15:00 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:275907</guid><dc:creator>Dmitry Gromov</dc:creator><description>Hi!&lt;br&gt;&lt;br&gt;That article is incorrect. Hotfix DOES NOT install Tarpit fix on Windowss 2003 unless _original_ KB842851 was installed.&lt;br&gt;&lt;br&gt;WindowsServer2003-KB885881-x86-enu.EXE includes two versions of smtp.dll - GDR (for RTM versions) and QFE (for hotfix version). ONLY QFE version of smtp.dll has Tarpit fix. RTM version does not.&lt;br&gt;&lt;br&gt;If original KB842851 fix (available from MS) was not installed, it is still possible to replace smtp.dll but that is not supported, of cause.&lt;br&gt;&lt;br&gt;And the way it works is very simple - it times out SMTP response if reply is not in 250 status. Works perfectly with plain SMTP service and some other sink-based spam filters.&lt;br&gt;</description></item><item><title>When "it's the pits" is actually GOOD</title><link>http://blogs.technet.com/exchange/archive/2004/12/06/275851.aspx#275928</link><pubDate>Tue, 07 Dec 2004 00:39:00 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:275928</guid><dc:creator>Exchange Security</dc:creator><description>&amp;lt;p&amp;gt;&lt;br&gt;Microsoft today released a hotfix for the Windows 2003 SMTP stack that provides tarpitting for SMTP....  The idea is that you install software that intentionally slows down SMTP throughput for bogus requests.&lt;br&gt;&amp;lt;/p&amp;gt;</description></item><item><title>re: SMTP Session Tarpitting for Windows 2003 and Exchange</title><link>http://blogs.technet.com/exchange/archive/2004/12/06/275851.aspx#277523</link><pubDate>Tue, 07 Dec 2004 10:49:00 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:277523</guid><dc:creator>Bernd Kruczek</dc:creator><description>Great! But what value for tar pit would be the best?</description></item><item><title>re: SMTP Session Tarpitting for Windows 2003 and Exchange</title><link>http://blogs.technet.com/exchange/archive/2004/12/06/275851.aspx#277689</link><pubDate>Tue, 07 Dec 2004 17:36:00 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:277689</guid><dc:creator>Nino Bilic</dc:creator><description>Dmitry,&lt;br&gt;&lt;br&gt;You are correct - I fixed the main post. Thanks for keeping us honest! :)</description></item><item><title>re: SMTP Session Tarpitting for Windows 2003 and Exchange</title><link>http://blogs.technet.com/exchange/archive/2004/12/06/275851.aspx#277690</link><pubDate>Tue, 07 Dec 2004 17:36:00 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:277690</guid><dc:creator>Peter</dc:creator><description>This sounds like a good idea but does it really work?  Since address harvesting is automated would anyone really notice or care if a certain domain took longer than another?</description></item><item><title>re: SMTP Session Tarpitting for Windows 2003 and Exchange</title><link>http://blogs.technet.com/exchange/archive/2004/12/06/275851.aspx#277748</link><pubDate>Tue, 07 Dec 2004 18:38:00 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:277748</guid><dc:creator>Greg</dc:creator><description>Thanks for the feedback, all!&lt;br&gt;&lt;br&gt;Peter: You are right in that tarpitting is not an end-all technique for stopping attacks. But raising the cost of an attack helps deter some of them and draws out the others such that a diligant administrator may have measures to detect the traffic and block the IP. So to answer your question, I'd argue that a e-mail organization whose accounts are being harvested would indeed care if it took longer to extract useful information, partially because it increases the chance that it can be detected and corrective measures to be taken.&lt;br&gt;&lt;br&gt;Tarpitting isn't a replacement for, just something to be used in conjunction with other techniques such as limiting the number of connections per IP/Domain, RBL, address filtering, and traffic monitoring. As some of you might have guessed, there are scenarios where harvesting or mail abuse attacks can span multiple connections, sometimes from a distributed source. These scenarios should be considered as well.&lt;br&gt;&lt;br&gt;Bernd, this is a very good question. A common number is about 5 seconds. However, if you are a gateway and you are confident that a large number of SMTP protocol errors your servers issue are due to one form of other of abuse, this value can certainly be increased. Keep in mind that a lot of mail servers and clients have a time limit associated with a SMTP session after which it may time out, so this should not be a very, very large value.</description></item><item><title> SMTP Tarpitting</title><link>http://blogs.technet.com/exchange/archive/2004/12/06/275851.aspx#277843</link><pubDate>Tue, 07 Dec 2004 20:25:00 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:277843</guid><dc:creator>Peter Schmidt</dc:creator><description>Referred on &lt;a target="_new" href="http://www.exchange-digest.com"&gt;http://www.exchange-digest.com&lt;/a&gt;.</description></item><item><title>re: SMTP Session Tarpitting for Windows 2003 and Exchange</title><link>http://blogs.technet.com/exchange/archive/2004/12/06/275851.aspx#278047</link><pubDate>Wed, 08 Dec 2004 03:56:00 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:278047</guid><dc:creator>Dmitry Gromov</dc:creator><description>Cool!&lt;br&gt;&lt;br&gt;Thanks for updating post... Would be great if KB article gets updated too ;-)&lt;br&gt;&lt;br&gt;As for time setting, I'd suggest more like 30 sec. At least MS SMTP connection timeout is 10 min and other servers usually don't have it less then 1 min.&lt;br&gt;&lt;br&gt;I'm planning to elaborate on this more in my blog soon...&lt;br&gt;</description></item><item><title>re: SMTP Session Tarpitting for Windows 2003 and Exchange</title><link>http://blogs.technet.com/exchange/archive/2004/12/06/275851.aspx#279147</link><pubDate>Thu, 09 Dec 2004 21:48:00 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:279147</guid><dc:creator>Paul Robichaux</dc:creator><description>It looks like you only have to install the 885881 hotfix, then follow the directions in 842851 to configure tarpitting. Is that correct, or did I miss something subtle in one of the articles?</description></item><item><title>re: SMTP Session Tarpitting for Windows 2003 and Exchange</title><link>http://blogs.technet.com/exchange/archive/2004/12/06/275851.aspx#300066</link><pubDate>Tue, 14 Dec 2004 14:40:00 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:300066</guid><dc:creator>Reto</dc:creator><description>I've just installed package 885881, made the modification to the registry &amp;amp; restarted the smtp-servcie.&lt;br&gt;After that, people from outside the ex-org were unable to sent any e-mail to any ex-recipients. Everybody got an ndr, that states an authenticaion-error.&lt;br&gt;Does anybody encounter similar troubles?&lt;br&gt;</description></item><item><title>re: SMTP Session Tarpitting for Windows 2003 and Exchange</title><link>http://blogs.technet.com/exchange/archive/2004/12/06/275851.aspx#316499</link><pubDate>Thu, 16 Dec 2004 02:57:00 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:316499</guid><dc:creator>Greg</dc:creator><description>To the best of my knowledge, the fix in 885881 should not influence authentication behavior. I'd check your existing authentication settings to see if a setting didn't take and was enacted when you recycled the service... otherwise I'd use message tracking to see where the message is blocked and drill in from there.</description></item><item><title>Messaging Security at Microsoft presentation</title><link>http://blogs.technet.com/exchange/archive/2004/12/06/275851.aspx#356205</link><pubDate>Wed, 19 Jan 2005 21:17:00 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:356205</guid><dc:creator>Eileen Brown's WebLog</dc:creator><description /></item><item><title>re: Messaging Security at Microsoft presentation</title><link>http://blogs.technet.com/exchange/archive/2004/12/06/275851.aspx#356399</link><pubDate>Thu, 20 Jan 2005 01:47:00 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:356399</guid><dc:creator>Eileen Brown's WebLog</dc:creator><description /></item><item><title>Exchange Error 0X8004010F - The Operation failed. An Object could not be found</title><link>http://blogs.technet.com/exchange/archive/2004/12/06/275851.aspx#375372</link><pubDate>Thu, 17 Feb 2005 19:59:00 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:375372</guid><dc:creator>Eileen Brown's WebLog</dc:creator><description /></item><item><title>What to do in case of.... and </title><link>http://blogs.technet.com/exchange/archive/2004/12/06/275851.aspx#394408</link><pubDate>Sat, 12 Mar 2005 10:06:00 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:394408</guid><dc:creator>E-Bitz - SBS MVP the Official Blog of the SBS </dc:creator><description /></item><item><title>What to do in case of.... and </title><link>http://blogs.technet.com/exchange/archive/2004/12/06/275851.aspx#394411</link><pubDate>Sat, 12 Mar 2005 10:08:00 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:394411</guid><dc:creator>E-Bitz - SBS MVP the Official Blog of the SBS </dc:creator><description /></item><item><title>Microsoft Security Advisory (842851)</title><link>http://blogs.technet.com/exchange/archive/2004/12/06/275851.aspx#404954</link><pubDate>Mon, 16 May 2005 12:30:22 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:404954</guid><dc:creator>subject: exchange</dc:creator><description /></item><item><title>Microsoft Security Advisory (842851)</title><link>http://blogs.technet.com/exchange/archive/2004/12/06/275851.aspx#404955</link><pubDate>Mon, 16 May 2005 12:33:06 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:404955</guid><dc:creator>subject: exchange</dc:creator><description /></item><item><title>Approaches to fighting spam in an Exchange environment</title><link>http://blogs.technet.com/exchange/archive/2004/12/06/275851.aspx#406402</link><pubDate>Wed, 15 Jun 2005 12:43:47 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:406402</guid><dc:creator>Eileen Brown's WebLog</dc:creator><description>Greg presented this Technet evening for me last night.&amp;amp;amp;nbsp; The topic was all about fighting spam -...</description></item><item><title>Resources for Webcast - Exchange Server 2003: Tips, Tricks, and Shortcuts (March 24, 2006)</title><link>http://blogs.technet.com/exchange/archive/2004/12/06/275851.aspx#423090</link><pubDate>Fri, 24 Mar 2006 20:36:11 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:423090</guid><dc:creator>Full of I.T.</dc:creator><description>Kevin&amp;amp;amp;rsquo;s Webcast Resources:&lt;br&gt;Exchange Server 2003 &amp;amp;amp;ndash; Tips, Tricks, and Shortcuts&lt;br&gt;Here are...</description></item></channel></rss>