I recently had a case where a customer was asking how to figure out the mailbox version of a given user using Exchange Web Services (EWS). We noticed there is a node returned in the AutoDiscover response message called ServerVersion, but this value seems pretty opaque. Here’s a snippet from the AutoDiscover POX response from my test server: < Protocol > < Type > EXCH </ Type > < Server > MAILBOXEX7.domain.com </ Server > < ServerDN > /o=First Organization/ou=Exchange

Recently, I helped a customer with an issue where they were wondering if it was essential to set the ToRecipients , CcRecipients , and BccRecipients if they were setting the same values in the MimeContent property when doing a CreateItem call in Exchange Web Services. While trying to test out the scenarios, I thought “maybe it depends on the order of the elements in your <t:Message>. I soon realized that the order of the properties in the <t:Message> node seemed to matter. As it turns

In continuation to my previous post , the customer also had a SMTP Agent that was installed on a Edge Server and did context sensitive email analysis for incoming SMTP messages. In this case only 20 email could be processed by the SMTP Agent. How were the SMTP messages being sent? The customer had a multithreaded application to send out mail. Fortunately, I was able to reproduce this too.In my case when I sent more than 20 mails using a multithreaded application, I ran into the following exception:

I recently ran in an issue where one of my customer was developing a context sensitive email analysis software for MS Exchange 2007. The results of the analysis was used to decide how that email would be dealt with. Due to the complexity of the analysis, the estimated processing time per email was about 15 to 30 seconds. To realize an acceptable throughput of emails per minute, they needed to ensure that the email processing was strongly parallelized. Therefore they encapsulated the analysis itself

In case you missed it, Exchange 2007 SP2 was released this week. There are some cool new features, which the EHLO blog talks about here as well as all the bug fixes etc. One major thing to point out is that we no longer promote X- headers to custom properties on messages – though you can still get to them through the internet transport headers property.

Matt , Rick , and I were working on an issue recently where when an application using EWS would set a contact’s Street address to a value containing a carriage return and line feed, like this: physicalAddress.Street = "1234 56 Ave NE\r\nc/oPatrick Creehan" ; the address card control in Outlook would render it like this: Ugly, right? The problem was that the XMLSerializer would strip out the line feed and leave the carriage return, which the address card didn’t like. We could prove by sending

I recently helped a customer with an issue where they were calling ConfigureMsgService and that call was failing, returning an HRESULT of MAPI_E_INVALID_PARAMETER (0x80070057). After debugging it, we established that the reason that ConfigureMsgService was failing was that the PR_PROFILE_HOME_SERVER_ADDRS property was missing from the profile. Outlook seemed to work fine, logons worked, sending mail worked; it was just that ConfigureMsgService would fail. We tried recreating the profile, but still

According to our documentation , DeleteItem calls should fail with a ErrorStaleObject error when the ChangeKey is not the most recent one. This, however, is not the case. In Exchange 2007, the ChangeKey is completely ignored in DeleteItem calls. This decision was made on the logic that if you are trying to delete an item, chances are you don’t care if you have the most recent copy or not. But, what if you do? You could try doing a GetItem , check the ChangeKey and then call DeleteItem right after,

Want to learn Exchange Web Service but not sure how and from where? Here are the few articles that I share very often with partners and customers who want to learn more about Exchange Web Services. Undoubtedly there is so much information out there and that’s too in such a short span of time. You better start with Inside Exchange Web Services book from MSPRESS and then the rest of the articles can be utilized.   MSPRESS BOOK Inside Microsoft Exchange Web Services http://www.microsoft.com/learning/en/us/books/10724.aspx

First thing first, you should understand that this is NOT SUPPORTED & NOT RECOMMENDED solution by Microsoft. This is just a proof of concept that OWA 2007 can be auto login, if you know the username & password of target account. The approach is simple and took me little reverse engineering or OWA’s login page. Owa login page being HTML does a form submit and post the username/password along with few hidden variables and upon receiving those parameters owaauth.dll generate a cookie, assign