This document provides information about the SMTP configuration report, which presents the SMTP account settings within Segura®.
Path to access
- On Segura®, in the navigation bar, hover over the Products menu and select Settings.
- In the side menu, select Email > SMTP Configuration
Actions Menu
| Item | Type | Description |
|---|---|---|
| New | Button | Opens the SMTP server settings window for a new SMTP account to be registered. |
| Actions | Dropdown menu | Displays the options for Print Report, Export CSV, and Schedule Report. |
Search fields
To view all search fields, click More.
| Item | Type | Description |
|---|---|---|
| ID | Text field | Filters by the SMTP account code in Segura®. |
| Name | Text field | Filters by the name of the SMTP account in Segura®. |
| Sender e-mail | Text field | Filters by SMTP account sender's email address. |
| Reply e-mail | Text field | Filters by SMTP account's Reply-To email address. |
| Return e-mail | Text field | Filters by SMTP account's Return-Path email address. |
| Confirmation e-mail | Text field | Filters by SMTP account confirmation email address. |
| Enabled | Dropdown menu | Filters according to the SMTP account status in Segura®. It can be Yes or No. |
Report fields
- ID.
- Name.
- Sender e-mail.
- Reply e-mail.
- Return e-mail.
- Confirmation mail.
- Enabled.
- Default: indicates if this SMTP account is the default use in Segura®.
- Secure connection: indicates if the SMTP account uses a secure connection.
- Uses config: indicates if the SMTP account should be forced to use the configuration section
- Read Conf: indicates if the SMTP account receives a read confirmation of the message.
- Footer: indicates if the account sends the footer in the email.
- Actions:
- Edit: opens the SMTP server settings window.
- Authenticate: starts the Microsoft OAuth2 authorization for the account. Available when the account uses a Microsoft OAuth2 flow.
- Test setting: opens the Test Email - Account window.
SMTP server settings
| Item | Type | Required | Description |
|---|---|---|---|
| Account Name | Text field | Yes | SMTP account name. |
| Enabled | Radio button | No | Indicates the SMTP account status. It can be Yes or No. |
| Sender e-mail | Text field | Yes | Filters by SMTP account sender's email address. |
| Reply e-mail | Text field | Yes | SMTP account response email address. |
| Reply e-mail (Return-Path) | Text field | Yes | SMTP account return email address. |
| Confirmation mail | Text field | Yes | Filters by SMTP account confirmation email address. |
| Default account | Radio button | No | Indicates whether the account is the default account for use in Segura®. It can be Yes or No. |
| Send Read Receipt | Radio button | No | Indicates whether the SMTP account will receive a read confirmation. It can be Yes or No. |
| Force settings use | Radio button | No | Indicates whether the SMTP account will be forced to use the default setting. It can be Yes or No. |
| Enable footnote | Radio button | No | Indicates whether the SMTP account should send the message footnote. It can be Yes or No. |
| Host SMTP | Text field | Yes | STMP account host address. |
| Port | Text field | No | Port where the SMTP account host is listening. |
| Use safe connection? | Radio button | No | Indicates whether the SMTP account should use a secure connection. It can be Yes or No. |
| Secure connection type | Radio button | No | Indicates which type of secure connection will be used. It can be TLS or SSL. |
| User authentication | Radio button | No | Indicates whether the SMTP account should use a credential for authentication. It can be Yes or No. |
| Ignore certificate error | Radio button | No | Indicates whether the SMTP account should ignore certificate errors. It can be Yes or No. |
| Use Network Connector | Radio button | No | Indicates whether the account should use a Network Connector. It can be Yes or No. |
| Network Connector | Dropdown menu | No | Select the Network Connector to use when connecting the SMTP account. Note: This option will only be enabled if you select Yes on the Use Network Connector radio button. |
| Credential for authentication | Dropdown menu | No | Select the credential that will be used for authentication by the SMTP account. Note: If you select Yes in the Use authentication option, the selection of a credential is mandatory; the credential must be previously registered in Segura®. |
| Microsoft OAuth2 flow | Dropdown menu | No | Defines how a Microsoft (Azure/Office 365) account authenticates with Microsoft over OAuth2. It can be Delegated (user consent) or Application (admin consent, app-only). Default is Delegated. See Microsoft OAuth2 flow options in the following section. |
Microsoft OAuth2 flow options
Defines how the SMTP account authenticates with Microsoft/Azure to send email over OAuth2. The right choice depends on how the customer's Azure tenant grants permissions to applications. To register the Azure application and grant these permissions, see Configure OAuth2.0 authentication for SMTP and IMAP via Azure.
| Option | Description |
|---|---|
| Delegated (user consent) | A user authorizes sending by signing in interactively and granting consent; Segura® sends emails on behalf of that user's mailbox, so the configured sender must match it. Use it in tenants where users can consent to applications themselves, or where an administrator performs the authorization login. Requires the Microsoft Graph delegated permissions Mail.Send and offline_access on the Azure app registration. |
| Application (admin consent, app-only) | A tenant administrator authorizes sending at the application level by granting consent once; no user signs in at send time, and Segura® sends emails from the configured sender mailbox using the application permission. Use it in tenants that require administrator approval for new applications, where the Delegated flow cannot complete because the approval is asynchronous. Requires the Microsoft Graph application permission Mail.Send on the Azure app registration, with administrator consent granted. |
Info
Security recommendation (least privilege): with the application Mail.Send permission, the app can send as any mailbox in the tenant. Restrict the application to the configured sender mailbox with an Application Access Policy in Exchange Online.
Authentication and consent messages
Segura® can display these messages while you authenticate a Microsoft OAuth2 account with the Authenticate action.
| Message | When it appears |
|---|---|
| Consent not completed. Application consent was not granted. If your tenant requires administrator approval, request it and run the authentication again. | The OAuth2 consent was not granted. Common in tenants that require administrator approval for new applications. |
| Consent completed. Send a test email to validate sending. | Consent was granted successfully; the account is ready for a test send. |
| Could not complete authentication with Microsoft. | The OAuth2 authentication could not be completed. Start the authentication again. |
| Sending via Microsoft Graph failed. Check whether the application permission was approved by the administrator (it may take a few moments to propagate). | A send attempt failed because the application permission is missing, not yet approved, or still propagating. |
| Sending via Microsoft Graph failed. | A send attempt through Microsoft Graph failed. |
Test Email - Account
| Item | Type | Required | Description |
|---|---|---|---|
| Send to | Text field | Yes | Fill in the email address where Segura® should send the test message. |
| Subject | Text field | Yes | Fill in the subject of the test email. By default it is filled with the TEST MESSAGE! string. |
| Message | Text field | Yes | Fill in the body of the test email. By default it is filled with the ATTENTION: THIS IS A TEST MESSAGE! string. |