EWS Mail fetching issue - Proxy not enabled for ews. isIncoming: true
Issue: EWS Mail fetching issue using different tenants
Error trace 1:
Possible root cause:
The user might add the app registration under different tenants verify the same with the user. Check the domain names in the Azure portal login screen.
Solution:
Changing the tenant to multitenant or login to Azure using the email tenant used on the mail server settings.
New to ADSelfService Plus?
Related Articles
Mail fetching - deleted flag issue
This message will be thrown, when you have provided a shared mailbox. The concept here is, SDP MSP reads the mail from the configured mailbox and adds it as a request. During the time, if some other application fetches the mail from the same mailbox ...Troubleshooting Oauth configuration for mail server settings
Oauth in ServiceDesk Plus / AssetExplorer for Mail SDP supports Oauth configuration for Office365 and GSuite mailboxes since 11106 build. Office365 mailboxes can be configured with Oauth authentication using EWS (since 11106) and IMAP / SMTP (since ...EWS OAuth configuration with screenshots from Azure
In order to configure EWS OAuth configuration successfully, please follow the exact steps in the below link, https://help.servicedeskplus.com/configure-azure-as-authentication-server Note: For client secret, there would be a field called 'Value' as ...Problem in extracting emails via EWS from 11134
Emails getting fetched via EWS are getting failed to process and stops the Mail Fetching when that mail's object doesn't have InternetMessageHeaders. Note: This issue will not occur for all emails extracted via EWS except for the emails which don't ...Mail Fetching: Inability in Decoding 'iso-8859-8-i' Encoded Subjects Results In Mail Fetching failure
Issue: Mail fetching fails when the subject is encoded with 'iso-8859-8-i' due to the inability to decode the subject. This issue occurs across IMAP, POP, and EWS configurations. Issue ID: SD-120959 Error Trace for EWS: ...