• Resolved BlogAid

    (@blogaid)


    I set up FluentSMTP for my clients who use Workspace emails and all has been fine, though I haven’t checked it lately. However, today I’m setting it up for a client who uses Gmail. I’ve been through the process with her Google account and then again with my own and get the same result.

    In the Fluent settings, when I click the button to Authenticate with Google & get Access Token, then choose my Gmail account (that I’m already logged into), I get a 403 error. It states:

    “Access blocked: fluentsmtp.com has not completed the Google verification process. The app is currently being tested, and can only be accessed by the developer-approved testers. If you think you should have access, contact the developer. If you are a developer of fluentsmtp.com, see error details (linked to https://accounts.google.com/). Error 403: access_denied”

    I’ve seen other posts in this forum with similar issues that had replies that the credentials/app must be set up incorrectly. As stated, I’ve done this successfully for my clients using Workspace so I know my notes are accurate.

    Could you please check if Gmail is no longer allowing a connection to your plugin?

    The page I need help with: [log in to see the link]

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Support Ibrahim Sharif

    (@ibrahimsharif)

    Hello @blogaid,

    The error message “Access blocked: fluentsmtp.com has not completed the Google verification process” usually indicates a problem with the Google Cloud project configuration, specifically concerning the app’s verification status and the user accounts authorized to use it.

    Based on our experience and the information you’ve provided, let’s investigate two key areas:

    1. Developer Email Mismatch: Please carefully verify that the Google account you used to create the Google Cloud project and set as the developer email is the same Google account you’re using to generate the OAuth token within FluentSMTP. A mismatch here can absolutely trigger this 403 error. Make sure you’re logged into the correct Google account in your browser when you attempt the authentication.
    2. App Production Status in Google Cloud: It’s crucial that your Google Cloud project is in “Production” mode, not “Testing.” When an app is in testing mode, Google restricts access to only explicitly authorized testers. If the app remains in testing mode after you have created it, you will see this error.

    If these two key steps are not the case then the below solution can be considered for more investigation:

    Here are some additional troubleshooting steps you might find helpful:

    • Authorized Redirect URI: Make absolutely certain that the “Authorized redirect URIs” in your Google Cloud project match the redirect URI displayed in FluentSMTP’s settings exactly. This is case-sensitive and must be a precise match. Usually this is : https://fluentsmtp.com/gapi/

    Please let me know if checking the developer email and production status resolves the issue.

    Thread Starter BlogAid

    (@blogaid)

    Thank you for the suggestions. I set up this plugin for my clients and have a checklist of all the steps, so the things you mentioned were not skipped or performed incorrectly.

    Since I posted on this forum, I have successfully set up 2 more Workspace accounts with this plugin and all was well – using my same checklist.

    FYI, to test, I also tried WP Mail SMTP with free Gmail and it also failed with a 403 Forbidden error.

    So, I believe Gmail changed something with the free version. In fact, the interface has a new message since I posted this too, which does not allow you to do a private setup when using free Gmail. It has to be open to all testers.

    Have you actually tried to set up free Gmail with this plugin recently?

Viewing 2 replies - 1 through 2 (of 2 total)

The topic ‘Access blocked when connecting Gmail’ is closed to new replies.