Configure outgoing mail and templates
Archived guide for existing Fusion Owned License installations; use the instructions for your installed build.
Basic email settings
Open **Settings > Email Settings > Basic Email Settings**. The source lists PHP mail, SMTP and supported provider integrations such as SendGrid or Mailgun; the options available depend on the build.
| Field | What to configure |
| --- | --- |
| **Mail sending type** | Scheduled or instant delivery |
| **Scheduled settings** | Number of messages per batch when scheduled sending is selected |
| **System mail** | Default sender address |
| **The system from name** | Sender display name |
| **Admin signature** | Default system email signature |
| **Mail type** | PHP or SMTP |
| **SMTP Host** | Outgoing SMTP server |
| **SMTP Port** | The server's configured port |
| **SMTP Username / SMTP Password** | Authentication entered privately in the protected settings |
The historical Gmail example uses `smtp.gmail.com` and port `465`. Treat these as the archived example, not a complete current Gmail setup: use your mail provider's supported TLS and authentication method. The old example calls its authentication value a Gmail password; follow the provider's supported authentication method for the actual account and never send that value to support. SMTP sends mail; IMAP and POP3 mailbox settings do not replace it.
Scheduled and instant messages
The source specifies a scheduled mail job every 5 minutes and a configurable batch size. It does not provide a written mail-job endpoint or CLI command, so use the job supplied with your installed build rather than copying the daily-maintenance job for mail.
A template can also have a scheduled/instant setting. If one message type is delayed while others send, check both **Mail sending type** and that template's delivery setting before retrying the entire queue.
Email templates
Open **Settings > Email Settings > Email Template**. Choose the category and template, then use **Edit** to update its content. The documented uses include invoices, welcome messages, account changes and order alerts.
Keep the supported system variables as placeholders; they are replaced with the actual event information. A template can be disabled, and the source supports content in several languages with default-language content used where a translation is missing.
Test the edited message with a controlled recipient and review its final subject, variables and signature. For a delivery problem, preserve the template name, time and redacted error; a queued or submitted message is not confirmed mailbox delivery.