Hi,
Unfortunately, the issue still persists.
Now the error has changed tough :Error: Microsoft Exchange returned HTTP 403 (ErrorAccessDenied): Access is denied. Check credentials and try again.
Any suggestions?
Thank you,
David
Hi,
Unfortunately, the issue still persists.
Now the error has changed tough :Error: Microsoft Exchange returned HTTP 403 (ErrorAccessDenied): Access is denied. Check credentials and try again.
Any suggestions?
Thank you,
David
Hello,
we found out the issue which is effectively linked to a missing permission on the Easymorph for Exchange Online : you need to add User.ReadBasic.All. It's required to use the translateExchangeIds api endpoint when using it on a share mailbox (not needed on your own mailbox).
Thanks
Olivier
Hello Olivier,
Thank you for researching this. We have identified the same cause of this issue. The "Fetch email" action translates message IDs to an EWS format using the translateExchangeIds endpoint for backward compatibility reasons, but this is not actually needed for most use cases, so we are considering adding an option that will determine whether message IDs should be translated.
Meanwhile, can you please tell us whether you are storing or comparing the message IDs returned by the "Fetch email" action against previously stored values?
David, can you please answer this question too?
No we don't have such use case. We read and process the messages only once. We use the id only when processing the message to be able to move it to a different mailbox's folder at the end of the pipeline. We don't store it nor compare it with previous executions.
Thanks
Olivier
Could you please try the new version and let us know if the issue has been resolved?
You can download the latest version here.
Hi,
Retried it and now it says this:
Error: Access to the path is denied.
Hi @davidMF98,
Are you trying to fetch attachments? If so, can you please try to run the "Fetch email" action without the "Fetch attachments" option checked? Also, don't forget to switch the "After a message is fetched" option to "Do nothing". Will this succeed?
The most likely reason for this error is that you are trying to fetch attachments to a folder without write permissions.