Appearance
SMTP
If necessary each tenant can override SMTP configuration to use a different SMTP server to send emails from their email tasks. Using variables and secrets in AireVault combined with appropriates scopes, it's even possible to specify different SMTP settings for each workflow definition version.
How do I override the SMTP configuration for my tenant?
Create whichever of the following variables and secrets you require in AireVault
| Name | Type | Description |
|---|---|---|
| SmtpHost | Variable | The host of your SMTP server, e.g. smtp.gmail.com |
| SmtpPort | Variable | Which port to connect on, defaults to 465 |
| SmtpUsername | Variable | The username for your SMTP server, e.g. john@example.com |
| SmtpPassword | Secret | The password for your SMTP server. This must be a secret, not a variable. |
| SmtpUseSsl | Variable | Whether to connect using SSL, defaults to true |
| SmtpDefaultFrom | Variable | The default sending email address, e.g. bob@example.com |
How do I override the SMTP configuration for a specific workflow?
Using AireVault scopes, you can set different values for each of the above settings down to a workflow definition version level. See some examples below.
| Scope | Description |
|---|---|
| empty | Providing an empty scope will use the value by default for all products that support overriding SMTP config with Vault, unless a more specific scope is found |
flow | The value will be used by default by AireFlow only |
flow:my-workflow-key | All versions of the workflow with key my-workflow-key will use this value |
flow:my-workflow-key:2 | Only version 2 of the workflow will use this value |