Email gateways and senders
A gateway is the email service your organisation sends through. A sender rule decides who each email says it is from. Together they decide whether a client’s email goes out, and whose name is on it.
You see them under Settings › Correspondence › Email.
Gateways
Each gateway row shows its type, who it sends for, its default From address, and whether its credential is set.
| Column | What it tells you |
|---|---|
| Type | The email service. SendGrid sends for real. Simulator records each email as sent and delivers nothing. |
| Sends for | Whole bank, or one operating entity that sends under its own brand. |
| Default From | The name and address an email carries when no sender rule applies. |
| Credential | Set once the service’s key is entered on the Secrets page. A Simulator gateway shows Not needed. |
If a gateway’s credential is not set, it sends nothing. Select the credential name to open Secrets and enter the key there. Nobody can read a key back once it is entered.
Which gateway sends an email
- If the email belongs to an operating entity with its own gateway, that gateway sends it.
- Otherwise the whole-bank gateway sends it.
If the operating entity’s own gateway has no credential, the email is not sent through the whole-bank gateway instead. Its letters must not go out under another brand. The email is recorded as skipped, “channel not configured”.
If there is no gateway at all, your organisation sends no email. Clients are not offered email on their Delivery tab.
The Simulator gateway
A Simulator gateway lets a tenant with no email account send correspondence. Use it for demos, training and testing.
- It needs no credential. Its channel counts as configured as soon as the row exists.
- It records every email exactly as a real send would. Nothing leaves the bank.
- Each email it records is badged Simulated in the client’s email history.
- The correspondence panel reads Email (simulated) for each channel it sent.
- You open what it sent on the Simulator Outbox page, under Back office.
- A demo or test environment allows it. Your organisation’s live deployment refuses it: email reads “channel not configured”, even where a simulator row is configured.
The recipient address chooses the outcome (the Amazon SES mailbox simulator convention):
| Recipient | Outcome |
|---|---|
bounce@… |
Fails at once: “mailbox does not exist”. A must-deliver type takes its fallback. |
retry@… |
Fails on the first attempt, then sends on the first retry, one minute later. |
| anything else | Sent. |
Only the whole local part counts. bouncer@… and dianne@bounce.example send
normally.
A statement to bounce@mail.example fails with “mailbox does not exist”. One to
retry@mail.example records a failed attempt, then a sent one.
Sender rules
Sender rules are checked top to bottom. The first rule that matches decides the From address, the display name and the Reply-To address.
flowchart TD
A[Email to send] --> B{A rule for this<br/>correspondence type?}
B -- yes --> R[Send from the rule's address]
B -- no --> C{The email names an<br/>operating entity with<br/>its own sender?}
C -- yes --> E[Send from the operating entity's address]
C -- no --> G[Send from the gateway's default From]
A rule limited to one operating entity is skipped for every other operating entity’s email.
Worked example
Woodgrove Bank sends from bank.example. The domain is authenticated with its
email service.
| Order | Applies to | From | Reply-To |
|---|---|---|---|
| 1 | Statements | statements@bank.example | service@bank.example |
| — | Operating entity default | service@bank.example | — |
| — | Gateway default | noreply@bank.example | — |
- A statement goes from
statements@bank.example, with replies toservice@bank.example. - A notice for the operating entity matches no rule. It goes from
service@bank.example. - A security notice names no operating entity. It goes from the gateway default,
noreply@bank.example.
The Domain column shows whether each rule’s address is still authenticated with the gateway today.
Why a rule is refused
Email services refuse to send as a domain you have not proved you own. So a rule is checked when it is saved, against every gateway that could send it.
| Message | What to do |
|---|---|
| The domain is not authenticated on a gateway | Authenticate the domain with your email service, or use an address on a domain that is. |
| Set the gateway credential first | Enter the gateway’s key on the Secrets page, then save the rule again. |
| Could not verify the domain; try again | The email service did not answer. Try again in a few minutes. |
| No email gateway can send it | Configure a gateway first. |
Subdomains of an authenticated domain count. mail.bank.example passes when
bank.example is authenticated. A lookalike such as evilbank.example does not.
Configuring a gateway checks every rule it would send. A gateway whose key does not cover an existing rule’s domain is refused, and the message names the rule.
Standards
- The From, display name and Reply-To follow the internet message format, RFC 5322.
- A domain is authenticated when the email service has verified its sender policy (SPF, RFC 7208) and its signing key (DKIM, RFC 6376). Receiving mail servers apply the domain’s DMARC policy (RFC 7489) to what arrives.
What your organisation configures
- Which email service your organisation uses, and its key.
- Whether an operating entity sends through a gateway of its own.
- Each gateway’s default From name and address.
- The sender rules and their order.
- A default sender for each operating entity.
From the LedgerTM product guide, as shipped with the software and written with it. Copied from the platform repository on 2026-11-11.