<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.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>mstehle: The CDOs and CDONTS of Messaging Development : MYTH</title><link>http://blogs.msdn.com/mstehle/archive/tags/MYTH/default.aspx</link><description>Tags: MYTH</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>MYTH: SmtpMail.SmtpServer.Insert(0,&amp;quot;127.0.0.1&amp;quot;) Actually Does Something</title><link>http://blogs.msdn.com/mstehle/archive/2005/11/23/myth-smtpmail-smtpserver-insert-0-quot-127-0-0-1-quot-actually-does-something.aspx</link><pubDate>Wed, 23 Nov 2005 22:18:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:496418</guid><dc:creator>mstehle</dc:creator><slash:comments>19</slash:comments><comments>http://blogs.msdn.com/mstehle/comments/496418.aspx</comments><wfw:commentRss>http://blogs.msdn.com/mstehle/commentrss.aspx?PostID=496418</wfw:commentRss><wfw:comment>http://blogs.msdn.com/mstehle/rsscomments.aspx?PostID=496418</wfw:comment><description>One of the principles of the Information Age is that anybody with a blog like mine or a Code Project account can write an article viewable to millions of people around the world.  As a support engineer, I love and hate this at the same time.  Take the following Code Project article for example......(&lt;a href="http://blogs.msdn.com/mstehle/archive/2005/11/23/myth-smtpmail-smtpserver-insert-0-quot-127-0-0-1-quot-actually-does-something.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=496418" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/mstehle/archive/tags/MYTH/default.aspx">MYTH</category><category domain="http://blogs.msdn.com/mstehle/archive/tags/System.Web.Mail/default.aspx">System.Web.Mail</category><category domain="http://blogs.msdn.com/mstehle/archive/tags/DevMsgTeam/default.aspx">DevMsgTeam</category><category domain="http://blogs.msdn.com/mstehle/archive/tags/CDOSYS/default.aspx">CDOSYS</category><category domain="http://blogs.msdn.com/mstehle/archive/tags/CDONTS/default.aspx">CDONTS</category></item><item><title>MYTH: Outlook and Exchange Can Reside on the Same Machine</title><link>http://blogs.msdn.com/mstehle/archive/2005/11/22/myth-outlook-and-exchange-can-reside-on-the-same-machine.aspx</link><pubDate>Tue, 22 Nov 2005 23:44:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:495941</guid><dc:creator>mstehle</dc:creator><slash:comments>2</slash:comments><comments>http://blogs.msdn.com/mstehle/comments/495941.aspx</comments><wfw:commentRss>http://blogs.msdn.com/mstehle/commentrss.aspx?PostID=495941</wfw:commentRss><wfw:comment>http://blogs.msdn.com/mstehle/rsscomments.aspx?PostID=495941</wfw:comment><description>&lt;P&gt;&lt;FONT face=Arial size=2&gt;I had a customer email me today saying they resolved their CDO problem by installing SP 2 on their Exchange server and installing Outlook 2003.&amp;nbsp; Big mistake!&amp;nbsp; It's unfortunate and common but so many people put their Exchange implementations at risk by installing Outlook on top of Exchange.&amp;nbsp; One of our Escalation Engineers, Stephen Griffin, has a great &lt;a href="http://blogs.msdn.com/stephen_griffin/archive/2004/07/03/172257.aspx"&gt;post&lt;/A&gt; and &lt;a href="http://blogs.msdn.com/stephen_griffin/archive/0001/01/01/215939.aspx"&gt;follow up&lt;/A&gt; on the subject.&amp;nbsp; Exchange and Outlook both have their own versions of CDO and MAPI.&amp;nbsp; When you install Exchange on top of Outlook or Outlook on top of Exchange you are essentially mixing and matching these libraries and their underlying subsystems.&amp;nbsp; This scenario is not supported by PSS and if you have problems with code running on a server with Outlook and Exchange we can't help you.&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;FONT face=Arial size=2&gt;&lt;EM&gt;...Don't get me wrong, the implementations are similar enough that you might not see any noticeable failures initially.&amp;nbsp; In fact, many have argued that they have a machine running for X number of days just fine and see no reason why you can't have both installed.&amp;nbsp; Take a look at Stephen's article, there are interfaces not implemented in the Outlook version that are implemented in the Exchange and vice versa.&amp;nbsp; As soon as you or Outlook or Exchange try to use one of those interfaces you will know why you shouldn't have both applications installed on the same box.&lt;/EM&gt;&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;&lt;FONT face=Arial size=2&gt;...A common and related issue is copying the server CDO 1.21 library to a non-Exchange server or client to get around the client version's security &lt;A href="http://support.microsoft.com/kb/295302/"&gt;prompts&lt;/A&gt;.&amp;nbsp; This is not a supported solution for the same reason Exchange and Outlook can't coexist.&lt;/FONT&gt;&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;&lt;FONT face=Arial size=2&gt;...Here is the KB article on the same issue, &lt;A href="http://support.microsoft.com/default.aspx?scid=kb;en-us;q266418"&gt;http://support.microsoft.com/default.aspx?scid=kb;en-us;q266418&lt;/A&gt;&lt;/FONT&gt;&lt;/EM&gt;&lt;/P&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=495941" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/mstehle/archive/tags/MYTH/default.aspx">MYTH</category><category domain="http://blogs.msdn.com/mstehle/archive/tags/MAPI/default.aspx">MAPI</category><category domain="http://blogs.msdn.com/mstehle/archive/tags/Exchange+General/default.aspx">Exchange General</category><category domain="http://blogs.msdn.com/mstehle/archive/tags/Outlook+General/default.aspx">Outlook General</category><category domain="http://blogs.msdn.com/mstehle/archive/tags/DevMsgTeam/default.aspx">DevMsgTeam</category></item></channel></rss>