We receive order requests from some customers embedded in the email body rather than an attachment. In Outlook, I can manually save the message as HTML. I configured Power Automate to create a file from the email. I'm not sure what format it is but it isn't HTML as if I saved it directly from Outlook. I've already wrote SQL code to parse the HTML message. Redoing it in this different format is problematic because the source code doesn't align like the manually saved file.
It needs to run as a cloud flow so calling an Outlook macro from PA Desktop is not a solution.
I have an accounting application that i use to send emails. Recently with the latest Outlook 365 update, every time i try and send an email, i get the error
"Sorry, something went wrong. You may want to try again."
The application is working through OLE to communicate with Outlook. In the application, there is an option to show the email before sending. This requires myself to click on Send. This option works fine.
However if do not want to see the email before sending and want it to be sent automatically, this is when the error comes up.
I have changed the Programmatic Access to to never warn me and allow 3rd party applications to go through. Prior to changing this setting, outlook use to pop up with a box asking permission for the application to go through. I used to click Allow and the error still appeared. With the above change, it does not prompt for me to allow but the error still appears.
I've a big problem because some eml file that are imported in the customer repository (IBM ECM) and retrieve from IBM Content Navigator.
This client demand the opening of this kind of file to the operating system and therefore to MS Outlook.
It occurs only for some of the emails and, by exporting the email and opening it with a test editor, it becomes clear that the problem is due to a series of null characters placed as the last line of the body of the email (I've attached a screenshoot).
Is there a way to allow Outlook to view these emails correctly?
Thinderbird for example also opens these emails without problems but the custome cant use this client, only MS Outlook is permitted.
Thank you in advance
email body
I've developed an add-in for Outlook, it needs to be able to access attachments to emails.
On the desktop app, if I move an email with attachments from a shared folder to my main inbox, then try to run the add-in on it, i get the error:
The specified attachment Id is invalid.
However, if I perform exactly the same operation through the web app, it works fine.
I have checked and the Office.context.mailbox.item.itemId and Office.context.mailbox.item.attachments[i].id are exactly the same whether on web or desktop.
Emails with attachments that have not been moved from a different folder, and emails without attachments work fine.
I am fetching the attachment on a remote server through a PHP script, using a callback token I orginally get from Office.context.mailbox.getCallbackTokenAsync. The requests are made via EWS requests.
I am running Office 365 and the Outlook version is 1910 (Build 12130.20390), running on Windows 10.
Can somebody please help?
After some helpful suggestions from #OutlookAdd-insTeam-MSFT, I've come to a solution for this.
The problem is, after moving a message from a shared folder to the main inbox, when using the desktop app, the Office.context.mailbox.item.attachments (created when we run Office.initialize) no longer returns the correct ID's, instead it seems to return the old cached/out of date ID's from before the email was moved. The ID's returned when using the web app are correct using this method.
However, requesting the ID's from the exchange server, via an EWS request (or a REST call, but I use EWS) always returns the correct attachment ID's, whether called from the web app or the desktop app.
So, the solution I have come to is to make sure and request all of the attachment ID's from the exchange server, rather than using the Office.context.mailbox.item object. It means adding in an extra step of having to get a callback token first to then be able to request the info from the exchange server, but it means you always get the correct ID's.
I hope this is of help to someone else.
My default email client is Windows Live Mail. When I right click on a file and select Send To->Mail Recipient Windows Live Mail New Message Window pops up, file is attached but body and subject are filled and I want them to be empty. Also, I want to Recipient (To: field) be filled with predefined address. What I found out so far:
Windows Live Mail (WLM) doesn't support automation via VBA so can't use vb scripting. Open Default E-mail Client using .Vbs file.
Note that you cannot attach files from the command line so can't create custom shortcut in Send To folder. Create a Message in Windows Live Mail or Outlook Express from the Command Line