Outlook for mac will not compose new message

#Outlook for mac will not compose new message how to#

With the release of OS X Mavericks and beyond, Outlook 2011 Sync Services has stopped syncing Outlook contacts to the Mac address book, making it very hard to clean up duplicate Outlook contacts on your Mac.

Note that very little is different from the above.Д®xample of the HTML contents of a sent email opened in OWA after this roundtrip.Outlook for Mac 2011 is one of the most popular email clients for OS X, and while itвЂ™s extremely useful in many ways, it doesnвЂ™t play well with others. As an example, here is the HTML result of a getAsync on an email with a single image inserted:Д®xample of HTML obtained from body.getAsync after the roundtrip.Operating System: MacOS High Sierra v 10.13.6 (17G3025Д®xample HTML obtained from body.getAsync before the 'roundtrip':.We're also not seeing any reference to a cid in the Mac Outlook HTML blob, so even if we did want to replace the src with the base-64 encoding from the Rest API, we don't know how we would.

#Outlook for mac will not compose new message how to#

We are at a loss for how to preserve the signature, or any image in the mail body, while still being able to write content in with setAsync.Дo we need to modify the src given to us in the images from getAsync before writing them back? This stackoverflow question and this one as well seem tangentially related to this problem, but we are currently only seeing this problem when composing in Mac Outlook (Windows Outlook 2013, Windows Outlook 2016, and Outlook Web App are all behaving as expected). However, this resulted in the signatures not rendering correctly when the mail was sent, which is especially scary because it looks fine from the sender perspective. We thought we could do that by reading the existing HTML, making modifications to body markup without touching the markup for the signature, and then inserting the new HTML back into the mail body.

However, we need to preserve our users' signatures. Our plugin uses setAsync since it is the most flexible of these methods: it allows us to write content anywhere in the mail body, regardless of a user's selection. We currently have 3 means of writing content to the mail body: prependAsync, setSelectedDataAsync, and setAsync. Verify that the link points to the correct file and location).

The file may have been moved, renamed, or deleted. The image will not render properly (will either show a broken image icon and display the alt description, or will say The linked image cannot be displayed. Open the email in OWA, or on another computer (basically anything besides Outlook for Mac on the computer it was sent from).Reopen the Draft from the drafts folder and enter compose mode again. Close the mail and save it as a Draft.Note that the image still renders normally in the compose window. Wait for the taskpane to open and the function to run to completion.This image can either be pasted in, inserted via the Pictures button in the ribbon, or be included in a signature. In Outlook for Mac, open the taskpane on a mail which already has an image in the mail body.Add the following script to a task pane which runs in a compose-mode email message:.This only happens in Outlook for Mac (images are preserved properly in Windows 2013/2016 and OWA) which seems to imply that this is a bug. On the receiving end, the images will not render, and their src is incorrect. This is not visible to either the user or the add-in, but will result in an incorrect src for images once the mail has been sent. In Mac desktop only, reading the mail body via getAsync and then writing that result back to the mail body via setAsync corrupts the src of existing images. I would expect that the exact HTML we receive from getAsync can be written back into the mail body with setAsync without any user-facing change - including preservation of images that currently exist in the mail body. This is a cross-post of this Stack Overflow question Expected Behavior When the existing mail body contains images, the image will render correctly in the compose window but will be broken when the recipient opens the mail. We are seeing an issue in Outlook for Mac around 'roundtripping' the mail body with .getAsync and .setAsync when the mail body contains images.