Configuring FluentSMTP is an essential step after creating a website in Scoreapps. Without an authenticated connection, WordPress may try to send email through the server's basic mail function. Messages may fail, land in spam or be rejected.

This affects password resets, new-user emails, forms, orders, bookings and administrative notifications.

What this guide covers

The main setup is designed for personal Gmail and Google Workspace, the most common case. It also explains the OAuth alternative and the essentials for other providers.

Before you start: choose the correct route

• Gmail or Google Workspace + app password: the simplest route for one website. It uses Other SMTP in FluentSMTP and is explained step by step below.
• Gmail/Google Workspace + OAuth: avoids an app password and is Google's preferred method, but requires a Google Cloud application. It is intended for administrators or technically experienced agencies.
• Another provider: use its official SMTP server, port, encryption, username and password.

1. Open your website dashboard

1. In Scoreapps, open My Websites.
2. Find the project and click Access.
3. If the visual builder opens, use the WordPress top bar and choose the website name > Dashboard.
4. In the sidebar, open Settings > FluentSMTP. A new website may also show a Configure FluentSMTP notice.

2. Choose Other SMTP for the simple Gmail setup

On the provider screen, click Other SMTP. The separate Google Workspace connector uses OAuth and requires additional Google Cloud configuration.

3. Enable Google 2-Step Verification

Google only allows app passwords when 2-Step Verification is enabled.

1. Open 2-Step Verification in your Google Account.
2. Sign in to the account that will send website emails.
3. Click Get started or Turn on and complete Google's security method.
4. Continue when Google confirms that 2-Step Verification is active.

If you already use a code, Google prompt or authenticator app when signing in, this protection is probably enabled.

4. Create the FluentSMTP app password

1. Open Google App passwords.
2. Google may ask you to enter your account password again. This is normal and happens only on Google's official page.
3. Under App name, enter a recognizable name such as FluentSMTP - Website name.
4. Click Create.
5. Google displays a 16-character code. Copy it immediately; this is the password you will paste into FluentSMTP.
6. Do not share the code or expose it in screenshots. If it may have been seen, delete it in Google and create a new one.

See Google's official explanation of app passwords.

If “App passwords” is missing

First confirm that 2-Step Verification is active. Google may also hide the option when:

• the account belongs to a company, school or organization that restricts it;
• 2-Step Verification is configured only with security keys;
• the account uses Advanced Protection.

For Google Workspace, ask the administrator. If app passwords are not allowed, use the OAuth route below.

5. Enter the Gmail details in FluentSMTP

Sender settings

• From Email: the full Gmail or Workspace account you just configured.
• Force From Email: enabled, so another plugin cannot use an unauthorized sender.
• Set the return path: enabled, so bounces are associated with the sender.
• From Name: the company, professional or website name recipients will recognize.
• Force From Name: enable it if every message should display the same name.

Server and authentication

Google also supports port 465 with SSL. Start with 587 + TLS and do not mix one option's port with the other's encryption.

Keep Store Access Keys in DB selected. FluentSMTP encrypts the password with the WordPress security keys. Leave Disable Encryption for SMTP Password (Not Recommended) unchecked.

Click Save Connection Settings.

6. Advanced alternative: Google Workspace OAuth connector

Google recommends Sign in with Google/OAuth when an application supports it. In FluentSMTP this route starts with the Google Workspace provider instead of Other SMTP and does not use an app password.

It requires creating a Google Cloud project, enabling the Gmail API, configuring the OAuth consent screen, creating a web application client, registering FluentSMTP's redirect URL, copying the Client ID and Client Secret, authenticating the account and saving the token.

This is appropriate when an agency manages the infrastructure, Workspace policy requires OAuth or app passwords are disabled. For a single website managed by a non-technical user, the previous route is usually simpler.

For this method, follow the official FluentSMTP Gmail and Google Workspace OAuth guide and never expose the Client Secret in screenshots or tickets.

7. If you use another email provider

Select its dedicated connector or choose Other SMTP. Ask the provider for the exact host, port, encryption, username and password. Common combinations are 587 + TLS and 465 + SSL, but always use the official values for your service.

Do not use smtp.gmail.com for a mailbox hosted elsewhere, and do not mix settings from different companies. The server, account and DNS records must belong to the same email service.

8. Send a test email

1. Open Email Test.
2. Under From, select the saved connection.
3. Under Send To, enter an inbox you can access, preferably outside the sender domain.
4. Keep HTML enabled and click Send Test Email.
5. Check the inbox and spam folder.

9. Review email logs

Open Email Logs and filter by status:

• Successful: FluentSMTP handed the message to the provider.
• Failed: the connection, authentication or provider handoff returned an error.

A Successful status means Gmail or the provider accepted the message, but it does not guarantee main-inbox placement. For Workspace domains, also review SPF, DKIM and DMARC if messages land in spam.

Expected result

• FluentSMTP shows an active connection.
• The test email is logged as Successful.
• The message arrives with the expected sender address and name.
• You have tested a real website flow such as Forgot Password or the contact form.

Common Gmail errors

Authentication failed / Username and Password not accepted

Confirm that the username is the full email address and that SMTP Password contains the app password, not the normal Gmail password.

The app password worked and then stopped

If the main Google password changed, create a new app password and update the connection.

App passwords is missing

Enable 2-Step Verification first. For Workspace, ask the administrator; policy may require OAuth.

The sender is rejected or changes

Use the authenticated account as the sender. If you need a Workspace alias, confirm that Google has authorized it first.

The log says Successful, but the message does not arrive

Check spam, wait a few minutes and verify the recipient address. For Workspace domains, also validate SPF, DKIM and DMARC.

The test arrives, but password reset does not

Request a new reset and check Email Logs immediately. If no attempt appears, the issue may be in the form or plugin that should generate the message rather than SMTP.

Final recommendation

Configure FluentSMTP immediately after creating every website. For Gmail or Workspace managed by a small client, start with Other SMTP and an app password. Saving the fields is not enough: send a test, review the logs and complete a real password-reset flow.

Gmail has sending limits and is not designed for bulk campaigns. For high-volume transactional or marketing email, use a dedicated provider such as Brevo, SMTP2GO, SendGrid, Mailgun or Amazon SES.