01. What SMTP email configuration is

SMTP (Simple Mail Transfer Protocol) is a common protocol for sending email on the internet.

An institution can connect its existing enterprise mailbox or email provider to Finger Manager, such as an internal mail server, Google Workspace, Microsoft 365 / Outlook, Amazon SES, SendGrid, Mailgun, or another email service that supports SMTP.

As long as the provider supplies SMTP connection details, the configuration can be completed according to system requirements.

02. Why use your own mailbox

After an institution uses its own SMTP service, emails are sent through the institution's own email account or email domain.

For example, users may receive email from [email protected], [email protected], or [email protected].

End users can see the institution's branded email address instead of a Finger Grid system mailbox. This is especially useful for white-label business, broker platforms, and independent brand operations.

03. Configure SMTP

Open System Settings -> Email and fill in the SMTP configuration according to the information provided by the email service provider.

Common fields include SMTP Server / Host, SMTP Port, Username, Password / App Password, Encryption Type, Sender Email, and Sender Name.

Different email providers may require different fields. Save the configuration after completing the required information.

04. SMTP Server

SMTP Server is the sending server address provided by the email provider.

It may look like smtp.example.com, but the actual address must follow the SMTP documentation of the email provider used by the institution.

Do not use an unverified server address.

05. SMTP Port

SMTP Port is used to establish the connection to the mail server.

Common ports include 465 and 587, or another port specified by the email provider.

The port to use should be determined from the provider's SMTP settings.

06. Username and Password

Username can be an email address, an SMTP username, or an SMTP account provided by the service provider.

Password may be the mailbox password, a dedicated SMTP password, an App Password, or an SMTP Credential generated by the provider.

Some email providers do not allow direct use of the main account password and require a separate App Password or SMTP Credential. Follow the provider's security requirements when configuring this information.

07. Sender Email

Sender Email is the sender address that users see when they receive email.

For example, [email protected] can be used as the sender address.

If the email provider restricts sender addresses, Sender Email must be a verified or authorized address. Otherwise, email delivery may fail.

08. Sender Name

Sender Name controls the sender display name shown in email clients.

For example, if Sender Name is ABC Securities and Sender Email is [email protected], users may see ABC Securities [email protected].

Use the institution's official brand name so email identity stays consistent with the App and website.

09. Email use cases

After SMTP is configured, email can be used by Finger Grid functions that support email delivery.

Typical scenarios include registration verification codes, login verification codes, password reset, security alerts, system notifications, targeted user notifications, user group notifications, operating campaigns, service reminders, account-related notifications, and other email messages.

The exact usage scope depends on the products and functions enabled for the Organization.

10. Difference from Finger Grid system email

Finger Grid can provide platform-side email delivery, but platform email may have sending quotas, frequency controls, or usage fees.

If an institution wants more independent email delivery, it can configure its own SMTP service.

Using Finger Grid email requires no separate mail server configuration and can use the system-provided email capability, but may be subject to quota, cost, and platform delivery rules.

Using the institution's own SMTP sends email from its own mailbox and domain. Sending quota depends on its own email provider, Finger Grid does not charge an additional email sending fee, and provider fees are settled between the institution and the provider.

11. Branded email

For white-label or independently operated institutional brands, using a dedicated SMTP service is recommended.

For example, if users are using ABC Broker, registration, verification, and notification emails can also be sent by ABC Broker through [email protected].

This keeps App branding, website branding, and email branding consistent, and avoids showing a third-party platform brand to end users.

12. Email provider limits

Finger Manager connects to the SMTP service provided by the institution, but actual delivery capacity is still controlled by the email provider.

Limits may include daily sending quota, per-minute sending frequency, single email size, recipient count, anti-spam rules, SPF / DKIM / DMARC requirements, sender domain verification, and account security policies.

If email delivery fails, check both Finger Manager configuration and the email provider console.

13. SPF, DKIM, and DMARC

If an institution sends a large amount of email using its own domain, SPF, DKIM, and DMARC should be configured correctly.

These settings help email providers confirm that email is authorized by the institution and can reduce the chance of messages being placed in spam folders.

Related DNS configuration must be completed in the institution's domain provider or email provider console. Finger Manager does not modify the institution's DNS records.

14. SMTP security

SMTP passwords are sensitive credentials.

Use a dedicated SMTP password or App Password where possible, avoid using the main mailbox account password, rotate SMTP Credentials regularly, do not share SMTP passwords with unrelated personnel, and grant email configuration permissions only to necessary administrators.

If the provider supports independent SMTP Credentials, create a dedicated credential for Finger Manager.

15. Test email

After SMTP configuration is complete, send a test email before using it for production notifications.

During testing, confirm whether email can be sent normally, whether the sender name and sender email are correct, whether the email enters spam, whether HTML email format is displayed correctly, and whether Chinese, English, and other characters render normally.

Use the email channel for user notifications only after testing succeeds.

16. Organization-level independent configuration

Email service is configured independently by Organization.

Different institutions can use their own SMTP services, such as Broker A using [email protected] and Broker B using [email protected].

SMTP accounts and email delivery configurations are independent between Organizations and do not affect each other.

This allows Finger Manager to support multiple institutions on the same infrastructure while maintaining independent email identities and brand systems.

17. Permissions

Email configuration is a sensitive system-level setting.

Only administrators with the required System Settings permissions can view or edit SMTP configuration.

Sensitive information such as SMTP Password, App Password, and Credentials should be stored and protected according to system security policies.

Only designated system administrators should maintain email configuration.