FAQ

[expand all]  [collapse all]  [expand sections]  [collapse sections]  

Show All FAQs

Server Settings

  • Open FAQ in new window Gmail: Oauth2 support - Using personal Oauth2 credentials
  • This method requires POP Peeper v5.6.2+

    In order to continue using Oauth2 with Gmail accounts, you can setup your own Oauth2 dev credentials. This is a one-time procedure (expected to take 5-10 minutes) that will allow you to access all your gmail accounts using Oauth2 (up to 100), but you will need to add email addresses to Gmail's list if you create new Gmail accounts in the future.

    Use case: This method may be preferred over using app-passwords if (a) You do not want to enable 2FA on your accounts OR (b) If you have multiple Gmail accounts that don't already have 2FA, this method may be easier.

    1. Open the link: https://console.developers.google.com
      Make sure you are logged in with the Gmail account that you want to use for this purpose. Also, this account will need to have 2-step verification enabled (per this Google article); so keep this in mind. If you don't already have at least one account with 2FA enabled, consider creating a new Gmail account for the purpose of this method or only enable 2FA when you need to access the console and disable 2FA when you're done.
    2. Read and agree to the TOS

    3. On the page "Enabled APIs & Services", Click "Create Project"
    4. Enter a Project Name (e.g. Private Oauth2)
    5. Leave Location = "No organization"
    6. Press the "Create" button

    7. Select "Oauth consent screen" on the left
    8. Click "Get started" on the right
    9. Specify App Name (e.g. POP Peeper)
    10. Select your email address for the "user support email"
    11. Set Audience = "external"
    12. Specify your contact email address (you can use the same email address as the account)
    13. Select "Agree"
    14. Press "Create" button

    15. Select "Clients" on the left
    16. Select "Create Client" on the right (top)
    17. Set Application type = "Desktop App"
    18. Specify a Name (e.g. "POP Peeper")
    19. Press the "Create" button
    20. Copy the "Client ID" and "Client secret" values and enter them into the corresponding fields in POP Peeper:
      Main menu: Tools / Options / Oauth2

    21. Select "Audience" on the left
    22. Under "Test users", click "Add Users"
    23. Add every Gmail email address that you want to access using POP Peeper with Oauth2
      When you press "save", the 'add users' window should slide out; if not, press "save" again; if the email address appears with a red border, it may not be a valid email address
    Oauth2 will now be available to use for Gmail accounts within POP Peeper.
    When you access the consent pages during the initial Oauth2 process, you will see the following:
    "Google hasn't verified this app"
    -> just press "Continue"

    Quick reference

    To access your Client ID and Client Secret values:
    - Open your Google Dev console (or directly to the Credentials page)
    - Click "Credentials" on the left
    - In the "OAuth 2.0 Client IDs" section, edit the client

    To add additional Gmail accounts to access Oauth2:
    - Open your Google Dev console (or directly to the Audience page)
    - Click "Oauth consent screen" on the left
    - Click "audience" on the left
    - Press "Add users" in the "Test users" section

    Note: if you do not add your account to the "Test users" list and try to access Oauth2 with that account, you will get the following error:
    "Access blocked: POP Peeper has not completed the Google verification process"
    To fix this, you must add your email account to the "Add users" list as instructed above.