- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-16-2022 03:37 AM
We are following below document provided by SNOW,
https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0816072
IMAP is working fine,
SMTP test connection showing below error.
Solved! Go to Solution.
- Labels:
-
Integrations
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-21-2022 12:20 AM
Hello Everyone,
I managed to solve this on my own,
below are the steps.
Configure your OAuth Profile in Application Registry, Add Entity Scopes.
Create 2 Email Accounts, one for IMAP and another for SMTP.
When you click on "Authorize Email Account" .
Make sure that you are signed in as same email account in the browser that you want to configure for email sending and receiving.
For example.
My email ID is 'jayantcpandit@gmail.com'
Email that I want to configure is 'example@example.com'
In this case, I need to sign in to the browser with 'example@example.com' where I click on "Authorize Email Account", not with my 'jayantcpandit@gmail.com'
With this way, it will make sure that you are using correct account to authorize.
Hope this helps.
Please mark this helpful, if solves your issue.
Thanks
Jayant
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-05-2023 04:41 AM
@Kushal09 - We are now facing the same issue, did you find a solution for this?
We have checked and we do have an E5 license but still getting the same error. We was able to authorize the SMTP email account but when testing the connection, that is when we get the error.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-05-2023 04:41 AM
@Jerry kk Wong - We are now facing the same issue, did you find a solution for this?
We have checked and we do have an E5 license but still getting the same error. We was able to authorize the SMTP email account but when testing the connection, that is when we get the error.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-27-2022 06:35 PM
@Jayant Pandit - I am facing a problem where the "Oauth token is either expired or not present". I've engaged ServiceNow HI for advice, but figured I'd see if you came across this in your experience.
We're using Azure AD as our SSO identity provider and Oauth endpoint for email. I've validated the email account is authorized to use the ServiceNow app, ensured it has an E5 license, and signed in as admin with that account.
In my opinion, the behavior seems to be a problem with our login redirect... when I click "authorize email account" it re-opens my ServiceNow environment in a new window... I would expect this to prompt for credentials (as it did when I set up the SSO idp). I've tried a variety of redirect uri's based on the SSO app's configuration but none seem to resolve the issue. Any thoughts are most appreciated.
V/R,
Daniel
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-28-2022 07:23 AM
Have you seen this link already ?
https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0791140

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-28-2022 10:14 PM
I had not, thank you for providing that link. Turns out the Oauth redirect uri was wrong, as I suspected. After updating to the correct instance.servicenowservices.com/oauth_redirect.do path the authentication was successful and the token was pulled. Now I just have to figure out why the connection presents the below error and email cannot be sent (receive is working fine).
All of our settings appear to be correct... Account has E5 license, scope is defined, API has send permissions, etc.
If we change security to --none-- instead of SSL/TLS... the error is not present, but email still won't send. Again, thoughts are appreciated.
V/R,
Daniel