Google have announced they are turning off access to G Suite via username/password authentication.

My initial concern was this could potentially impact anyone using G Suite for Outbound Mail. However the statement says "No change is required for scanners or other devices using simple mail transfer protocol (SMTP) or LSAs (less secure apps) to send emails."

My question is whether CiviCRM are considering OAuth2 authentication (eg Google's XOAUTH2 scheme) when sending mail?

2 Answers 2


CiviCRM is not responsible for authentication of users (that's the CMS, ie. Drupal or WordPress). Using OAuth2 (or other protocol) for authenticating CiviCRM to another system would be the responsibility of the extension that wants to do that.

Or do you see a reason to include Oauth2 in core CiviCRM?

I'd be hesitant about using Oauth2 before fully understanding what you're getting into - here's a helpful blog w/ links from Colan Schwartz:


  • 1
    True, but I think that what the poster is asking about is for civi administer - system settings - outbound mail if you choose smtp and are using gmail servers as your outbound mail server. In that case civi does authenticate to google.
    – Demerit
    Commented Dec 20, 2019 at 16:32
  • Yes, you're probably right. I'd still say that it would require an extension and including it in CiviCRM Core would not be smart (for reasons of security/maintenance).
    – Alan Dixon
    Commented Dec 20, 2019 at 17:26
  • Fair enough. I think also the auth might be currently handled by the 3rd party EZC/zetacomponents package which might not support it anyway.
    – Demerit
    Commented Dec 20, 2019 at 17:30
  • Speaking on behalf of myself (we run a trade organization in the US) and a handful of others whom use CiviCRM and we talk back and forth, we all use Google Suite (former Google Business Apps). There are about 5M +/- paying businesses whom use it currently. Not sure how that breaks down to CiviCRM, but it certainly is not fly-by-night. To that point, the outgoing mail would become an issue for us and we wouldn't change email providers in order to keep CiviCRM. Not being negative, just we are not coders and retraining email ops to keep Civi wouldn't happen here. Commented Dec 20, 2019 at 17:41
  • 3
    My reading of the quote is that the target dates are for INBOUND reading of emails through POP/IMAP clients etc and they have not set a specific date for requiring anything new regarding OUTBOUND emails, just that they are hinting someday they might. While POP/IMAP might be used by the email processor, so it would affect that, OUTBOUND is the bigger concern for most civi users but that isn't set to change yet. Anyway I've made a ticket at lab.civicrm.org/dev/mail/issues/59. Thanks @ken-west for reporting. EDIT: Forgot about bounce processing. This could matter for inbound too then.
    – Demerit
    Commented Dec 20, 2019 at 18:30

This is an update from 2024.

Google explain how to access accounts when two-step verification (2SV) is not possible. See https://support.google.com/accounts/answer/185833

You turn on 2SV for the account you're using, but create an app password. The app password is what CiviCRM uses, but human access requires 2SV. Convenient and secure.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.