MSGraph Email Poller

You need to make sure the that application tied to the client credentials you have received have access to the mailbox you are trying to connect to.

Hi Team,

We are using msgraph mail poller plugin to read emails. We are getting below error while reading emails. Could you please help on this ?

Error Message : Error code: ErrorAccessDenied Error message: Access to OData is disabled: [RAOP] : Blocked by tenant configured AppOnly AccessPolicy settings. GET

Thank you in advance for your help

• Security patch updated

Microsoft setup steps

• Create top level mailbox per environment for email polling
• Create mailbox folders for processed emails and failed emails
• Set up server side forward and deliver rules to copy emails from Shared Inboxes to Top Level Inbox
• Register Azure application
  • Mail.ReadWrite (for polling)
  • Mail.Send (for reply capabilities from each mailbox)
  • Top Level Inbox requires sendAs permission to all Shared Inboxes
  • Restrict application access to only Shared Inboxes & Top Level Inbox
  • OAuth 2.0 Client Credentials grant type
  • Application Permission:
    • Mail.ReadWrite (for polling)
    • Mail.Send (for reply capabilities from each mailbox)
    • Top Level Inbox requires sendAs permission to all Shared Inboxes
    Restrict application access to only Shared Inboxes & Top Level Inbox

Hi, Can someone help me what are the basic pre-requisites to configure this.

Anyone else facing the issue with null subject? It is kind of critical for us, as until the message with null/empty subject is deleted from the mailbox manually, the mail poller is blocked

Hello, we have started to receive new type of error after the upgrade to the version 4.2.6. If the email does not contain subject, mail poller fails with an error Cannot invoke "String.equals(Object)" because "subject" is null. This error persists until the message without subject is removed from the Inbox.

Can some error handling be added for these cases?

Thanks!

I see the error message "Error executing the request" in output from the smart service. The process doesn't faild and it ends correctly.
What's the problem?

I don't think it is something we have taken into account. MessageId is a field that tracks the internal id of the message withing Azure which should allow for referencing in replies or forwards. I would give that a try in your responses.

Have you opened a support case around this? While this is a plugin, the behavior seems very unexpected.
Do you have additional information from logs, e.g. a stack trace?