Skip to main content

Mail Enabling a Public folder via MAPI and WebDAV

I’ve had a few questions from people recently asking about the different methods you can mail enable a folder when your running Exchange 2003 in Native Mode. The standard method for mail enabling objects programmatically is to use CDOEXM and the IRecipient Interface . To mail enable a public folder you need to combine this with a little CDOEX like this

FolderURL = "http://server/public/folder/"
set objFolder1 = createobject("CDO.Folder")
objFolder1.DataSource.Open FolderURL, , 3,-1
Set objRecip1 =
objFolder1.Getinterface("IMailRecipient")
objRecip1.MailEnable
objFolder1.DataSource.Save

Now because this uses CDOEX which runs over Exoledb it will only work locally on an Exchange server. To do this remotely you can use the Exchange_PublicFolder WMI class I posted a sample of doing the here previously.

I was curious at the way Exchange System Manger went about mail enabling folders when you where using this on a remote machine as this obviously wasn’t using CDOEX. I did some network captures on a remote machine and the only conversation that the remote machine was having with any server when mailenabling a folder was that it was doing a proppatch on two properties on the public folder via webdav. There was no discernable LDAP traffic at all. I decided to give that go in script myself on a non enabled public folder to see if this would mail enable it and it seemed to work just fine and the RUS seemed to be happy enough to populate the email address’s and also deal with the directory object in Active Directory. I tried the same thing with a CDO script that created a new public folder in the root and mail enabled it via setting these two mapi properties and it seemed to work equally as well.

Now wether this method would be a supported way to mail enable public folders I don’t know it does seem to be how ESM is doing it. There’s also a little more discussion in a recent post on the Exchange Team blog and also in the following KB .

The two properties in question are

PR_PUBLISH_IN_ADDRESS_BOOK = &H3FE6000B
PR_PF_PROXY_REQUIRED = &H671F000B

I’ve only tested this on Exchange 2003 in Native mode as I said this is probably unsupported but the WebDAV to do this would look like

server = "server"
folderpath = "folder"
sDestinationURL = "http://" & server & "/public/" & folderpath & "/"
xmlstr = "<?xml version=""1.0"" ?><a:propertyupdate xmlns:a=""DAV:"" xmlns:b=""urn:schemas-microsoft-com:datatypes""
" _
& "xmlns:c=""xml:"" xmlns:d=""http://schemas.microsoft.com/mapi/proptag/"" " _
& "xmlns:e=""http://schemas.microsoft.com/exchange/events/"" xmlns:f=""http://schemas.microsoft.com/exchange/"">
" _
& "<a:set><a:prop>" _
& "<d:0x3FE6000B b:dt=""boolean"">1</d:0x3FE6000B>" _
& "<d:0x671F000B b:dt=""boolean"">1</d:0x671F000B>" _
& "</a:prop></a:set></a:propertyupdate>"
Set XMLreq = CreateObject("Microsoft.xmlhttp")
XMLreq.open "PROPPATCH", sDestinationURL, False
XMLreq.setRequestHeader "Content-Type", "text/xml;"
XMLreq.setRequestHeader "Translate", "f"
XMLreq.setRequestHeader "Content-Length:", Len(xmlstr)
XMLreq.send(xmlstr)
If (XMLreq.Status >= 200 And XMLreq.Status < 300) Then
Wscript.echo "Success! " & "Results = " & XMLreq.Status & ": " &
XMLreq.statusText
ElseIf XMLreq.Status = 401 then
Wscript.echo "You don't have permission to do the job! Please check your
permissions on this item."
Else
Wscript.echo "Request Failed. Results = " & XMLreq.Status & ": " &
XMLreq.statusText
End If


A CDO example would look like.

MailServer = "servername"
Mailbox = "mailbox"
PR_PUBLISH_IN_ADDRESS_BOOK = &H3FE6000B
PR_PF_PROXY_REQUIRED = &H671F000B
set objSession = CreateObject("MAPI.Session")
strProfile = MailServer & vbLf & Mailbox
objSession.Logon "",,, False,, True, strProfile
Set objInfoStores = objSession.InfoStores
set objInfoStore = objSession.GetInfoStore
Set objpubstore = objSession.InfoStores("Public Folders")
Set objTopFolder = objSession.GetFolder(objpubstore.Fields(&H66310102),objpubstore.ID)
Set objFolder = objTopFolder.Folders.Add("YellowCab1")
Set objFields = objFolder.Fields
objfields.add PR_PUBLISH_IN_ADDRESS_BOOK, true
objfields.add PR_PF_PROXY_REQUIRED, true
objFolder.Update

Popular posts from this blog

The MailboxConcurrency limit and using Batching in the Microsoft Graph API

If your getting an error such as Application is over its MailboxConcurrency limit while using the Microsoft Graph API this post may help you understand why. Background   The Mailbox  concurrency limit when your using the Graph API is 4 as per https://docs.microsoft.com/en-us/graph/throttling#outlook-service-limits . This is evaluated for each app ID and mailbox combination so this means you can have different apps running under the same credentials and the poor behavior of one won't cause the other to be throttled. If you compared that to EWS you could have up to 27 concurrent connections but they are shared across all apps on a first come first served basis. Batching Batching in the Graph API is a way of combining multiple requests into a single HTTP request. Batching in the Exchange Mail API's EWS and MAPI has been around for a long time and its common, for email Apps to process large numbers of smaller items for a variety of reasons.  Batching in the Graph is limited to a m
Read more

Sending a Message in Exchange Online via REST from an Arduino MKR1000

This is part 2 of my MKR1000 article, in this previous post  I looked at sending a Message via EWS using Basic Authentication.  In this Post I'll look at using the new Outlook REST API  which requires using OAuth authentication to get an Access Token. The prerequisites for this sketch are the same as in the other post with the addition of the ArduinoJson library  https://github.com/bblanchon/ArduinoJson  which is used to parse the Authentication Results to extract the Access Token. Also the SSL certificates for the login.windows.net  and outlook.office365.com need to be uploaded to the devices using the wifi101 Firmware updater. To use Token Authentication you need to register an Application in Azure https://msdn.microsoft.com/en-us/office/office365/howto/add-common-consent-manually  with the Mail.Send permission. The application should be a Native Client app that use the Out of Band Callback urn:ietf:wg:oauth:2.0:oob. You need to authorize it in you tenant (eg build a small ap
Read more

How to test SMTP using Opportunistic TLS with Powershell and grab the public certificate a SMTP server is using

Most email services these day employ Opportunistic TLS when trying to send Messages which means that wherever possible the Messages will be encrypted rather then the plain text legacy of SMTP.  This method was defined in RFC 3207 "SMTP Service Extension for Secure SMTP over Transport Layer Security" and  there's a quite a good explanation of Opportunistic TLS on Wikipedia  https://en.wikipedia.org/wiki/Opportunistic_TLS .  This is used for both Server to Server (eg MTA to MTA) and Client to server (Eg a Message client like Outlook which acts as a MSA) the later being generally Authenticated. Basically it allows you to have a normal plain text SMTP conversation that is then upgraded to TLS using the STARTTLS verb. Not all servers will support this verb so if its not supported then a message is just sent as Plain text. TLS relies on PKI certificates and the administrative issue s that come around certificate management like expired certificates which is why I wrote th
Read more
All sample scripts and source code is provided by for illustrative purposes only. All examples are untested in different environments and therefore, I cannot guarantee or imply reliability, serviceability, or function of these programs.

All code contained herein is provided to you "AS IS" without any warranties of any kind. The implied warranties of non-infringement, merchantability and fitness for a particular purpose are expressly disclaimed.