Gmail integration test
Overview
AlthoughThe system supports Gmail integration as a testing feature, but it is still recommended that you use a standard mail server for daily operations. This is because Gmail integration is primarily intended for testing purposes and may not be suitable for all production environment requirements. To ensure more stable and reliable mail delivery, choosing a formal mail service is a better option.
Setup
If you have already linked your own Gmail account but have not set it up following the "Google verified dedicated mailbox" steps, don't worry. Simply follow the steps below: after creating a dedicated Google verified mailbox, go into your Gmail account and resend the verification email to this newly created dedicated mailbox.
To comply with Google's security rules and ensure that you can successfully receive the verification email for integration, you need to add a mailbox dedicated to receiving Google verification emails. For example, you can name this dedicated mailbox "Google Verified Dedicated Mailbox" for easy identification.
And in the receiving settings' service email location, directly copy and paste the system default Email address described below.
For the SMTP part, since sending emails is not required, you can fill it in arbitrarily.
Formal binding
Assuming today you want to bind Google mailbox to the system, this field should be filled with the mailbox to be serviced, that is, your Gmail.
Open Gmail and click the gear icon at the top right of the page to go to settings.
Select "Forwarding and POP/IMAP" tab, and click "Add a forwarding address."
Enter " FIRST LINE system mail address". Example: [email protected]
Later the FIRST LINE system will receive from Google averification email,please make sure to return to Gmail settings to complete the verification, otherwise forwarding will not work correctly.
Once everything is ready, settings as shown indicate the binding procedure is complete.
Frequently Asked Questions
Cannot send via SMTP
When you test Gmail SMTP sending, if an error occurs that says "Failed to authenticate on SMTP server with username “[email protected]” using 3 possible authenticators. Authenticator LOGIN returned Swift_TransportException." please ask the administrator of that mailbox to help troubleshoot the following possible causes:
Your Google mailbox has already exceeded the limit of three app authorizations.
Because your account usestwo-step verification, you mustcreate an app passwordto use app sign-in.
How to enable an app password
If you find Gmail SMTP sending failing, a possible reason is that from May 2022, Google has fully moved to the more stringent "app password" feature and you can no longer use your regular Google login password to send mail.
Go to the Google security settings page:
Open your browser and go to the Google Security settings page.
In the "Sign in to Google" section, click "2-Step Verification."
Enable 2-Step Verification:
Click "Get started" and follow the prompts to verify your identity (you may need to enter your Google password).
Enter your phone number and choose how to receive verification codes (SMS or voice call).
Enter the verification code you receive to complete the 2-step verification setup.
Generate an app password:
Return to the Google Security settings page, find the "App passwords" option and click it.
In the "Select app" dropdown, choose "Other (Custom name)."
Enter "FIRST LINE system", then click "Generate."
The system will generate an app password; please record it carefully.
Configure FIRST LINE system SMTP:
Log in to your FIRST LINE system admin interface and go to the email settings page.
Enter the following SMTP configuration information:
Server address: smtp.gmail.com
Port: 587
Account: [your Gmail account]
Password: [the app password you just obtained]
Encryption: TLS
After saving the settings, try sending a test email to confirm whether the configuration was successful.
Last updated