Connect a mail server: e-mail for security notices (research first) #896

Closed
opened 2026-10-13 21:36:30 +00:00 by Cordy · 7 comments
Owner

Split from #895 (decision by Nikola, 2026-10-13).

Why

  • Cairn sends no e-mail today. There is no mail server setting; everything goes to the bell.
  • NIST SP 800-63B-4 (final, July 2025): when a new authenticator is bound to an account (in Cairn, a new connected device or app password, #895), the CSP SHALL notify the subscriber via a mechanism independent of the transaction binding the new authenticator. A bell item inside the same session only partly meets this; e-mail is the usual independent channel.
  • Other notices that would benefit, to be confirmed during research:
    • all devices disconnected by an admin reset (#851, #895);
    • an emergency (break-glass) account signed in (#887);
    • administrator rights changed (#887);
    • an admin review due (#888);
    • scheduled reports (#888, #833);
    • share expiry.

Scope (to be refined after research)

  • A new section in the admin dashboard to connect a mail server:
    • SMTP host, port, TLS mode (implicit TLS / STARTTLS / none for a local relay);
    • authentication (username and password, possibly OAuth2 for Microsoft 365 / Google, see below);
    • sender address and name;
    • a test e-mail button with a clear error message.
  • The secret is held like other secrets: config/env first; the dashboard possibly write-only.
  • E-mail addresses per account:
    • from the IdP claim or LDAP mail;
    • for local accounts, a field (verified?);
    • Cairn has no address field for local accounts today.
  • Which notices go by mail: per notice type, user opt-out where it isn't security-relevant, security notices not mutable (like the bell).
  • Templates in 4 languages plus de-CH, plain text plus simple HTML, no tracking pixels or remote images.

Research first

  • What comparable products do: Nextcloud, ownCloud/oCIS, OpenCloud, Seafile, FileRun, Gitea/Forgejo, Keycloak (its own SMTP settings), Synology.
  • What breaks in practice: SPF/DKIM/DMARC alignment, relay restrictions, and Microsoft 365 / Google ending Basic SMTP AUTH (Microsoft: off by default for existing tenants end of Dec 2026, see #895 research). Is OAuth2 SMTP needed from day one?
  • Operator needs: a local relay or smarthost, a queue and retries when the mail server is down, a send log or audit, rate limits.
  • Standards and legal:
    • NIST 800-63B-4 §4.6 notifications;
    • BSI APP.5.3 (E-Mail-Client/-Server) where relevant;
    • GDPR / revDSG for addresses as personal data;
    • CRA (#876) secure defaults (TLS required by default).
  • Privacy: what goes in the mail (no file names in the subject?), data minimisation.

Decisions and a mockup of the dashboard section come after the research is read.

Split from #895 (decision by Nikola, 2026-10-13). ## Why - Cairn sends **no e-mail** today. There is no mail server setting; everything goes to the bell. - **NIST SP 800-63B-4** (final, July 2025): when a new authenticator is bound to an account (in Cairn, a new connected device or app password, #895), the CSP **SHALL notify the subscriber via a mechanism independent of the transaction binding the new authenticator**. A bell item inside the same session only partly meets this; e-mail is the usual independent channel. - Other notices that would benefit, to be confirmed during research: - all devices disconnected by an admin reset (#851, #895); - an emergency (break-glass) account signed in (#887); - administrator rights changed (#887); - an admin review due (#888); - scheduled reports (#888, #833); - share expiry. ## Scope (to be refined after research) - A new section in the admin dashboard to **connect a mail server**: - SMTP host, port, TLS mode (implicit TLS / STARTTLS / none for a local relay); - authentication (username and password, possibly OAuth2 for Microsoft 365 / Google, see below); - sender address and name; - a **test e-mail** button with a clear error message. - The secret is held like other secrets: config/env first; the dashboard possibly write-only. - E-mail addresses per account: - from the IdP claim or LDAP `mail`; - for local accounts, a field (verified?); - Cairn has no address field for local accounts today. - Which notices go by mail: per notice type, user opt-out where it isn't security-relevant, security notices not mutable (like the bell). - Templates in 4 languages plus de-CH, plain text plus simple HTML, no tracking pixels or remote images. ## Research first - **What comparable products do:** Nextcloud, ownCloud/oCIS, OpenCloud, Seafile, FileRun, Gitea/Forgejo, Keycloak (its own SMTP settings), Synology. - **What breaks in practice:** SPF/DKIM/DMARC alignment, relay restrictions, and **Microsoft 365 / Google ending Basic SMTP AUTH** (Microsoft: off by default for existing tenants end of Dec 2026, see #895 research). Is OAuth2 SMTP needed from day one? - **Operator needs:** a local relay or smarthost, a queue and retries when the mail server is down, a send log or audit, rate limits. - **Standards and legal:** - NIST 800-63B-4 §4.6 notifications; - BSI APP.5.3 (E-Mail-Client/-Server) where relevant; - GDPR / revDSG for addresses as personal data; - CRA (#876) secure defaults (TLS required by default). - **Privacy:** what goes in the mail (no file names in the subject?), data minimisation. Decisions and a mockup of the dashboard section come after the research is read.
Author
Owner

Decision (Nikola, 2026-10-13) and proposed approach

Decision: security notices always go to the bell. Once a mail server is connected, they go by e-mail as well. #895 ships the bell items now and gets the e-mail copy through this issue.

Why this is needed

  1. NIST SP 800-63B-4 §4.1.2 / §4.6: binding a new authenticator SHALL be notified through a mechanism independent of the binding transaction. A bell item in the same browser is not independent; an e-mail to a stored address is. Notices in scope:
    • new connected device (#895);
    • all devices disconnected (#851);
    • password changed or reset.
  2. Operators need to reach people who aren't signed in. The bell only works for someone who opens Cairn. Notices that matter when nobody is looking:
    • admin review due (#888);
    • an emergency account signed in (#887);
    • scheduled reports (#888, #833);
    • share expiry.
  3. Market: every comparable product can send mail (Nextcloud, Seafile, oCIS/OpenCloud through their notification service, Gitea/Forgejo, FileRun). A file server that can't is a gap people notice in evaluations.

Proposed approach (to be checked against the research)

  1. Config first, dashboard second.
    • mail.smtp{host, port, tls: implicit|starttls|none, username, password, from, fromName} in config/env, with the password from env or a secret file.
    • New admin section Basic settings › Mail server:
      • shows the active values (password write-only);
      • a Send test e-mail button with the SMTP server's actual answer as the error message;
      • a status chip (Not connected / Connected / Failing since …).
    • Whether the dashboard may set values (stored encrypted in the state backend) or only show them is a decision for after the research.
  2. Delivery:
    • an in-memory queue with retries (backoff up to 24 h), persisted so a restart doesn't lose security notices;
    • a failing server raises an admin bell item and the Overview row;
    • every sent security notice is audited (mail-sent, recipient and type, no content).
  3. Addresses:
    • directory accounts: IdP email claim or LDAP mail;
    • local accounts: a new optional e-mail field (admin-set or self-set with a verification link);
    • break-glass accounts: an operator-set notice address in config, so an emergency sign-in reaches someone.
  4. Content:
    • plain text plus simple HTML, 4 languages plus de-CH, the recipient's language;
    • no tracking, no remote images;
    • minimal data (no file names in subjects);
    • every security mail says what happened, when, from where (respecting audit.ip), and what to do if it wasn't you.
  5. TLS required by default, with no plain text to remote hosts unless explicitly configured. This fits the CRA secure-by-default rule (#876).
  6. Microsoft 365 and Google: Basic SMTP AUTH is being retired (Microsoft: off by default for existing tenants end of Dec 2026). Research whether OAuth2 SMTP (XOAUTH2) is needed in v1, or whether "use your relay or smarthost" is acceptable.

Research before the spec

Read the research before deciding anything:

  • products: Nextcloud, oCIS/OpenCloud, Seafile, Gitea/Forgejo, Keycloak, FileRun, Synology;
  • operator pain: SPF/DKIM/DMARC, relays, queues, OAuth SMTP;
  • standards: NIST §4.6, BSI APP.5.3, GDPR / revDSG;
  • the dashboard section mockup.
## Decision (Nikola, 2026-10-13) and proposed approach **Decision:** security notices always go to the **bell**. Once a mail server is connected, they go **by e-mail as well**. #895 ships the bell items now and gets the e-mail copy through this issue. ### Why this is needed 1. **NIST SP 800-63B-4 §4.1.2 / §4.6:** binding a new authenticator SHALL be notified through a mechanism independent of the binding transaction. A bell item in the same browser is not independent; an e-mail to a stored address is. Notices in scope: - new connected device (#895); - all devices disconnected (#851); - password changed or reset. 2. **Operators need to reach people who aren't signed in.** The bell only works for someone who opens Cairn. Notices that matter when nobody is looking: - admin review due (#888); - an emergency account signed in (#887); - scheduled reports (#888, #833); - share expiry. 3. **Market:** every comparable product can send mail (Nextcloud, Seafile, oCIS/OpenCloud through their notification service, Gitea/Forgejo, FileRun). A file server that can't is a gap people notice in evaluations. ### Proposed approach (to be checked against the research) 1. **Config first, dashboard second.** - `mail.smtp{host, port, tls: implicit|starttls|none, username, password, from, fromName}` in config/env, with the password from env or a secret file. - New admin section **Basic settings › Mail server**: - shows the active values (password write-only); - a **Send test e-mail** button with the SMTP server's actual answer as the error message; - a status chip (Not connected / Connected / Failing since …). - Whether the dashboard may *set* values (stored encrypted in the state backend) or only show them is a decision for after the research. 2. **Delivery:** - an in-memory queue with retries (backoff up to 24 h), persisted so a restart doesn't lose security notices; - a failing server raises an admin bell item and the Overview row; - every sent security notice is audited (`mail-sent`, recipient and type, no content). 3. **Addresses:** - directory accounts: IdP `email` claim or LDAP `mail`; - local accounts: a new optional e-mail field (admin-set or self-set with a verification link); - break-glass accounts: an operator-set notice address in config, so an emergency sign-in reaches someone. 4. **Content:** - plain text plus simple HTML, 4 languages plus de-CH, the recipient's language; - no tracking, no remote images; - minimal data (no file names in subjects); - every security mail says what happened, when, from where (respecting `audit.ip`), and what to do if it wasn't you. 5. **TLS required by default**, with no plain text to remote hosts unless explicitly configured. This fits the CRA secure-by-default rule (#876). 6. **Microsoft 365 and Google:** Basic SMTP AUTH is being retired (Microsoft: off by default for existing tenants end of Dec 2026). Research whether OAuth2 SMTP (XOAUTH2) is needed in v1, or whether "use your relay or smarthost" is acceptable. ### Research before the spec Read the research before deciding anything: - products: Nextcloud, oCIS/OpenCloud, Seafile, Gitea/Forgejo, Keycloak, FileRun, Synology; - operator pain: SPF/DKIM/DMARC, relays, queues, OAuth SMTP; - standards: NIST §4.6, BSI APP.5.3, GDPR / revDSG; - the dashboard section mockup.
Author
Owner

Second use: storage-restored notice (#904)

This issue was opened for security notices. #904 adds a second consumer, decided by Nikola on 2026-10-15:

  • Where: when an admin declares that storage was restored from a backup, the declaration form offers "Also e-mail everyone". It is off by default and only shown once mail is configured.
  • Content: the same text as the in-app banner: the date range of the gap and the admin's optional one-line message.
  • Recipients: every active account with an e-mail address. Sent once per declaration.
  • Proof: the send result per recipient should be visible to the admin next to "Seen by N of M", because institutions use it as proof of notification (nDSG Art. 24 / GDPR Art. 34 style records).
  • Not a replacement: the e-mail does not replace the in-app "Got it" acknowledgement.

Requirements for the mail design here:

  • Bulk send: to all users, rate-limited.
  • Results: a per-recipient delivery result stored with the event.
  • Languages: templates in EN/DE/FR/IT, chosen per user language.
  • No links: no tracking pixels or links that act on click.
## Second use: storage-restored notice (#904) This issue was opened for security notices. #904 adds a second consumer, decided by Nikola on 2026-10-15: - **Where:** when an admin declares that storage was restored from a backup, the declaration form offers **"Also e-mail everyone"**. It is off by default and only shown once mail is configured. - **Content:** the same text as the in-app banner: the date range of the gap and the admin's optional one-line message. - **Recipients:** every active account with an e-mail address. Sent once per declaration. - **Proof:** the send result per recipient should be visible to the admin next to "Seen by N of M", because institutions use it as proof of notification (nDSG Art. 24 / GDPR Art. 34 style records). - **Not a replacement:** the e-mail does not replace the in-app "Got it" acknowledgement. **Requirements for the mail design here:** - **Bulk send:** to all users, rate-limited. - **Results:** a per-recipient delivery result stored with the event. - **Languages:** templates in EN/DE/FR/IT, chosen per user language. - **No links:** no tracking pixels or links that act on click.
Author
Owner

From the #695 OpenCloud comparison (item 16a, kept 2026-10-27): when mail lands, the notification settings get a Mail column next to In-App, and a digest interval. This fits the 2026-10-13 decision: the bell always, e-mail in addition.

From the #695 OpenCloud comparison (item 16a, kept 2026-10-27): when mail lands, the notification settings get a **Mail** column next to In-App, and a digest interval. This fits the 2026-10-13 decision: the bell always, e-mail in addition.
Author
Owner

Research (2026-10-29)

NIST SP 800-63B-4 (VERIFIED): §4.1.2.1 binding a new authenticator SHALL notify via an independent mechanism (§4.6); §4.2 note: a password replaced while other authenticators exist counts as binding; §4.5 SHOULD notify on invalidation; §4.6: notifications SHALL go to all stored addresses, CSPs SHALL support two addresses per account, and give instructions + contact to repudiate.
Microsoft 365 (VERIFIED, MC786329): Basic SMTP AUTH disabled by default for existing tenants end of Dec 2026; OAuth (XOAUTH2, client credentials, SMTP.SendAsApp) is the path; 587 STARTTLS only; 30 msgs/min, 10k recipients/day; alternatives: relay connector (static IP), HVE (internal only, paid). Google: app passwords or the Workspace SMTP relay; XOAUTH2 needs full-mailbox scope.
Market: Nextcloud and Gitea fall back to plaintext when STARTTLS is missing; OpenCloud and Gitea drop failed mail silently; Keycloak has XOAUTH2 (Microsoft only); FileRun queues with a cron and stores each user's language server-side.
Cairn today: no address for anyone (OIDC scopes lack email, LDAP doesn't fetch mail, local accounts have no field), UI language lives only in the browser, no password-changed bell kind.

Recommended v1: config/env (secrets via _FILE), TLS required (STARTTLS mandatory, no skip-verify; plaintext only to loopback/unix or with an explicit flag + warning), password and Microsoft XOAUTH2 client credentials; dashboard section read-only with Check connection + Send test (real SMTP replies shown); addresses from OIDC email (only email_verified), LDAP mail, admin-set for local accounts; server-side UI language; persisted outbox with retry (24 h, then admin bell), single sender lease (#742, at-least-once with stable Message-ID), global rate limit 30/min; privacy (generic subjects, no remote content, one recipient per mail, Auto-Submitted, repudiation contact). Mandatory security mails: device connected, app passwords revoked, device removed/resumed/refused, password reset by admin, password changed (new bell kind too), address changed; admins: break-glass sign-in, admin rights changed, emergency path removed/none, audit failing, storage restore suspected, key pin mismatch, TLS expired, LDAP insecure; reviewers: admin review due; plus #904 bulk mail. Library: net/smtp + small in-house layer (go-mail as fallback).

Open questions (recommendations): OAuth2 in v1 → Microsoft client credentials only; dashboard edits SMTP → not in v1; local addresses → admin-set (self-set with code in v2); unverified email → don't send unless trustUnverifiedEmail; sign-in failure mails → not in v1; links in mails → text URL only; admin recipients → all admins with an address + break-glass list; retry → 24 h; #904 proof wording → "accepted by the mail server"; M365/Google relay → document the processor/sovereignty trade-off, recommend a Swiss/on-prem smarthost; second notification address (NIST) → later; BSI APP.5.3 text → read before the spec cites it.

## Research (2026-10-29) **NIST SP 800-63B-4 (VERIFIED):** §4.1.2.1 binding a new authenticator SHALL notify via an independent mechanism (§4.6); §4.2 note: a password replaced while other authenticators exist counts as binding; §4.5 SHOULD notify on invalidation; §4.6: notifications SHALL go to all stored addresses, CSPs SHALL support **two** addresses per account, and give instructions + contact to repudiate. **Microsoft 365 (VERIFIED, MC786329):** Basic SMTP AUTH disabled by default for existing tenants **end of Dec 2026**; OAuth (XOAUTH2, client credentials, `SMTP.SendAsApp`) is the path; 587 STARTTLS only; 30 msgs/min, 10k recipients/day; alternatives: relay connector (static IP), HVE (internal only, paid). **Google:** app passwords or the Workspace SMTP relay; XOAUTH2 needs full-mailbox scope. **Market:** Nextcloud and Gitea fall back to plaintext when STARTTLS is missing; OpenCloud and Gitea drop failed mail silently; Keycloak has XOAUTH2 (Microsoft only); FileRun queues with a cron and stores each user's language server-side. **Cairn today:** no address for anyone (OIDC scopes lack `email`, LDAP doesn't fetch `mail`, local accounts have no field), UI language lives only in the browser, no password-changed bell kind. **Recommended v1:** config/env (secrets via `_FILE`), TLS required (STARTTLS mandatory, no skip-verify; plaintext only to loopback/unix or with an explicit flag + warning), password and Microsoft XOAUTH2 client credentials; dashboard section read-only with Check connection + Send test (real SMTP replies shown); addresses from OIDC `email` (only `email_verified`), LDAP `mail`, admin-set for local accounts; server-side UI language; persisted outbox with retry (24 h, then admin bell), single sender lease (#742, at-least-once with stable Message-ID), global rate limit 30/min; privacy (generic subjects, no remote content, one recipient per mail, `Auto-Submitted`, repudiation contact). Mandatory security mails: device connected, app passwords revoked, device removed/resumed/refused, password reset by admin, **password changed (new bell kind too)**, address changed; admins: break-glass sign-in, admin rights changed, emergency path removed/none, audit failing, storage restore suspected, key pin mismatch, TLS expired, LDAP insecure; reviewers: admin review due; plus #904 bulk mail. Library: net/smtp + small in-house layer (go-mail as fallback). **Open questions (recommendations):** OAuth2 in v1 → Microsoft client credentials only; dashboard edits SMTP → not in v1; local addresses → admin-set (self-set with code in v2); unverified email → don't send unless `trustUnverifiedEmail`; sign-in failure mails → not in v1; links in mails → text URL only; admin recipients → all admins with an address + break-glass list; retry → 24 h; #904 proof wording → "accepted by the mail server"; M365/Google relay → document the processor/sovereignty trade-off, recommend a Swiss/on-prem smarthost; second notification address (NIST) → later; BSI APP.5.3 text → read before the spec cites it.
Author
Owner

Decision (Nikola, 2026-10-29): the v1 recommendations above are approved. Next: whole-page mockup (Basic settings › Mail server, address fields, sample mails in 4 languages), then spec and build.

**Decision (Nikola, 2026-10-29):** the v1 recommendations above are approved. Next: whole-page mockup (Basic settings › Mail server, address fields, sample mails in 4 languages), then spec and build.
Author
Owner

Mockup approved (Nikola, 2026-10-29): design-direction-decision-needed/896-mail-server-mockup.html, all frames, with the recommendations for its 17 open questions (Basic settings tabs General + Mail server; "Connected" from the last send/check, check at start and on retries; amber after 2 failures, red after give-up or remote plaintext; Check connection stops after AUTH; test recipient prefilled, 5 per admin per 10 min, audited; smtpHost: "unix:/path"; mail.replyTo defaulting to the contact; Entra email_verified: verify in the spec, and if absent document auth.oidcTrustUnverifiedEmail: true for Entra with a UI hint; admin bells mail-failing after 15 min and mail-undelivered hourly, not mutable; language stored server-side from the browser, mail.defaultLanguage until then; address in the accounts list grey line + "no e-mail" filter; shared addresses allowed; text + simple inline-styled HTML, no images; minimal outbox with "Retry now"; no address: no audit, counted in the Recipients row, #904 stores no-address; no nudge in v1; server time zone by name). Next: spec and plan, then build.

**Mockup approved (Nikola, 2026-10-29):** `design-direction-decision-needed/896-mail-server-mockup.html`, all frames, with the recommendations for its 17 open questions (Basic settings tabs General + Mail server; "Connected" from the last send/check, check at start and on retries; amber after 2 failures, red after give-up or remote plaintext; Check connection stops after AUTH; test recipient prefilled, 5 per admin per 10 min, audited; `smtpHost: "unix:/path"`; `mail.replyTo` defaulting to the contact; Entra `email_verified`: verify in the spec, and if absent document `auth.oidcTrustUnverifiedEmail: true` for Entra with a UI hint; admin bells `mail-failing` after 15 min and `mail-undelivered` hourly, not mutable; language stored server-side from the browser, `mail.defaultLanguage` until then; address in the accounts list grey line + "no e-mail" filter; shared addresses allowed; text + simple inline-styled HTML, no images; minimal outbox with "Retry now"; no address: no audit, counted in the Recipients row, #904 stores `no-address`; no nudge in v1; server time zone by name). Next: spec and plan, then build.
Author
Owner

Shipped in v0.6.374 (PR #1050). Both dogfoods run v0.6.374; pods ready, only the known WARN lines. No mail block is configured on the dogfoods, so mail is off there and the Mail server tab shows the setup steps.

Sending

  • mail.* is configuration only.
    • STARTTLS is mandatory, and implicit TLS on port 465 is supported.
    • Plain text only to a loopback host or unix socket, or with smtpAllowPlain plus a WARN.
    • No skip-verify; the certificate appears in Certificates.
  • Sign-in methods: PLAIN, LOGIN, and XOAUTH2 for Microsoft 365 (client credentials).
  • Outbox: one record per e-mail with a stable Message-ID, and a sender lease across instances (#742).
    • Retries back off from 1 minute up to hourly; Cairn gives up after 24 h.
    • Sent ids are remembered for 24 h, there is a rate limit, and administrators can retry now.

What is mailed

  • 17 notice kinds go out in the recipient's language.
    • People: device connected or removed, app passwords revoked, password changed or reset, e-mail address changed (to the old and the new address).
    • Administrators: emergency sign-in, admin rights changed, no emergency access, audit log failing, storage restored, key check, certificate expired, LDAP without verification, admin review due, mail undelivered or restored. These also go to mail.adminNotify.
  • #904 storage-restored mail carries per-person results and CSV columns.

Addresses and language

  • OIDC addresses count only with email_verified, or xms_edov from Entra issuers, or oidcTrustUnverifiedEmail. Users & access shows the Entra hint.
  • LDAP addresses come from ldapMailAttr; config accounts from auth.users[].email.
  • Administrators can set addresses on local accounts. Each change is audited, both addresses are told, and the person gets an email-changed bell item.
  • The language is stored with the account.
  • A departed account's profile is removed by the directory re-check or by Delete unread files.

Admin UI and audit

  • Basic settings › Mail server: status, Check connection, Send test e-mail, outbox.
  • Overview row and cards, mail bells, and a Certificates row.
  • Audit verbs: mail-sent, mail-failed, mail-test and account-email-set.

Docs: docs/handbook/mail.md, section 8 of the Entra page, the configuration reference, and ARCHITECTURE.md.

Upgrade note: the auth.oidcScopes default now includes email.

The live checks are in #1005. Closing.

**Shipped in v0.6.374** (PR #1050). Both dogfoods run v0.6.374; pods ready, only the known WARN lines. No `mail` block is configured on the dogfoods, so mail is off there and the Mail server tab shows the setup steps. **Sending** - `mail.*` is configuration only. - STARTTLS is mandatory, and implicit TLS on port 465 is supported. - Plain text only to a loopback host or unix socket, or with `smtpAllowPlain` plus a WARN. - No skip-verify; the certificate appears in Certificates. - Sign-in methods: PLAIN, LOGIN, and XOAUTH2 for Microsoft 365 (client credentials). - Outbox: one record per e-mail with a stable Message-ID, and a sender lease across instances (#742). - Retries back off from 1 minute up to hourly; Cairn gives up after 24 h. - Sent ids are remembered for 24 h, there is a rate limit, and administrators can retry now. **What is mailed** - 17 notice kinds go out in the recipient's language. - People: device connected or removed, app passwords revoked, password changed or reset, e-mail address changed (to the old and the new address). - Administrators: emergency sign-in, admin rights changed, no emergency access, audit log failing, storage restored, key check, certificate expired, LDAP without verification, admin review due, mail undelivered or restored. These also go to `mail.adminNotify`. - #904 storage-restored mail carries per-person results and CSV columns. **Addresses and language** - OIDC addresses count only with `email_verified`, or `xms_edov` from Entra issuers, or `oidcTrustUnverifiedEmail`. Users & access shows the Entra hint. - LDAP addresses come from `ldapMailAttr`; config accounts from `auth.users[].email`. - Administrators can set addresses on local accounts. Each change is audited, both addresses are told, and the person gets an `email-changed` bell item. - The language is stored with the account. - A departed account's profile is removed by the directory re-check or by Delete unread files. **Admin UI and audit** - Basic settings › Mail server: status, Check connection, Send test e-mail, outbox. - Overview row and cards, mail bells, and a Certificates row. - Audit verbs: `mail-sent`, `mail-failed`, `mail-test` and `account-email-set`. **Docs:** `docs/handbook/mail.md`, section 8 of the Entra page, the configuration reference, and ARCHITECTURE.md. **Upgrade note:** the `auth.oidcScopes` default now includes `email`. The live checks are in #1005. Closing.
Cordy closed this issue 2026-10-29 23:45:55 +00:00
Sign in to join this conversation.
No labels
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: Cordy/Cairn#896
No description provided.