Mail relay

Infra > Mail relay. The SMTP server that carries confirmations, password resets and administrator notices. It is infra because it is a third-party service reached by host and port, with credentials - the same nature as a route's upstream.

Several features are switches with nothing behind them until this is set: self-registration with a confirmed address, password reset links, the one-time code by e-mail, and the daily digest.

The relay

The Mail relay screen: the server, its security, the sender address, password authentication, the test send and the daily digest

Then the credentials, as two separate forms rather than one generic set of boxes:

Mode When
Password An account and a secret. What every transactional relay uses, and what Gmail accepts with an application password
OAuth2 A token minted by client credentials stands in for the password (XOAUTH2). The only way into Microsoft 365, which no longer accepts a password over SMTP

OAuth2 asks for the token URL (your tenant's token endpoint), the client ID, the client secret, and a scope - left empty it uses Microsoft's SMTP scope.

Send a test

Pick which message, which language, and the recipient (your own address by default), and a real message goes through the relay with fake values but the real look. This is the fastest way to find out that a port is closed or a sender refused.

Daily digest

Once a day, the administrators who carry an e-mail address are told which accounts are about to lose access, which just did, which vault entries are about to reach their reminder date - and, first, which certificates are about to expire or have expired. A certificate issued automatically (ACME) is renewed weeks before its end, so one that shows up here is one whose renewal has been failing, and the line says so.

A day with nothing to say sends nothing. With no relay configured the notice stays owed and goes out the morning a relay answers.

Traps