Skip to main content

Add a Picture to Contact in Outlook 2003 via Script

I'm currently writing some code for an event sink that will convert a Vcard attached to a message into a contact in a public folder. Mostly the Vcards that I want to import are from the Palm desktop software which allows you to add images into the contact similar to the new functionality added to Outlook 2003. So as part of my code I had to come up with something that would decode the picture from the vcard file and then add it to the contact in a way Outlook 2003 would understand it. Although I haven't quite finish the vcard code i thought this was worth a separate post.

Basically to add a picture to a contact in Outlook you need to first have the file in jpg format and the name of the file your going to attachment must be ContactPicture.jpg. Once you have attached that file you then need to modify/Add 2 properties on that attachment itself. The only API that you can use to successfully do this (well that I've found) is MAPI. So this means you need to use CDO 1.2 if your scripting. The two props you need to set are

H7FFF000B Set it to true which makes outlook 2003 hide the attachment(still visible in 2002 though)
H370B0003 PR_RENDERING_POSITION needs to be set to -1

The other thing that needs to be done is you need to add a property to the contact itself that tells Outlook that there is Picture for the contact. This property is the named property {00062004-0000-0000-C000-000000000046}0x8015 .

I've put a barebones script together that will do this using a hardcode EntryID that needs to be pulled from the contact using OulookSpy or pfDavAdmin. I've posted a downloadable copy of the code here the script itself looks like.

mapiserver = "servername"
mapimailbox = "mailbox"
contactEntryID = "000000002F7E...etc"
filename = "c:\temp\ContactPicture.jpg"
set objSession = CreateObject("MAPI.Session")
Const Cdoprop1 = &H7FFF000B
const Cdoprop2 = &H370B0003
strProfile = mapiserver & vbLf & mapimailbox
objSession.Logon "",,, False,, True, strProfile
Set objInbox = objSession.Inbox
Set objInfoStore = objSession.GetInfoStore(objSession.Inbox.StoreID)
set objmessage = objSession.getmessage(contactEntryID)
set objAttachments = objmessage.Attachments
Set objAttachment = objmessage.Attachments.Add
objAttachment.Position = -1
objAttachment.Type = 1
objAttachment.Source = filename
objAttachment.ReadFromFile filename
For Each objAttachment In objAttachments
if objAttachment.name = "ContactPicture.jpg" then
objAttachment.fields.add Cdoprop1,"True"
objAttachment.fields(Cdoprop2).value = -1
end if
Next
objmessage.fields.add "0x8015",11,"true","0420060000000000C000000000000046"
objmessage.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.