<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: BDAT causing SMTP service to drop Email</title>
	<atom:link href="http://joekiller.com/2007/09/19/bdat-causing-smtp-service-to-drop-email/feed/" rel="self" type="application/rss+xml" />
	<link>http://joekiller.com/2007/09/19/bdat-causing-smtp-service-to-drop-email/</link>
	<description>Music.Life.Tech.Charlottesville</description>
	<lastBuildDate>Wed, 12 Aug 2009 14:16:11 -0400</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Joe</title>
		<link>http://joekiller.com/2007/09/19/bdat-causing-smtp-service-to-drop-email/comment-page-1/#comment-3697</link>
		<dc:creator>Joe</dc:creator>
		<pubDate>Wed, 12 Aug 2009 14:16:11 +0000</pubDate>
		<guid isPermaLink="false">http://joekiller.com/?p=96#comment-3697</guid>
		<description>Hi Alan,

I think you will be safe to subtract out the offending SMTP verbs from the total options.  The KB article only focuses on a limited subset of the SMTP commands that IIS&#039; SMTP service offers.  In any case, since they are tied to specific hex values, subtracting out the ones you want to turn off will turn those off.  I would suggest writing down the original just in case things don&#039;t go as planned.  We dumped the product after we fixed this problem due to the slowdown it caused in the mail queue. 

Good luck!

-Joe</description>
		<content:encoded><![CDATA[<p>Hi Alan,</p>
<p>I think you will be safe to subtract out the offending SMTP verbs from the total options.  The KB article only focuses on a limited subset of the SMTP commands that IIS&#8217; SMTP service offers.  In any case, since they are tied to specific hex values, subtracting out the ones you want to turn off will turn those off.  I would suggest writing down the original just in case things don&#8217;t go as planned.  We dumped the product after we fixed this problem due to the slowdown it caused in the mail queue. </p>
<p>Good luck!</p>
<p>-Joe</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alan</title>
		<link>http://joekiller.com/2007/09/19/bdat-causing-smtp-service-to-drop-email/comment-page-1/#comment-3695</link>
		<dc:creator>Alan</dc:creator>
		<pubDate>Tue, 11 Aug 2009 22:05:46 +0000</pubDate>
		<guid isPermaLink="false">http://joekiller.com/?p=96#comment-3695</guid>
		<description>I&#039;m having a similar problem, and I found the Symantec SMTP Server with the Metabase Explorer. However, the current value for SmtpInboundCommandSupportOptions is 4546589 and from the MS artile you mention I cannot figure what combination of options is turned on or off from this value. Should I simply subtract the values for Binary and Chunking from this and hope?</description>
		<content:encoded><![CDATA[<p>I&#8217;m having a similar problem, and I found the Symantec SMTP Server with the Metabase Explorer. However, the current value for SmtpInboundCommandSupportOptions is 4546589 and from the MS artile you mention I cannot figure what combination of options is turned on or off from this value. Should I simply subtract the values for Binary and Chunking from this and hope?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Magnus HasselgÃ¥rd</title>
		<link>http://joekiller.com/2007/09/19/bdat-causing-smtp-service-to-drop-email/comment-page-1/#comment-3206</link>
		<dc:creator>Magnus HasselgÃ¥rd</dc:creator>
		<pubDate>Thu, 18 Sep 2008 15:26:19 +0000</pubDate>
		<guid isPermaLink="false">http://joekiller.com/?p=96#comment-3206</guid>
		<description>Excellent!

I was troubleshooting a problem similar to this one back in 2005, but from a client-side perspective. The SMTPSVC running on Windows 2000 Server was getting the exact same treatment when forwarding mails with BDAT to an Exchange 5.0 server. I never did figure out why BDAT had stopped working, but I found a workaround that forced the SMTPSVC service to always use DATA instead: change the MetaBase property /LM/SmtpSvc/SmtpOutboundCommandOptions from &quot;7&quot; (the default) to &quot;5&quot;. Undocumented, but worked like a charm. :)

The problem resurfaced at a different installation this week, with Windows 2003 Server and Exhange 6. Now I can tell the Exhange administrators there to take a closer look at their security software - _it_ could actually be dropping BDAT connections, like you describe.

Thanks!

-m-</description>
		<content:encoded><![CDATA[<p>Excellent!</p>
<p>I was troubleshooting a problem similar to this one back in 2005, but from a client-side perspective. The SMTPSVC running on Windows 2000 Server was getting the exact same treatment when forwarding mails with BDAT to an Exchange 5.0 server. I never did figure out why BDAT had stopped working, but I found a workaround that forced the SMTPSVC service to always use DATA instead: change the MetaBase property /LM/SmtpSvc/SmtpOutboundCommandOptions from &#8220;7&#8243; (the default) to &#8220;5&#8243;. Undocumented, but worked like a charm. :)</p>
<p>The problem resurfaced at a different installation this week, with Windows 2003 Server and Exhange 6. Now I can tell the Exhange administrators there to take a closer look at their security software &#8211; _it_ could actually be dropping BDAT connections, like you describe.</p>
<p>Thanks!</p>
<p>-m-</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Duane Gran</title>
		<link>http://joekiller.com/2007/09/19/bdat-causing-smtp-service-to-drop-email/comment-page-1/#comment-2291</link>
		<dc:creator>Duane Gran</dc:creator>
		<pubDate>Thu, 20 Sep 2007 19:13:58 +0000</pubDate>
		<guid isPermaLink="false">http://joekiller.com/?p=96#comment-2291</guid>
		<description>This is somewhat prophetic, as I am troubleshooting an issue with our Exchange mail server that seems very similar to this.  Thank you for offering up the notes on your experiences.</description>
		<content:encoded><![CDATA[<p>This is somewhat prophetic, as I am troubleshooting an issue with our Exchange mail server that seems very similar to this.  Thank you for offering up the notes on your experiences.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
