How to Setup the Email Configuration
Email Configuration
Steps to Navigate
Step 1: Access Site Settings
- Click Site Settings in the left sidebar (or top navigation).
- Click the Integrations tab.

Step 2: Choose Email Configuration

1. Email Delivery Method (2 options)
Gmail (OAuth / API-based)
- Connects to Gmail through Google's secure sign-in (OAuth 2.0).
- You click "Sign in with Google" and allow the app access.
- Even when Gmail is chosen, you must still fill in all the SMTP fields below. The Update button only works when every required field has a value. If any field is blank, the configuration cannot be saved.
- The SMTP fields act as a backup if the Gmail sign-in expires or is cancelled.
- Use the "Send Test Mail" button to check the configuration before you save.
SMTP (Custom mail server)
- Uses standard SMTP to connect to a mail server (Gmail SMTP, Outlook, Zoho, your own server and so on).
- Needs the host, port, HELO domain, username, password and encryption.
- All fields in sections 2–7 apply.
- Use the "Send Test Mail" button to check the configuration before you save.
Configuration Note
In this setup, we chose SMTP, so everything below applies. If you choose Gmail, you must still fill in every field below. The Update button is always enabled, but if any field is empty, an error is shown and the configuration cannot be saved.
2. SMTP Server (Host)
Example values:
| Provider | SMTP Host |
|---|---|
| Gmail | smtp.gmail.com |
| Outlook | smtp.office365.com |
| Zoho | smtp.zoho.com |
| Custom | mail.yourdomain.com |
3. SMTP Port
The network door number on the SMTP server.
4. SMTP Helo Domain
When your app connects to the SMTP server, the first thing it says is:
HELO yourdomain.comThat text is the HELO domain (also called the "localhost name").
Why it matters:
- Some SMTP servers reject connections where the HELO looks fake (
localhost,127.0.0.1or random text). - Spam filters check it. A HELO domain that does not match raises your spam score.
- Best practice: enter your actual domain, for example
nextorbit.comoretrainia.com.
If you leave it blank, the app usually uses the server's own name or
localhost. This can get your emails marked as spam or rejected.
Required Field
This field must not be left blank. The Update button is always enabled, but if this field is empty, clicking Update shows an error and the configuration is not saved.
5. SMTP Authentication (3 options)
This decides how your app proves it is allowed to send mail.
None
- No username or password is sent.
- Works only on internal or trusted mail servers (for example, a company intranet SMTP server).
- Public servers (Gmail, Outlook) reject this.
- Use it only if your SMTP server is on your own network and set up to allow your IP address.
Login
- Standard username and password sign-in (
AUTH LOGIN/AUTH PLAINbehind the scenes). - Almost all providers use this.
- Your credentials are the email address and the app password or SMTP password.
Plain
- AUTH PLAIN sends the username and password together in one go, in encoded form.
- Works the same as Login, with a different method.
- Safe only over TLS or SSL. Without them, the password is only encoded, not encrypted.
- Many servers support both. The app picks one.
Recommended
For Gmail, Outlook or Zoho, choose Login (or Plain, both work).
6. Email + SMTP Password
- Email: the full email address used to sign in, for example
noreply@nextorbit.com. - SMTP Password:
- For Gmail with 2-step verification (2FA), you must use an App Password (16 characters), not your real password.
- For Gmail without 2-step verification, use "Less secure app access" (Google no longer supports this).
- For Outlook or Zoho, usually your account password or an app password.
- For custom servers, use the password your mail admin set.
Security Warning
Never store this in plain text in the app. Use:
- Android:
EncryptedSharedPreferencesor Keystore - Server: encrypted DB column + environment secrets
Required Fields
Note: Both fields must be filled. The Update button is always enabled, but if either field is empty, clicking Update shows an error and the configuration is not saved.
7. The 3 Checkboxes
These options control the SMTP connection and its security settings.
7.1 — "Automatically use STARTTLS if available"
STARTTLS means the connection starts plain, then upgrades to TLS using the STARTTLS command.
- If checked: the app connects plain and asks the server "Can we use TLS?" If yes, it upgrades. If no, it carries on plain (⚠️ risk).
- If unchecked: the app never tries to upgrade to TLS.
- Recommended: checked, with port 587.
Think of it as: "Knock on the door, then ask to move to a private room."
7.2 — "Use SSL connection"
SSL/TLS (implicit) means the connection is encrypted from the very start.
- If checked: the app encrypts the connection straight away. Usually port 465.
- If unchecked: no implicit SSL is used.
- Do NOT check both SSL and STARTTLS at the same time. They are two different ways to encrypt.
Think of it as: "The door itself is a vault — you're secure from the moment you enter."
Quick decision table
7.3 — "Active Status" (Active / Inactive)
This is a toggle for the whole configuration, not a protocol option.
- Active → the app uses this configuration to send emails.
- Inactive → the configuration is saved but not used. The app falls back to the default, Gmail, or sending is turned off.
When to use it:
- Admin is testing a new configuration → keep it Inactive until it is checked.
- Multiple configurations stored → only one Active at a time.
- Turn sending off for a while without deleting credentials.
8. Send Test Mail
How it works
Fill in all fields (even if Gmail is selected, every field is required).
Click "Send Test Mail".
A popup appears with:
- An Email input field.
- A Cancel button.
- A Send button.
The app tries to connect using the values in the form (SMTP host, port, HELO, authentication, credentials and TLS/SSL settings).
A test email is sent to the Email address entered in the popup.
The result is shown:
- ✅ Success: "Test mail sent successfully" (check your inbox and spam folder).
- ❌ Failure: an error message explains why (wrong host, wrong port, sign-in failed, TLS mismatch, blocked by a firewall and so on).

Popup behaviour
| Action | What Happens |
|---|---|
| Send | Test mail is sent to the entered email address. Success or failure is shown. |
| Cancel | Popup closes. No test mail is sent. Nothing happens. |
Important
The test mail is only sent when you click Send. Clicking Cancel closes the popup and no email is delivered. The configuration is not tested.
Why use it
- Confirms the SMTP credentials are correct before saving.
- Catches port and TLS mismatches (for example, 465 with STARTTLS instead of SSL).
- Verifies the HELO domain is accepted by the server.
- Ensures the "from" address is allowed to send.
- Avoids saving a broken configuration that would fail quietly later.
When Gmail is selected
- Even though Gmail normally uses its own sign-in (OAuth), the test mail still uses the SMTP fields you filled in.
- This proves the backup SMTP route works.
- If the Gmail sign-in is active, the app may also offer a test through Gmail.
Important
The Update button is always enabled. If any field is empty, including when Gmail is selected, clicking Update shows an error and the configuration is not saved. Send Test Mail is the way to check the configuration before saving.
9. What Is Shown and Required for Each Delivery Method
Important
Choosing Gmail does not hide the SMTP fields. Every field must be filled in. The Update button is always enabled, but clicking it with any empty field shows an error and the configuration is not saved. Use Send Test Mail to check before you save.
Recommended Setup
For Gmail (OAuth): all fields are still required
Last updated on