docs(admin): email is SMTP now, and the Gmail connect flow is gone
Engagement Phase 1's share of this repo (docs/website/ENGAGEMENT.md §6.0b). Four pages described a delivery path that no longer exists — one of them under the heading "There is no SMTP option", which is now the opposite of true. notifications-and-email.mdx: the Email section is rewritten around the three postures the org lead settled on (§7.1 Q5), leading with a relay and naming smtp.gmail.com:587 with an app password as the migration off OAuth2. Two cautions carry the failures that produce no error at all — Implicit TLS left on for port 587, which hangs, and an operator-typed sender the relay will not accept, which is an SPF/DMARC rejection that looks like nothing. Send test is what proves both. troubleshooting.mdx gains those two, plus the enabled toggle, which now gates every message rather than some of them. configuration.mdx loses the "set up Google first" ordering constraint, which is gone with the borrowed client. system-architecture.mdx's encrypted-at-rest list is corrected: the Gmail refresh token is replaced by the transport credentials, which are write-only like the sidecar token. This lands on `edge`, so nothing here is published while `main` still carries the Gmail flow. platform.json and capabilities.mjs are untouched — they belong to Phase 12. Co-Authored-By: Claude <noreply@anthropic.com>
This commit is contained in:
@@ -97,9 +97,18 @@ a Team. See [Teams](/docs/administration/teams/).
|
||||
|
||||
## Email and announcements never arrive
|
||||
|
||||
- **The contact form opens a mail client.** Email delivery is not connected; that is the
|
||||
documented fallback. Connect Gmail in **Settings → Email delivery** — after configuring
|
||||
the Google provider, which it reuses.
|
||||
- **The contact form opens a mail client.** Email delivery is not configured; that is the
|
||||
documented fallback. Enter SMTP credentials in **Settings → Email delivery**. If this site
|
||||
used to send mail and stopped, the Gmail connect flow was removed — the admin dashboard
|
||||
says so, and [Notifications and email](/docs/administration/notifications-and-email/) has
|
||||
the migration.
|
||||
- **Mail is configured but nothing arrives, and there is no error.** Two usual causes, both
|
||||
invisible without a test send. *Implicit TLS* left on for port 587 hangs rather than
|
||||
failing; and a **Send from** address the server will not let you send as is rejected for
|
||||
SPF/DMARC reasons. Press **Send test** — its failure message names both cases.
|
||||
- **Email was working and the toggle is still on.** *Enable email sending* now gates every
|
||||
message, not just some of them. If it is off, nothing is sent, including the contact
|
||||
form.
|
||||
- **A published post announced nothing.** The Discord bot is a separate container. If the
|
||||
Discord Bot screen says *bot unreachable*, it is not running.
|
||||
- **A missed announcement does not come back.** Nothing retries; the post itself is still
|
||||
|
||||
Reference in New Issue
Block a user