- 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
08-16-2022 03:54 AM
Hi, it is covered already in the same KB article, within "Known error" section, no?
Hope it helps
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-16-2022 04:25 AM
Hi Appli, Already tried that, not working.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-08-2022 04:31 AM
Hi Jaynat, did you get a response on a solution as we are also facing the same issue.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-19-2022 03:21 AM
I am facing the same issue. Licence is E5 and I am still getting the same error