Gmail and O365 deprecation of basic auth in favour of OAuth 2.0 for POP/IMAP mail retrieval

Support scope clarification

We’re getting a few support queries at the moment relating to mail server authentication problems. To be clear, Jira is responsible for definition of mail hosts and connectivity to those hosts, when a mail has been successfully retrieved, then JEMH is invoked (by Jira), and our support scope begins. We try to be helpful, and offer suggestions - our support is best effort as this problem area is not in our support scope. Problems with the Jira platform should be directed to support.atlassian.com

Below are some current references on authentication impacting changes (removal of basic auth)

O365 (affects POP/IMAP)

https://docs.microsoft.com/en-us/exchange/clients-and-mobile-in-exchange-online/deprecation-of-basic-authentication-exchange-online

When will this change take place?
We've already started making this change. New Microsoft 365 tenants are created with Basic authentication already turned off as they have Security defaults enabled.

So effectively 1 OCT 2022 basic auth will start to be disabled regardless of usage, SMTP basic auth remains valid.

Authentication problems?

If you are unable to authenticate, maybe this can help.

https://docs.microsoft.com/en-us/exchange/troubleshoot/administration/pop-imap-auth-fails-if-x-ms-client-application-is-microsoft-exchange-popimap

Gmail (affects POP/IMAP)

Quoting:

You may need to enable 2SV: and then use the app password instead of your regular password: .

Less secure apps are stopping for non Google Workspace customers in MAY 2022

A blog from Atlassian of 19th APR:

any mail server set up in Jira via a username and account password with a personal Google email account will not work from 30th May 2022

Atlassian Server/DC docs on configuring OAuth 2.0 to receive mail

Jira 8.13+ is required (https://jira.atlassian.com/browse/JRASERVER-63917).