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 Gr...
Read more

Sending a MimeMessage via the Microsoft Graph using the Graph SDK, MimeKit and MSAL

One of the new features added to the Microsoft Graph recently was the ability to create and send Mime Messages (you have been able to get Message as Mime for a while). This is useful in a number of different scenarios especially when trying to create a Message with inline Images which has historically been hard to do with both the Graph and EWS (if you don't use MIME). It also opens up using SMIME for encryption and a more easy migration path for sending using SMTP in some apps. MimeKit is a great open source library for parsing and creating MIME messages so it offers a really easy solution for tackling this issue. The current documentation on Send message via MIME lacks any real sample so I've put together a quick console app that use MSAL, MIME kit and the Graph SDK to send a Message via MIME. As the current Graph SDK also doesn't support sending via MIME either there is a workaround for this in the future my guess is this will be supported.
Read more

Export calendar Items to a CSV file using Microsoft Graph and Powershell

For the last couple of years the most constantly popular post by number of views on this blog has been  Export calendar Items to a CSV file using EWS and Powershell closely followed by the contact exports scripts. It goes to show this is just a perennial issue that exists around Mail servers, I think the first VBS script I wrote to do this type of thing was late 90's against Exchange 5.5 using cdo 1.2. Now it's 2020 and if your running Office365 you should really be using the Microsoft Graph API to do this. So what I've done is create a PowerShell Module (and I made it a one file script for those that are more comfortable with that format) that's a port of the EWS script above that is so popular. This script uses the ADAL library for Modern Authentication (which if you grab the library from the PowerShell gallery will come down with the module). Most EWS properties map one to one with the Graph and the Graph actually provides better information on recurrences then...
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.