The Exchange API team has a new post to explaining the differences between using Exchange Impersonation vs. Delegate Access to access an Exchange mailbox using Exchange Web Services.  I’ve seen first hand that there is a gap in understanding the difference between the two and when to use one versus the other.  This post goes a long way to address some of the confusion. An important note that some people miss is the differentiation between Windows and Exchange impersonation – they’re not

The Exchange team announced the upcoming service pack for Exchange 2007 recently.  The primary focus of this service pack is preparing Exchange 2007 for interoperability with Exchange 2010 but there are also fixes and changes to existing components and technologies that make this update worth installing when it comes out.  Here are some developer related points of interest that were announced: “ Exchange Volume Snapshot Backup Functionality - A new backup plug-in has been added to the product

The Exchange team announced that Exchange 2010 will not have a 32-bit version – not even for evaluations. The post focuses on mainly the non-developer related impact of this change. The key points for developers are: > Applications that automate Exchange cmdlets locally will need to be compiled for 64-bit. > 32-bit or 64-bit applications could leverage the remote Powershell capabilities in Powershell 2.0 to invoke the Exchange cmdlets remotely.

It took me forever to get around to watching this but this is just a great presentation about Exchange development’s future at PDC. He does a great job of explaining where we’ve been as well… Learn about the Exchange Web Services Managed API and how Exchange is getting “Cloud Ready” at PDC’08 This is an absolute must watch for any Exchange developer!

The Exchange API-spotting blog, which is run by the Exchange MSDN content and Exchange API product  folks, as a new post about the transition from store event sinks to Exchange Web Service notifications .  The aim is to provide some more detail about notifications and try to directly answer some questions that have been posed by developers about how notifications can realistically replace store event sinks when they go away . ...If you have feedback for the product team about the transition

I was reviewing a customer's case today and it reminded me of a topic I meant to blog about a while ago... Ever since Exchange 2000/2003 customers have tried to apply the disclaimer SMTP sink sample to internal mail and found that the disclaimer text is not stamped on these messages.  Of course in Exchange 2000/2003 this won't work .  This is further described in the Exchange 2003 documentation on TechNet about The Advanced Queuing Engine ... "...the CDO interface does not support

Steve posted a link to the MSDN protocol documentation.  He talks about them here and here as well.

Exchange 2007 only adds 64-bit components in a 64-bit install, when you install Exchange it will register CDOEX.DLL which will replace CDOSYS.DLL and be used when you instantiate CDO.Message. So you will see CDO.Message pointing to "C:\Program Files\Common Files\Microsoft Shared\CDO\CDOEX.DLL" in the 64-bit registry and you will see CDO.Message pointing to "C:\WINNT\SysWow64\cdosys.dll" in the 32-bit registry. If your application is a 64-bit process it will load up CDOEX.DLL when you instantiate

...We have had a few customers looking for information on writing a custom foreign connector for Exchange 2007 and I finally got around to combining all my information into one document so that I could reuse it. I thought I would share it here as well to maybe save a few calls to our team... What is a gateway connector? “Gateway connectors generally use non-standard protocols, or proprietary APIs to connect Exchange to non-Exchange messaging systems” – [TechNet]Gateway Messaging Connectors Architecture

Reading this kind of stuff almost makes we wish I was a consultant again...I say almost because then I think about requirement gathering, deadlines, budgets, debating the merits of agile development, etc... The Exchange SDK team linked to this article on their blog the other day and I just had a chance to read through it. Exchange development seems like such a niche expertise sometimes and in the past the "tribal" knowledge it took to understand how to work with and extract data from Exchange could