sam-4screen-desktop 2026-9-3:15:39:8

This commit is contained in:
2026-09-03 15:39:08 +10:00
parent 9ec7eea1c3
commit 3cd7053daf

View File

@@ -158,6 +158,21 @@ where-woof.com outgoing (transactional) email:
- DNS for delivery already set (SPF/DKIM/DMARC include SES + PurelyMail)
- Do NOT use PurelyMail SMTP for site/transactional mail — use SES
```
## SES SMTP CREDENTIALS (created 2026-09-03, local file `aws-credentials.local`)
- Endpoint: `email-smtp.ap-southeast-2.amazonaws.com` : `587` (STARTTLS)
- IAM user: `ses-smtp-user.20260903-152339`; SMTP username/password stored in `aws-credentials.local` (600, not Obsidian)
- Permission: `ses:SendRawEmail` only (least privilege)
- **Production access requested 2026-09-03** (transactional form, where-woof.com) — awaiting AWS approval (~hours)
- Until approval: SES sandbox = can only send to verified addresses (samuelrolfe@gmail.com).
## TODO — audasmedia.com.au SES (2026-09-03)
- [ ] **Give audasmedia.com.au the same SES sending access as where-woof**: create/confirm SES identity for audasmedia.com.au (already exists), create SMTP creds for it, and ensure production access covers it.
- audasmedia.com.au will also send email (site mail) → same pattern as where-woof.
- When audasmedia infra is built on .13 (user to advise).
## NEXT — audasmedia.com.au infra on .13 (2026-09-03)
- User will advise details. Apply same hosting/backup/email pattern as where-woof.
1. SES console → Send test email (audasmedia.com.au → samuelrolfe@gmail.com); check delivery + DKIM/SPF pass.
2. Request SES production access (free).
3. Then return to Phase 3 (local infra) / CMS migration project.